The following are other organization types that you will eventually eed in order ot manage the publication and licensing of your application. Production/CRM Org: the purpose of this organization for managing contacts, leads, opportunities, cases and other CRM objects. AppExchange Publishing Org (APO) This org is used to manage your use of AppExchange. This org is actually […]
Author: nisarkhan
Packages can be uploaded in one of two states Release: Release packages can be installed into subscriber production orgs and can also provide an upgrade path from previous releases. The downside is that you cannot delete the previously released components, or change certain things, such as a field’s type. Changes to the components that are […]
Important decision when creating a managed package is the namespace this is a prefix applied to all your components (custom objects, visualforce pages, lightning components etc…) The namespace prefix is an important part of the branding of the application since it is implicitly attached to any Apex code or other components that you include in your […]
A package is a container that holds your application components, such as Custom Objects, Apex code, Apex triggers, Visualforce pages, Lightning Components, and so on. This makes up your application. While there are other ways to move components between Salesforce orgs, a package provides a container that you can use for your entire application or […]
In most cases the platform automatically enforces admin-configured authorization settings, so your job is easy. However, because the platform is flexible, there are certain cases where developers can bypass authorization settings. To understand why and where this happens, you need to understand the two execution contexts that a Force.com app runs in: user and system. […]
Access to online data is generally restricted to only those who are identified, authenticated, and authorized. There are three main ways: –> Create, read, update, and delete (CRUD) settings ——–> Determine which objects a user can create, read, update, and delete –> Field level security (FLS) settings ——-> Determine which fields a user can read […]
Literal strings must be enclosed in single quotation marks. double quotation marks are reserved for enclosing attribute values, and must be escaped in strings. Use the “\” character to escape strings. Favorite
Lets create the component event first and called it “StudentSelectedEvent”:
|
1 2 3 |
<aura:event type="COMPONENT" description="Selected Student" > <aura:attribute name="contactId" type="Id" ></aura:attribute> </aura:event> |
The name attribute in must match the name attribute in the tag in the component that fires the event. in the above component event the type of event is “COMPONENT” and we have one attribute which is “contactId” and type of it is “Id” […]
–Calling base component WITH passing params
|
1 |
<aura:component controller="XXXXX" extends="c:Base" > |
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 |
<lightning:select label="select instructor" variant="label-hidden" name="instructor" value="{!v.selectedInstructorId}" onchange="{!c.onInstructorChange}" > <option value=""> select instructor </option> <aura:iteration items="{!v.instructors}" var="i"> <option value="{!i.Id}"> {!i.Name} </option> </aura:iteration> </lightning:select> |
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 |
onInstructorChange : function(component, event, helper) { component.set('v.selectedDeliveryId',''); var selInstructorId = component.get('v.selectedInstructorId'); if(component.get('v.selectedInstructorId') != '' && component.get('v.selectedInstructorId') != null) { helper.callServer( component,"c.getDeliveriesByInstructor", function(response) { component.set('v.deliveries',response); }, { instructorId : component.get('v.selectedInstructorId') } ) helper.onFilterEvent(component); } else { component.set('v.deliveries',""); } }, |
Favorite
–Calling base component without passing any params
|
1 |
<aura:component controller="XXXXX" extends="c:Base" > |
|
1 2 3 4 |
<aura:handler name="init" value="{!this}" action="{!c.doInit}"/> |
|
1 2 3 4 5 6 7 8 9 10 11 |
({ doInit : function(component, event, helper) { helper.callServer( component, "c.getCertifications", function(response) { component.set('v.certifications', response); } ); } }) |
Favorite