Thank you Salesforce !!!! for not extending waiting period for releasing local development of lightning components too longer. Local development is nothing but, which enables build, run and test lightning web components without deploying the code to salesforce sandbox or scratch orgs.Continue reading
This is my first lightning web component to list down all the available contacts from a json file.
This is a simple example to validate lightning input fields in a lightning component.Continue reading
In this blog, I would like to discuss you about how to create a custom lightning page template or layout using SFDX.
In this blog, I would like to discuss how to test the salesforce apex rest APIs using postman which is one of the well-known rest client available in the market.Continue reading
In this blog, I would like to share with you the available Salesforce CLI Commands. CLI Commands will reduce your effort in creating and configuring the Apex, Visualforce, Lightning components. Refer to my previous blogs for setting up the SFDX with visual studio code IDE.
In this blog, I would like to share the steps for configuring Salesforce Developer Experience (SFDX) in my favourite code editor Visual Studio Code for enabling Source Driven Development model. Salesforce DX supports the traditional application development experience with debugging (specifically on apex), CLI (Command Line Interface) Support along with Visual Studio Code.
Lightning mainly focuses on the user experience on the web and mobile interfaces. So, most of the scenarios we should need to know the information of the browser to align the design with respect to the device browser. In this post, I would like to discuss, how we can detect the browsing device information in a lightning component.
In lightning, we have developed multiple components for different functionalities. All custom components include a lot of boilerplate code and we will have to exclude most of the redundant code by building generic function in the helper part of aura bundle. However, it wouldn’t be the perfect solution to avoid the redundancy as we will have to do the same for other components as well. For example, Communication between an apex controller and a component is written separately for each custom component, even if the components are related to each other. Are there any mechanisms available in lightning for abstracting the boilerplate into one component for others to make use of it?
From my experience, this can be solved by Inheritance as it makes the code more structured and flexible. The Salesforce Apex framework supports inheritance similar to what we see in object-oriented programming languages like Java and others. Is Aura framework built to support inheritance?
“Tell me and I forget, teach me and I may remember, involve me and I learn ” ― benjamin franklin
I would like to involve you to learn how we can allow our users to log in across multiple Salesforce orgs using single sign-on (SSO) credentials.
Let’s take a look into the advantages of having single sign on.
- We spend less time managing passwords.
- Our employees save time when they don’t have to manually log in to Salesforce.
- More people use Salesforce. Users can send out links to Salesforce records and reports, and their recipients can open them in a single click.
- We can manage access to sensitive information from one place.
Salesforce offers the following ways to use SSO.
- Federated authentication using Security Assertion Markup Language
- Delegated authentication (Integrate authentication with your LDAP server or use a token instead of a password for authentication)
- External Authentication providers- Salesforce uses the user’s login credentials from the external service provider to establish authentication credentials. (Google, PayPal, and LinkedIn)