In design section you can control which attributes are exposed to builder tools like the Lightning App Builder, Experience Builder, or Flow Builder. A design resource lives in the same folder as yours .cmp resource, and describes the design-time behavior of the Aura component—information that visual tools need to display the component in a page or app.
Continue reading “Design in Lightning Bundle”
<design:component label="Hello World">
<design:attribute name="subject" label="Subject" description="Name of the person you want to greet" />
<design:attribute name="greeting" label="Greeting" />
Renderer in Client-side is to override default rendering for a component. You can consider what data should render on load or on reload. The framework’s rendering service takes in-memory component state and creates and manages the DOM elements owned by the component. If you want to modify DOM elements created by the framework for a component, you can modify the DOM elements in the component’s renderer. Otherwise, the framework will override your changes when the component is rerendered.
The base component in the framework is aura:component. Every component extends this base component.
This renderer has base implementations for the four phases of the rendering and rerendering cycles:
Continue reading “Renderer in Lightning Bundle”
Documentation helps developers use your components to develop their apps more effectively. You can provide interactive examples, documentation, and specification descriptions for
Continue reading “Documentation in Lightning Bundle”
Sometimes there will be scenario where you need to define specific set of style to the tags that are used in component. This is similar to how style tags are defined in normal HTML pages or Visualforce pages. Only difference is style name definition will start with .THIS keyword. You can also define specific style tags for other devices like, mobile or tablet etc using @media.
Continue reading “Style in Lightning Bundle”
Continue reading “Helper in Lightning Bundle”
- Helper is similar to controller but helper does not handle events.
- Helper functions also enable specialization of tasks, such as processing data and queueing server-side actions.
- Helper methods are local to Component bundle.
- A helper function can pass in any arguments required by the function, such as the component it belongs to, a callback, or any other objects.
- You can call a helper method from another helper method using this. operation.
Continue reading “Controller in Lightning Bundle”
Component is where you do actual UI design for the module that is being developed. Lightning has its own set of tags which are called aura tags. When you create a component with above steps you see salesforce created a default tag for lightning component.
Continue reading “Component in Lightning Bundle”
// User Interface Code Here.
Salesforce introduced lightning platform way back in 2014 and to build custom applications on lightning platform salesforce introduced Lightning Aura Components in Sprint 2015. Salesforce lightning is best known for its modern UI interface and beautiful look, which is a Platform as a Service (PaaS) platform that allows developers to create add-on applications that integrate into main salesforce.com application. These third-party applications are hosted on Salesforce.com’s infrastructure. In this blog we will see what a Lightning Aura Component contains.
The Lightning Component framework is a UI framework for developing single page applications for mobile and desktop devices. Lightning includes the Lightning Component Framework and some exciting tools for developers. Lightning makes it easier to build responsive applications for any device like desktop, mobile, tablet etc. As per Sprint’19 release you can build lightning component using two programing models.
Continue reading “Introduction to Lightning Aura Component.”
- Lighting Aura Component.
- Lightning Web Component.
Access modifiers are used in apex class in salesforce. Similar to Java programming, Salesforce supports 4 different access modifiers in salesforce.
Continue reading “Access Modifiers in Salesforce”
Why do we have this concept in salesforce?
In salesforce there are many restrictions put on user in different ways, like OWD, Profiles, Field-Level Security, Object permissions, Sharing Rules, Role Hierarchy etc. But these restrictions do not apply to System Administrator. System admin has access to all records that are in system irrespective of owner or sharing rules or access to any object or field. An apex classes can be executed by any user in salesforce. An apex class can be triggered from a Visualforce Page, Visualforce Components, Lightning Components, Process Builder, Flow and many more ways. Class in salesforce can be executed in 3 modes in salesforce
- with sharing
- without sharing
- inherited sharing
Use the with sharing or without sharing keywords on a class to specify whether sharing rules must be enforced. Use the inherited sharing keyword on an Apex class to run the class in the sharing mode of the class that called it.
Continue reading “User Mode and System Mode of Apex Class in Salesforce.”