Lightning – ABSYZ

Drive User Action with Floating Prompts in Lightning Experience

Kshitij Tahiliani — Wed, 29 Apr 2020 20:42:17 +0000

Think of driving employees to complete compliance training, pushing them to fill out a GPTW annual survey or sending reminders for completing Salesforce certification maintenance exams. Salesforce Floating prompts can assist you to drive employee actions, broadcast company news, send recurring reminders & more.

Let us look at an illustration for a Floating prompt. Below prompt is meant to drive all Project managers to complete the forecasting activity for the current month when they view their Salesforce landing page.

Before deep diving into the creation of a Floating prompt, let us review the org-wide prompt settings.

Review Org-Wide Prompt Settings

Go to Setup-> In-App Guidance -> Add Prompt -> Prompt Settings.

Display between prompts: This decides the time delay between showing two prompts per app. With the current custom setting of 2 hours, you would be able to see another prompt after viewing one in the same app only after a delay of 2 hours.
Salesforce standard prompts: You would’ve come across these prompts in your org for introduction/highlighting of new Salesforce features like Recycle bin in Lightning or Controlling the density feature. These prompts are part of in-app guidance offered by Salesforce which can be activated/deactivated from this path
Custom Prompts: You can activate/deactivate all the custom prompts in your org using this option.

Setting up a Floating Prompt

The Authoring Bar

Let’s see the origins of the Floating prompt introduced earlier. First step would be to reach the Prompt authoring bar. You can go there from this path: “Setup-> In-App Guidance -> Add Prompt -> Open Authoring Bar”.

Once opened, the authoring bar would remain at the top of an App. You would be able to navigate between different pages here like you do when working within an app by switching between Home Page, record pages, list views & more. When you are on a page(see above screenshot), you would see the already added prompts to the page from 1) “Prompts on this Page” drop down. You can also add more prompts on the page you are using 2) “Add Prompt” button.

When clicking on “Prompts on this page”, you will be able preview & edit prompts already defined on the current page.

Add a New Prompt: Select Type & Position

From the “Add Prompt” option on the authoring bar, you will be taken to the prompt wizard. Select “Floating Prompt” from the below screen:

Select the “Floating Prompt” option on the above screen. Next you can decide Prompt’s location. There are 6 locations where a floating prompt can be placed. Be sure you do not have important information on that part of the page as you can’t temporarily minimise the prompt without interacting with it. You can select the “Top Left” option for the current case.

Visibility

On the next screen, you’ll have to decide whether to restrict this prompt to certain profiles & permission set assignees or keep it open to all. In the current example, you will be allocating this to a specific profile since this message is targeted towards the Project managers group.

Additionally, you can add permission sets from the next screen which essentially means you can set the prompt’s visibility based on a combination of Profile & Permission sets. You can currently have a combination of upto 10 profiles & permissions on a Prompt.

Add Content

Next, comes the all important content section.

A floating prompt’s content consists of:

Title – Header for the prompt
Body – Accepts plain text only with 240 chars. The content should be concise & convey the message effectively without any ambiguity.
Dismiss Button Label – Name of the Dismiss Button label
Action Button Label (Optional) – Name of the Action Button label
Action button URL (If Action button Label has values) – The “Action” button can redirect you to another URL. It does not invoke a flow or a process. For the current example, you can redirect the user to another app page where forecasting activity is done.

Scheduling

Finally, fix a date range during which you want the prompt to show up for the target audience. Since the expectation is to complete the forecasting activity by end of 1st week of May, we would keep the date range from 1st – 8th May’20

Configure the frequency at which this prompt would show. Add the no. of times it should show & the days between each occurrence in the “Times to Show” & the “Days in Between” fields respectively.

The “Show prompt when the page loads” checkbox overrides the default time gap set in “Prompt Settings” & shows the prompt every time the page loads if the user hasn’t interacted with the prompt. You can use this option to reinforce the importance of the current prompt’s message over other configured prompts.

Add remaining details & Preview

Post configuring the schedule, you can add remaining details for the prompt like Prompt Name, API name & description on the last page of the creation wizard.

Once done, you can Save & Preview the Prompt.

You can make further edits to the prompt using the “Edit” button or make it ready for use by marking it “Done”.

User Interaction & its impact on Floating Prompt’s Occurrences

Scenario:1 “Action” button is defined on the Floating Prompt

Since an “Action” button is defined, the intent is for the user to complete the action. Till the action button is clicked, the Prompt would show up based on its schedule settings.

Below are the Prompt behaviours which occur based on User Actions:

Sr. No.	User Action	Prompt Behaviour
1	Do nothing, stay on the page	Prompt stays
2	Do nothing on Prompt – Navigate to another page & come back to the first page where prompt is defined	Show prompt when user navigates back to same page**
3	Close the prompt using ‘X’ on top right	Show prompt when user navigates back to same page**
4	Click on “Do it Later”	Show prompt after 1 day***
5	Click on “Forecast Now”	Stop showing prompt even if more recurrences are scheduled

** Org-wide delay of 2 hrs set earlier in “Prompt Settings” is overwritten by “Show Prompt when Page loads” checkbox set in the Floating prompt’s schedule we’ve defined. If the checkbox was unchecked, the system would wait for 2 hrs from occurrence of any other prompt on the current app before showing the Floating Prompt on the current page again.

*** Since in the Prompt’s Schedule settings “Days in between” is set to 1.

Scenario:2 “Action” button is not created on the floating prompt

With all remaining settings being the same as in Scenario:1, Sr. No. 1-3 from the “User Action – Prompt Behaviour” mapping table in the previous scenario would still hold. Sr. No. 4’s behaviour would change to -> Stop showing prompt even if more recurrences are scheduled. This is because without the action button, the prompt only expects the user to view the message. An appropriate example can be:

Conclusion

As mentioned in the introduction, Floating prompts are meant to drive user action. But there is another engagement activity which Salesforce prompts support – User Adoption. The other category of prompts i.e Docked prompts are primarily used for driving adoption using step by step instructions & in-prompt videos. You can expect another post on it soon ! Meanwhile, hope you enjoyed this blog !! Thank you for your time !!!

Summer’20 Release Treasure Hunt: Top Features

Abhirup Mukherjee — Wed, 29 Apr 2020 06:04:49 +0000

Summer’20 is just around the corner… and with every release Salesforce introduces new features and enhancements made to the platform. Thus enhancing our productivity by using the native declarative and programmatic features.

Summer’20 official Release notes are not yet out, below are few features we have identified as few and among the coolest ones!

Let’s look at few out of the box features which are going to be introduced with this release!!

1. Flows

1.1 Before/After Handling in Flow Triggers

We recently saw Flows inherit an ability from Apex: the ability to act as a Trigger. You could select criteria which a Flow would be called automatically, and handle data.

With Summer ’20, we’re seeing yet another step in Flow becoming a fully-fledged declarative alternative to Apex: the ability to handle before and after events. This is a massive step for Flow and will grant even more power to declarative users.

Instead of being an Auto-Launched Flow, this will now be known as a ‘Record Changed’ Flow (one of a number of new Flow Types).

You can choose when to trigger the flow(see image below).

1.2 Run Flows in System Mode

Now you can execute/run your flows overriding the current user’s permissions by setting your flow to run in system context with sharing. The flow still respects org-wide default settings, role hierarchies, sharing rules, manual sharing, teams, and territories, but it ignores object permissions, field-level access, or other permissions of the running user.

1.3 Flow Loop Variables are Automatically Created

In every iteration of Flow Builder and Designer to date, we’ve had to create our loops, then create a separate loop variable resource. It’s just an extra step that felt so unnecessary.

Salesforce has addressed this by creating this resource automatically when you create a loop. Let’s say you had a loop called ‘lead_loop’, Flow Builder will automatically create a resource called ‘Current Item from lead_loop’. The result? It will save you a ton of time, and make it much easier for new Flow users to learn how to use the tool.

1.4 Roll back Mode in Flow Debugger

With rollback mode enabled in your Flow Debugger, any changes that are executed by your Flow won’t be saved while you test it. This helps to keep your data clean and tidy while you create and test your Flows. This is one of those tiny changes that will have a huge impact.

2. Lightning

2.1 Navigate to a record page with default values

Now, you can create custom button or links that pass default field values to a new record using formulas.

This feature is not available for the Lightning communities, or the Salesforce mobile app.

To construct a custom button or link that launches a new record with prepopulated field values, use this sample formula:

lightning/o/Account/new?defaultFieldValues=
    Name={!URLENCODE(Account.Name)},
    OwnerId={!Account.OwnerId},
    AccountNumber={!Account.AccountNumber},
    NumberOfEmployees=35000,
RecordType=Account_Record_Type_Test,
    CustomCheckbox__c={!IF(Account.SomeCheckbox__c, true, false)}

2.2 Empty the Recycle Bin in One Step

Empty your Salesforce org’s Recycle Bin in Lightning Experience with a single click. Previously, you either selected individual items to delete, or had to switch to Salesforce Classic to remove all items at once permanently.

2.3 Split View in Standard Navigation

Standard Navigation gets a Console makeover! Console view displays multiple records and their related records on the same screen, and ‘Split View’ displays a List View within a record page:

This means that you can quickly work through records – ideal for updating overdue Tasks, all Opportunities in your pipeline, or the new Leads assigned to you…or anything you use List Views for!

2.4 Source Tracking in Sandboxes

You can now enable Source Tracking in Developer and Developer Pro to use the Salesforce Command Line Interface (CLI) to view, pull, and push changes in the Sandbox. Once enabled, any new Sandboxes you create will have tracking enabled automatically, and after refresh for any existing Sandboxes.

3. Development

3.1 The @track decorator is no longer needed to make the Lightning Web Component Class Reactive

In order to capture changes to a field’s value and to make it reactive to changes you had to decorate it with @track before Spring’20.

But with Summer’20 @track decorators are no more needed to make the fields reactive, the fields in LWC are reactive by default now.

If a field’s value changes, and the field is used in a template or a getter of a property that’s used in a template, the component rerenders and displays the new value.

3.2 Style Lightning Web Components with Custom Aura Design Tokens

A Lightning web component’s CSS file can use a custom Aura token created in your org or installed from an unmanaged package. Tokens make it easy to ensure that your design is consistent, and even easier to update it as your design evolves.

You can define a token value once and reuse it in your Lightning component’s CSS.

Create a custom Aura token in the Developer Console by creating a Lightning Tokens bundle.

Here “myBackgroundColor” is a custom aura token.

Custom Aura tokens aren’t new, but now you can use them in a Lightning web component’s CSS file by using the standard var() CSS function. Prepend –c- to the custom Aura token.

// myLightningWebComponent.css
color: var(--c-myBackgroundColor);

3.3 Smarter Source Tracking for Lightning Web Components in Scratch Orgs

Until now, CLI commands tracked source changes for Lightning web components in a local project, but didn’t track changes to Lightning web components in a scratch org.

With Summer’20 release Salesforce command-line interface (CLI) now tracks changes to Lightning web components in a scratch org. The CLI output lists any changes, and alerts you to any conflicts between your local project and a scratch org.

This change is available in Salesforce CLI with salesforcedx v48, which released on February 15, 2020.

sfdx force:source:pullPulls 
changed source from a scratch org to your project.

sfdx force:source:pushPushes 
changed source from your project to a scratch org.

sfdx force:source:statusTracks 
changes between your project and a scratch org.

3.4 DOM API Changes May Require UI Test Updates

The content and structure of HTML, CSS, and the DOM in Lightning Experience can change at any time and can’t be considered a stable API. Automated UI tests that use tools like the Selenium WebDriver to reach into component internals require your ongoing maintenance.

4. Reports and Dashboards

With Summer’20 release now we can send the attachment while scheduling the Report/Dashboards from Salesforce Lightning.

Navigate to Report & Dashboards Setting & Enable “Let users attach reports as files to report subscription emails in Lightning Experience” Setting.

5. Federation Id can be made case sensitive

With Summer’20 release you now have the option to make the Federation Id as case-sensitive. Previously this feature was not available.

Go to setup, from setup select single sign on settings and enable the checkbox “Make Federation Id case sensitive”.

6. AWS Private Link

With summer’20 release Salesforce introduces the Private Connect. Assuming this will facilitate establishing connection between Salesforce and AWS VPC and other AWS Services.

AWS PrivateLink simplifies the security of data (hosted on the AWS platform) shared with cloud-based applications by eliminating the exposure of data to the public Internet. AWS PrivateLink provides private connectivity between VPCs, AWS services, and on-premises applications, securely on the Amazon network.

With AWS PrivateLink, you can connect your VPCs to AWS services and SaaS applications in a secure and scalable manner.

From setup, go to Private Connect, choose whether you want to create an Inbound Connection/Outbound Connection.

Inbound connection will allow you to access data shared with your Salesforce Application from an AWS VPC(Virtual Private Cloud) which is an additional layer of an Amazon EC2 (Elastic Compute Cloud)Instance.

Outbound Connection will allow you to share/proxy your Salesforce Data into an AWS VPC.

You would need to specify the end point Id of your AWS VPC and also the region in which the service is hosted.

You can also specify the option of provisioning the connections and choose whether to provision connection immediately or at a later point of time.

These are some of the features that we have explored out.

We will be back with Part I and Part II of the Release highlights with more information on the hot and newest features that shall roll into your Salesforce org’s with the summer’20 release.

Till then, you can sign up here for a Pre-Release Org and keep on exploring!!

Outlook connection with Salesforce through custom Objects

kumarkankari — Wed, 19 Feb 2020 07:21:41 +0000

This blog post helps you to integrate Microsoft Outlook with Salesforce by using Lightning for Outlook sync by OAuth 2.0 connection method and create Custom Objects data from outlook.

Set Up Lightning for Outlook in the Microsoft Outlook

For setting up of Outlook connection to salesforce, please follow the below blog from points 1-9 to setup the users in outlook who needs to have sync with Salesforce.

.https://blogs.absyz.com/2018/07/11/step-by-step-process-of-integration-between-outlook-and-salesforce-by-service-account-connection-method/

Lightning for Outlook and Lightning Sync from Salesforce

Enter Outlook Integration and Sync in the quick find box
Enable Outlook Integration and Lightning Sync.

Expand the Lightning Sync section after enabling it. You could see two types of connection methods.
OAuth 2.0
Service account

Select the OAuth 2.0 and click on Log in Button.

Once you click on Login button, It will automatically redirect to outlook login page.

Enter the details of Global admin User of Microsoft Account and click on Accept.

The connection gets accepted and we will be getting the Office 365 Tenant ID automatically which is shown in below screenshot.

Click on Connect. The connection gets authorised and ready for testing the user connection with Outlook.

Enter the user’s email address whose email is same in both the systems (Salesforce & Outlook) in the Test your connection prompt.

Click on test after entering the email address. This will verify with Outlook server and enables a secure connection between both the systems.

Now we have successfully connected with email server, so the exchange happens between both the systems.

Define the sync settings and click on Go to Configs

Define lightning sync configurations.

Click on New lightning sync configurations and give the exchange behaviour as shown below.

Click on Save.

Outlook Connection Establishment:

Open your Outlook mailbox and click on mail and you can find more actions on right side.

Click on Get Add-ins.

From the search bar you can search for salesforce add in and add to outlook.

Once the salesforce plugin is added, login to salesforce where you can select your environment (Sandbox / Production).

Enter the salesforce login credentials and click on login. After successful connection we can see the standard objects displayed in the connector.

Now we can directly create Task, Event, Account, Contact and Lead from outlook to salesforce.

Now, we are going to learn how to add Custom Objects to this standard list.

I have used a custom Object (Agent) and some custom fields to link with Outlook.

Go to salesforce and search for global action from search bar and then create a new global action.

After creation of new global action (New Agent), it will take you through page layout of that action where we can add the necessary fields to that layout.

Enter Outlook in the search bar and click on Outlook Integration and Sync.

Expand the section of Outlook Integration and click on New Email Application Publisher Layout.

Create a new Layout and add the global action (New Agent) to Quick Action.

Now add the layout to profiles.

Click on Publisher layout assignment and add the layout to profiles.

Once this is done, we can able to view custom objects along with standard objects in Outlook.

create a custom object data from outlook to salesforce.

Limitations for creating Global action in salesforce.

Adding too many fields to an action layout can impact user efficiency. We recommend a maximum of 8 fields. To reduce the number of fields, you can set predefined values for fields that need a value but won’t often be edited. You can safely remove those fields from the layout. Set predefined values from the action detail page.

If we have record types for an object, we need to create global action for each record type because each record type has its own page layout.
Custom Objects which are on the detail side of a master-detail relationship cannot be created via Global Action. A detail object record requires a master record and can’t be created in a non-entity-specific context.
Ref—– https://help.salesforce.com/articleView?id=000337323&type=1&mode=1

Displaying standard report data in Lightning component

sandeeppolishetty — Mon, 30 Dec 2019 15:37:25 +0000

Sometime we might end up the slow performance of showing custom charts by querying the object data- if the data is in millions. The best way to improve the performance is by creating a standard report and getting data of report to apex with ReportManager class.
we can also pass the filter values based on your requirement and display charts in the Lightning component with the help of Javascript chartCanvas class.

FYI : The above charts are constructed with standard reports- Matrix and Summary type.

We need to consider some standard classes.

ReportManager class helps to run a report synchronously or asynchronously.

ReportResults class contains the results of running a report.

ReportFilter class contains information about a report filter, including column, operator, and value.

and some Methods of above classes

describeReport(reportId) Retrieves report, report type, and extended metadata for a tabular, summary, or matrix report.

Example:Reports.ReportDescribeResult describe = Reports.ReportManager.describeReport(reportId);

getReportMetadata() Returns metadata about the report, including grouping and summary information.

Example:Reports.ReportMetadata reportMd = describe.getReportMetadata();

getReportFilters() Returns a list of each custom filter in the report along with the field name, filter operator, and filter value.

Example: Reports.ReportFilter filterlist = reportMd.getReportFilters()[0];
filterlist .setValue(filterId);

Apex code

[sourcecode language=”java”]
@AuraEnabled
public static string Getreportplanned(String AccId){
Report repRec=[SELECT Id,Name,DeveloperName from Report where DeveloperName=:system.Label.CLNOV19SLS04];
string reportPlannedId=repRec.Id;
string filterId=String.valueOf(AccId).substring(0, 15);
// Retrieves report metadata
Reports.ReportDescribeResult describe = Reports.ReportManager.describeReport(reportPlannedId);
Reports.ReportMetadata reportMd = describe.getReportMetadata();
// Add/Override filters
Reports.ReportFilter filterlist = reportMd.getReportFilters()[0];
filterlist .setValue(filterId);
//and Run report
Reports.ReportResults reportResult = Reports.ReportManager.runReport(reportPlannedId,reportMd);
system.debug(‘ReportResultsJSON’+JSON.serialize(reportResult));
return JSON.serialize(reportResult);
}

[/sourcecode]

Aura component

To load chart on page load.

For displaying the report

To view standard report

[sourcecode language=”java”]
View Report
[/sourcecode]

Js Code

[sourcecode language=”java”]
var urlPlannedreport = ‘/lightning/r/Report/’+getPlannedReportId+’/view?queryScope=userFolders&fv0=’+accIdsub;

createPlannedchart: function(component) {
var chartCanvas = component.find(“plannedChart”).getElement();
var action = component.get(“c.getreportplanned”);

action.setParams({
“AccId”: component.get(“v.accrecId”)
});
action.setCallback(this, function(response) {
var state = response.getState();
if (state === “SUCCESS”) {
var reportResultData = JSON.parse(response.getReturnValue());
// alert(JSON.stringify(reportResultData));
var chartData = [];
var chartLabels = [];
var nullcheck = reportResultData.groupingsDown.groupings;
if (nullcheck !== null) {
for (var i = 0; i < (reportResultData.groupingsDown.groupings.length); i++) {
//Iterate and prepare the list of Labels for the chart
var labelItem = reportResultData.groupingsDown.groupings[i].label;
chartLabels.push(labelItem);
var keyTemp = reportResultData.groupingsDown.groupings[i].key;
//Prepeare the chart data to be plotted.
var valueTemp = reportResultData.factMap[keyTemp + “!T”].aggregates[0].value;
chartData.push(valueTemp);
}
}
//Construct chart-doughnut/bar
var chart = new Chart(chartCanvas, {
type: ‘bar’,
data: {
labels: chartLabels,
datasets: [{
label: “Count”,
data: chartData,
backgroundColor: [
“#52BE80”,
“#76D7C4”,
“#1E8449”,
“#2ECC71”,
“#FFB74D”,
“#E67E22”,
“#F8C471”,
“#3498DB”,
“#00BCD4”,
“#D32F2F”,
“#82E0AA”,
“#AFB42B”
]
}]
},
options: {
responsive: true,
title: {
display: true,
text: ‘Planned Visits’
},
scales: {

yAxes: [{
ticks: {
// max: 100,
stepSize: 25,
beginAtZero: true
},
scaleLabel: {
display: true,
labelString: ‘Visits Count’
},
}],
xAxes: [{
scaleLabel: {
display: true,
labelString: ‘Created Date’
}
}]
},
maintainAspectRatio: false,
legend: {
display: false,
position: “right”,
fullWidth: false,
}
}
});

} else(state === “ERROR”) {
console.log(‘Problem, response state: ‘ + state);
}

});
$A.enqueueAction(action);
}
[/sourcecode]

You can change the look of charts with the help of chartcanvas methods.

Using Modal/ Popup in Lightning Web Components

abhishekkumar915 — Thu, 31 Oct 2019 07:31:54 +0000

In this blog, we will be learning to use Modal/ Popup in Lightning Web Component. We will be using SLDS classes that helps in showing or hiding the Modal.

The below classes help in showing and hiding of the modal

slds-fade-in-open – Shows the modal
slds-backdrop_open – Shows the backdrop(greyed out)

So, adding and removing these classes at an action will show/ hide the modal accordingly.

In this example, we will be making a Modal component and show the data required by checking the sObject of the current record page it is being used. So, this component can be used at any sObject record page, and the required server call can be performed.

Let’s have a look at the components.

Apex Class

Modal_LWC_controller.cls
This class checks the sObject type and calls the function required for that sObject

/**
* @File Name          : Modal_LWC_controller.cls
* @Description        : 
* @Author             : Abhishek Kumar
* @Group              : 
* @Last Modified By   : abhishek.kumar@absyz.com
* @Modification Log   : 
* Ver       Date            Author      		    Modification
* 1.0    19/10/2019   	Abhishek Kumar     				1.0
**/
public with sharing class Modal_LWC_controller {
    
    @AuraEnabled(cacheable=true)
    public static WrapperClass fetchWrapperData(Id sObjectId){
        WrapperClass wrapperClassVar = new WrapperClass();
        if(sObjectId.getSobjectType() == Schema.Account.SObjectType){
            wrapperClassVar.contactList = Modal_LWC_controller.getRelatedContacts(sObjectId);
        }else if(sObjectId.getSobjectType() == Schema.Contact.SObjectType){
            wrapperClassVar.accId = Modal_LWC_controller.getAccId(sObjectId);
        }
        System.debug('wrapperClassVar-->>'+wrapperClassVar);
        return wrapperClassVar;
    }
    
    public static List getRelatedContacts(String accId){
        return [SELECT Id, Name, Phone, Email FROM Contact WHERE AccountId =:accId];
    }
        
    public static String getAccId(String contactId) {
        return [SELECT Id, AccountId FROM Contact WHERE Id=:contactId].AccountId; 
    }
    
    public class WrapperClass {
        @AuraEnabled
        public List contactList {get; set;}
        @AuraEnabled
        public Id accId{get; set;}
        
        public wrapperClass() {
            this.contactList = new List();
        }
    }
}

LWC Components

modal_LWC.html

modal_LWC.js

import { LightningElement, track, api } from 'lwc';
import { ShowToastEvent } from 'lightning/platformShowToastEvent'
import fetchWrapperData from '@salesforce/apex/Modal_LWC_controller.fetchWrapperData';

const columns = [
  { label: 'Name', fieldName: 'Name' },
  { label: 'Email', fieldName: 'Email', type: 'email' },
  { label: 'Phone', fieldName: 'Phone', type: 'phone' }
];

export default class Modal_LWC extends LightningElement {
  @track columns = columns;   
  @track accountId; 
  @track contactList;
  @track rowOffset = 0;
  @track error;   
  @track btnLabel = '';   
  @track modalHeader = '';
  @track isContact = false;
  @track modalClass = 'slds-modal ';
  @track modalBackdropClass = 'slds-backdrop ';
  @api recordId;  //Stores recordId
  @api objectApiName;   //Stores the current object API Name

  connectedCallback() {   //doInit() function, Dynamically changing the modal header and button label as per sObject, and also assigning the isContact property as per sObject
    if(this.objectApiName === 'Account'){
      this.isContact = false;
      this.modalHeader = 'Related Contacts';
      this.btnLabel = 'See Related Contacts';
    }else if(this.objectApiName === 'Contact'){
      this.isContact = true;
      this.modalHeader = 'Account Details';
      this.btnLabel = 'See Account Details';
    }
  }

  //Adds the classes that shows the Modal and does server calls to show the required data
  openModal() {
    this.modalClass = 'slds-modal slds-fade-in-open';
    this.modalBackdropClass = 'slds-backdrop slds-backdrop_open';
    fetchWrapperData({sObjectId: this.recordId})
      .then(result => {    //Returns the wrapper 
        if(result.accId != null){
          this.accountId = result.accId;
          this.isContact = true;
        }else{
          this.contactList = result.contactList;
          this.isContact = false;
        }
      })
      .catch(error => {
        const event = new ShowToastEvent({
          title: 'Error Occured',
          message: 'Error: '+error.body.message,
          variant: 'error'
         });
        this.dispatchEvent(event);    //To show an error Taost if error occurred while the APEX call
        });
  }

  //Removes the classes that hides the Modal
  closeModal() {
    this.modalClass = 'slds-modal ';
    this.modalBackdropClass = 'slds-backdrop ';
  }
}

Alternatively, we can use

FSL Admin	FSL Admin License FSL Admin Permissions
FSL Agent	FSL Agent License FSL Agent Permissions
FSL Dispatcher	FSL Dispatcher License FSL Dispatcher Permissions
FSL Resource	FSL Mobile License FSL Scheduling License FSL Resource Permissions

Lightning – ABSYZ

Drive User Action with Floating Prompts in Lightning Experience

Review Org-Wide Prompt Settings

Setting up a Floating Prompt

The Authoring Bar

Add a New Prompt: Select Type & Position

Visibility

Add Content

Scheduling

Add remaining details & Preview

User Interaction & its impact on Floating Prompt’s Occurrences

Conclusion

Summer’20 Release Treasure Hunt: Top Features

1. Flows

1.1 Before/After Handling in Flow Triggers

1.2 Run Flows in System Mode

1.3 Flow Loop Variables are Automatically Created

1.4 Roll back Mode in Flow Debugger

2. Lightning

2.1 Navigate to a record page with default values

2.2 Empty the Recycle Bin in One Step

2.3 Split View in Standard Navigation

2.4 Source Tracking in Sandboxes

3. Development

3.1 The @track decorator is no longer needed to make the Lightning Web Component Class Reactive

3.2 Style Lightning Web Components with Custom Aura Design Tokens

3.3 Smarter Source Tracking for Lightning Web Components in Scratch Orgs

3.4 DOM API Changes May Require UI Test Updates

4. Reports and Dashboards

5. Federation Id can be made case sensitive

6. AWS Private Link

Outlook connection with Salesforce through custom Objects

Set Up Lightning for Outlook in the Microsoft Outlook

Lightning for Outlook and Lightning Sync from Salesforce

Outlook Connection Establishment:

Limitations for creating Global action in salesforce.

Displaying standard report data in Lightning component

Apex code

Aura component

Using Modal/ Popup in Lightning Web Components

Apex Class

LWC Components

Account Record Page:

Contact Record Page:

LWC with Aura Components,Calling controller from LWC,LDS in LWC

Calling controller from LWC:

Import Syntax

1.Wire a property:

2.Wire a function:

3.Call a method imperatively:

Lightning Web Components with Aura Components:

LDS in Lightning Web Component:

Create Record through LDS :

Top Highlights of Salesforce Winter’20 Release: Part II

Development:

1.Lightning web components open source:

2. Add Lightning Web Components as Tabs:

3. Communicate Across Salesforce UI Technologies with Lightning Message Service :

4. Launch into Lightning Experience Apps with the Mobile App Launcher:

5. Navigate Users directly to an App:

Lightning Flows:

1.Start a Flow on a Schedule:

Salesforce CLI: New and Changed Commands:

1. Discover New and Changed CLI Commands:

Query in Bulk API 2.0 :

Protect Your Salesforce App with Enhanced Mobile Security:

Generally Available Updates:

1. Make Your List Views Stay on Topic with Topic Filters:

2. Save Ink and Paper with Printable View for Lists:

3. Complete Tasks in a Single Click:

4. Find Email File Attachments in One Click:

5. Scan and Scroll the Activity Timeline:

6. Track Setup Changes Made to Connected App Policies and Settings:

Field Service Lightning

Components of Field Service Lightning:

Setup and Working of Field Service Lightning:

1)FSL Admin:

Enable & Installing Field Service Lightning:

Setting up FSL:

2)FSL Agent:

Write a Javascript test suite
Components for Testing