Import existing Salesforce project in Visual Studio Code

This blog post describes how to import an existing Salesforce projects in Visual Studio Code. Primarily this process will consists 3 major steps such as creating project, authorizing an org and importing all existing components. Before creating project we should have installed salesforce extensions pack for Visual Studio code and also Salesforce CLI and JDK 8 is must in order to work these extensions. The Visual Studio Code can run SFDX commands from its terminal. After installing the extension pack. The first step is to create project.Always Choose the option to create a project with manifest because when you do create a project with manifest it will populate some files for you such as package.xml with apex classes and triggers and Ltng Components. Once created the project in local we need to authorize/connect Salesforce Org to the project. To do this type Ctrl+Shift+P  and choose SFDX:Authorize an Org command from command palette and choose instance url either for Sandbox or dev org. Leave the org alias empty and click enter and this action will open the Salesforce login screen in browser and once done After successful authorization next step is to import all metadata to our local/Visual Studio Code. Check the package.xml file in project tree and then right click on it and choose the command SFDX: Retrieve Source in Manifest from Org and this action can also be done from command palette when package.xml file is open. This is the only action, even just in case we want to import newly created metadata components  by other developers during development  from org  . The command SFDX:Retrieve Source from Org will only refresh the existing meta data components from updated versions in Org and it won't import newly created metadata components such as classes etc to local. Note: While setting up JDK 8, the JAVA_HOME system variable is necessary. Resources: Quick Start: Visual Studio Code for Salesforce Development Org Development Model Salesforce Extension Pack Cheers!!...

This blog post describes how to import an existing Salesforce projects in Visual Studio Code . Primarily this process will consists 3 major...

Launch/invoke flow from process builder and update child records with Flow

In this post for easier grasping I took the basic example of updating child records when parent updated. To achieve this I took a two checkbox custom fields "Read Only Account" on Account object and another custom field "Read Only Contact" on contact object. So when ever the account's field "Read Only Account" is set to true/checked then the related all contacts' field "Read Only Contact" will get updated to true/checked. The contact update part is implemented in Flow builder and this flow is invoked from process builder which is fired/invoked when account is updated. Process builder to invoke the Flow when "Read Only Account" field on Account is checked. Make sure the "accId" flow variable is set to "allow input" from out side the flow when creating flow. Created an Auto Launched flow with 3 different actions including getting/query contacts and iterating them, change field "Read Only Contact" to checked/true and then updating them in the final stage after iterating all items in loop. Ensure the loop is closed always after certain operations or assignments completed and then invoke other actions such as updates after last item finished in loop. The break down of each stage is mentioned  in the below pictures and I skipped few steps such as creating flow variables and choosing data types. However, in this flow we use text, list of contacts and contact data types mostly. It makes sense for us which data type should we choose, when we explore the flow builder more . In the above stage make sure "accId" flow variable is set take input from outside the flow. Specify fields to query and create a list of contacts variable to hold query returned records. Iterate contacts and holding each record in a loop variable of contact type  Setting field "Read Only Contact" on contact to True and adding it to a list. At this point avoid simply adding loop variable to a list for update, this doesn't work. We need to capture the fields need to update into another variable in this case variable {!tempConToUpdate} and then add this variable to a list. Never forget the Id field is required in an update call. Updating contacts by passing previously populated list from assignment stage. Cheers!!!...

In this post for easier grasping I took the basic example of updating child records when parent updated. To achieve this I took a two check...

Embed Lightning component in Flows and passing data between flow and Ltng Component

This blog post explains how to embed/place/use lightning component in Screen Flow. The Lightning component which will be used in Flow must implement interface lightning:availableForFlowScreens. Let's take a basic example with a contact insertion using screen flow. In this example, the lightning component is used a account look up search field. Screen Flow preview To demonstrate this approach in a simple way I took lightning data services tag lightning:recordEditForm and to avoid complexity. The attributes specified in design:component will be accessible from flow. When these design attributes are mapped/connected to flow variables, the lightning component even can restore the field values from paused flows. This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters Show hidden characters <aura:component implements="lightning:availableForFlowScreens" access="global"> <aura:attribute name="greeting" type="String" access="global" default="this is for test!!"/> <aura:attribute name="recId" type="String" access="global" /> <lightning:recordEditForm aura:id="recordViewForm" objectApiName="Contact"> <!-- the messages component is for error messages --> <lightning:messages /> <lightning:inputField value="{!v.recId}" aura:id="accId" fieldName="AccountId" onchange="{! c.onAccountChange}"/> </lightning:recordEditForm> </aura:component> view raw AccSearchCmp.xml hosted with ❤ by GitHub This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters Show hidden characters ({ onAccountChange : function(component, event, helper) { var recId = component.find("accId").get("v.value"); component.set("v.recId", recId); } }) view raw AccSearchCmpController.js hosted with ❤ by GitHub This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters Show hidden characters <design:component> <design:attribute name="recId" label="Account Id" /> </design:component> view raw AccSearchCmpDesign.xml hosted with ❤ by GitHub Once created the Lightning component then create a Screen flow to insert a Contact. Drag and drop the Lightning component created in previous step. Provide mapping for lightning component variables which are from design attribute section, to the Flow variables. The input and output variables mapping in flow will ensures the Lightning component loads the saved data when flow paused. The flow variable {!acRecId} in this case holds the account Id selected in Lightning component and makes it available for Insert contact stage in flow even user comes back to paused flows. Add other text fields such as email and phone of contact to the flow screen and provide mapping in the final contact insert stage as mentioned below screenshots. Adding Lightning component and other text fields in screen flow. Drag and drop the create records action from flow actions and provide mapping for inserting contact record from flow input fields and variables. Cheers!!!...

This blog post explains how to embed/place/use lightning component in Screen Flow. The Lightning component which will be used in Flow must ...

Navigate users to record detail after finishing Screen Flow

This blog post demonstrates how to navigate a user to record detail automatically after finishing the flow. This can be achieved with a a custom Lightning Component which can accessible in side the flow. The standard Lightning interfaces force:lightningQuickAction and lightning:availableForFlowActions will make the lightning component is accessible from core actions section in Flow builder. Let's create a Lightning Component that can be accessible inside the flow and can be accessible for core actions in flow. Create a lightning component as specified below. The invoke method in the controller js will be fired automatically when flow invokes the lightning component. This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters Show hidden characters <aura:component implements="force:lightningQuickAction,lightning:availableForFlowActions"> <aura:attribute name="recordId" type="String" /> </aura:component> view raw NavigateToRecord.xml hosted with ❤ by GitHub This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters Show hidden characters ({ invoke : function(component, event, helper) { var recId = component.get("v.recordId"); // Get the standard Lightning event navigateToSObject var redirect = $A.get("e.force:navigateToSObject"); redirect.setParams({ "recordId": recId }); redirect.fire(); }}) view raw NavigateToRecordController.js hosted with ❤ by GitHub This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters Show hidden characters <design:component> <design:attribute name="recordId" label="Record ID" /> </design:component> view raw NavigateToRecordDesign.xml hosted with ❤ by GitHub Let's create flow now, To avoid complexity let's consider a basic contact insertion with a screen flow.  A new contact screen in flow builder. Let's build a form with flow builder with contact first name, last name. mobile and phone. First Drag and drop a screen component from flow builder and add all text components for above mentioned fields in new contact form. In the next step, drag and drop the create records action from flow builder and select contact object for insertion and also map all the text fields values(no flow variables required) from previous screen flow to contact object fields in current screen. Also create a variable to hold record Id of contact after insertion as in below screenshot {!contactId}. While creating this variable make sure you did not provided any default value for variable and avoid "Available for input" option in flow variable screen or else flow will throws an error. In the final step, drag and drop the Core Actions action from flow builder and choose the lightning component that we created initially and provide mapping for record Id in the Lightning component from the flow variable contactId which consists a inserted contact Id.   We can preview this screen flow from app builder. Just go to app builder from Lightning Quick find side bar in setup and create an App Page from app builder and drag and drop your screen flow. Once created an app page we can access it from app launcher search bar....

This blog post demonstrates how to navigate a user to record detail automatically after finishing the flow. This can be achieved with a a c...

Using trigger events / context variables with enum System.TriggerOperation

In summer'18 release Salesforce has first introduced enum System.TriggerOperation which consists specific set of trigger context variables AFTER_DELETE, AFTER_INSERT, AFTER_UNDELETE, AFTER_UPDATE, BEFORE_DELETE, BEFORE_INSERT,BEFORE_UPDATE. This enum makes life easy for developer from using different context variables like triger.isAfter and trigger.isInsert with a bunch of AND statements and IF statements. The new Trigger context variable Trigger.operationType  will returns an enum System.TriggerOperation during trigger context. With this enum we can easily identify the current trigger context and can invoke our logic from handlers. This enum can also be used with in a trigger handler class. The simple snippet below demonstrates using this enum with a switch statement. This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters Show hidden characters trigger AccountTrigger on Account (before insert, before update, after update){ system.debug(Trigger.operationType); switch on Trigger.operationType { when BEFORE_INSERT { //Invoke before insert trigger handler system.debug('--BEFORE_INSERT---'); } when BEFORE_UPDATE { //Invoke before insert trigger handler system.debug('--BEFORE_UPDATE---'); } when AFTER_UPDATE { //Invoke before insert trigger handler system.debug('--AFTER_UPDATE---'); } } } view raw AccountTrigger.java hosted with ❤ by GitHub Result in debug logs when updated a record on Account object. Happy coding, cheers!!! Resources: Releases notes Spring'19 TriggerOperation Enum...

In summer'18 release Salesforce has first introduced   enum System.TriggerOperation which consists specific set of trigger context vari...

Lightning Component for Sending Email for List View Selected Records and using Email Templates

Hi there, At the time of this blog post, There is no standard Lightning component available for Email composer, So I created a custom component for sending Email and mimic of the standard email composer and also for sending Listview selected records. I assumed sending email for person accounts (person accounts by default not available in salesforce you have to rise a case to enable them) of Opportunities. Please choose different object for sending(from contact List view)  since if you don't have person accounts enabled you will get compile errors. You also need to create a rich text field in any object since we don't have standard richtext tags in lighting at the time of posting this blog post. We need rich text field to mimic the email composer screen and also to render the text review of template selected. I have used a List view button of type visualforce in opportunities List view and in visualforce page i have placed Lightning Component. The list view selected records will be sent to Lightning Component. Get the snippets below to image. Visualforce Page: This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters Show hidden characters <apex:page standardController="Opportunity" action="{!doSomething}" recordSetVar="opportunities" tabStyle="Opportunity" extensions="ListEmaillOppController"> <apex:includeLightning /> <apex:slds /> <style> .close-btn{text-align: right;color: white;font-size: 20px;padding: 0.5%;cursor: pointer;} </style> <script src="https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js"></script> <script> var myUserContext = "{!$User.UITheme}"; var accIds = "{!accIdStr}"; var oppIds = "{!oppIdStr}"; var visualForceFunction = function(){ if (myUserContext == 'Theme4t' || myUserContext == 'Theme4d') { // The Visualforce page is in S1 or Lightning Experience sforce.one.navigateToURL("/006/o"); } else if (myUserContext == 'Theme3') { // The Visualforce page is running in Classic window.top.location.href = '{!$Label.OrgUrl}'+'006/o'; } else { console.log("Unsupported theme"); } }; $Lightning.use("c:SendListEmailOnOpp", function() { console.log('lead Id', '{!$CurrentPage.parameters.Id}'); $Lightning.createComponent("c:ListEmailOpp",{"accIds" : accIds, "oppIds" : oppIds},"lightning",function(cmp) { $('.close-btn').click(function(){ visualForceFunction(); }); $A.eventService.addHandler({ event: 'force:navigateToURL', handler: function(event) { visualForceFunction(); } }); }); }); </script> <input type="hidden" id="leadHiddenId" value="{!$CurrentPage.parameters.Id}"/> <div class="demo-only" style="height: 640px;"> <section role="dialog" tabindex="-1" aria-labelledby="modal-heading-01" aria-modal="true" aria-describedby="modal-content-id-1" class="slds-modal slds-fade-in-open"> <div class="slds-modal__container"> <span class="close-btn">X</span> <div class="slds-modal__content slds-p-around_medium" id="lightning"> </div> </div> </section> <div class="slds-backdrop slds-backdrop_open"></div> </div> </apex:page> view raw ListEmailPage.xml hosted with ❤ by GitHub Controller Extension: This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters Show hidden characters /* Class name : ListEmaillOppController, Created By : Anil Kumar Description : Enhancements : */ public class ListEmaillOppController { private ApexPages.StandardSetController standardSetController; public string accIdStr{get;set;} public string oppIdStr{get;set;} public ListEmaillOppController(ApexPages.StandardSetController standardSetController) { this.standardSetController = standardSetController; accIdStr=''; } public PageReference doSomething() { // Apex code for handling records from a List View goes here List<Opportunity> selectedListViewRecords = (List<Opportunity>) standardSetController.getSelected(); Boolean hasMore = standardSetController.getHasNext(); if(selectedListViewRecords.size()>0){ list<string> accIds = new list<string>(); list<string> oppIds = new list<string>(); for(Opportunity oppRec : [select id,accountId from Opportunity WHERE Id IN: selectedListViewRecords]){ accIds.add(oppRec.accountId); oppIds.add(oppRec.Id); } accIdStr = accIds.size()>0 ? String.join(accIds, ',') : ''; oppIdStr= oppIds.size()>0 ? String.join(oppIds, ',') : ''; } system.debug('---selectedListViewRecords ---'+selectedListViewRecords.size() ); return null; } } view raw ListEmaillOppController.java hosted with ❤ by GitHub EmailComp: This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters Show hidden characters <aura:component controller="ListEmailOppCntrlr" implements="force:hasRecordId,flexipage:availableForAllPageTypes,force:lightningQuickActionWithoutHeader" access="global"> <aura:handler name="init" value="{!this}" action="{!c.loadComponent}"/> <aura:attribute name="errorMsg" type="String" description=""/> <aura:attribute name="shoMsg" type="boolean" default="false" description=""/> <aura:attribute name="shwSucesMsg" type="boolean" default="false" description=""/> <aura:attribute name="showLoader" type="boolean" default="false" description=""/> <aura:attribute name="Opportunity" type="Opportunity" default="{ 'sobjectType': 'Opportunity', 'SampleRichText__c':''}"/> <aura:attribute name="disableTemplate" type="boolean" default="false" description=""/> <aura:attribute name="selTempl" type="String" description=""/> <aura:attribute name="templates" type="EmailTemplate[]" default="[]"/> <aura:attribute name="addnlEmails" type="String" default="" description=""/> <aura:attribute name="subjTxt" type="String" default="" description=""/> <aura:attribute name="msgReview" type="String" default="" description=""/> <aura:attribute name="accIds" type="String" access="GLOBAL" default="" description=""/> <aura:attribute name="oppIds" type="String" access="GLOBAL" default="" description=""/> <aura:attribute name="accRecords" type="sObject[]" default="[]" /> <aura:attribute name="templDetail" type="EmailTemplate" default="{}" /> <div class="slds-page-header" role="banner"> <div class="slds-grid"> <div class="slds-col slds-has-flexi-truncate"> <!-- SEARCH AREA --> <p class="slds-text-title--caps slds-line-height--reset"> <span title="lead Standard Icon"> </span>&nbsp;&nbsp;Send Email</p> <!-- / SEARCH AREA --> </div> </div> </div> <br/><br/> <!-- Connection 1 Section --> <div class="slds-grid slds-grid_vertical"> <div class="slds-box slds-box--small slds-theme--shade slds-text-align--left">Email Message</div> <br/> <div class="slds-col"> <div class="slds-form-element slds-size--1-of-1"> <!-- <label class="slds-form-element__label" for="input-02">Recipients<span color="red"><b>*</b></span></label> --> <!-- <input type="Text" autocomplete="off" style="border-left:4px solid red;" value="" class="slds-input" /> --> <c:reUsableMultiSelectLookup objectAPIName="account" IconName="standard:account" lstSelectedRecords="{!v.accRecords}" label="Recipients" aura:id="lookupRes" /> </div> </div> <br/><br/> <div class="slds-col"> <lightning:select disabled="{!v.disableTemplate}" onchange="{!c.loadTemplate}" name="SelectDivision" label="Select a Template:" aura:id="templateId" value="{!v.selTempl}"> <option text="None" value=""/> <aura:iteration items="{!v.templates}" var="item"> <option text="{!item.Name}" value="{!item.Id}"/> </aura:iteration> </lightning:select> </div> <br/><br/> <div class="slds-col"> <div class="slds-form-element slds-size--1-of-1"> <label class="slds-form-element__label" for="input-02">Subject:</label> <input id="subjMatter" type="Text" autocomplete="off" value="{!v.subjTxt}" class="slds-input" /> </div> </div><br/><br/> <div class="slds-col" aura:id="emailBodyDiv"> <div class="slds-form-element slds-size--1-of-1"> <label class="slds-form-element__label" for="input-02">Content :</label> <span></span> <force:inputField class="richTxt" value="{!v.Opportunity.SampleRichText__c}"/> </div> </div><br/><br/> <aura:if isTrue="{!!empty(v.selTempl)}" > <lightning:textarea name="myTextArea" value="{!v.templDetail.Body}" label="Content:" maxlength="700" class="txtAreaCls" disabled="true" /> <br/><br/> </aura:if> </div> <br/> <!-- Error message area --> <br/><br/> <aura:if isTrue="{!v.shoMsg}" > <ui:message aura:id="errPanel" title="Error" severity="error" closable="false"> {!v.errorMsg} </ui:message> <br/><br/> </aura:if> <aura:if isTrue="{!v.shwSucesMsg}" > <ui:message aura:id="errPanel" title="Success!" severity="confirm" closable="false"> Email has been sent! </ui:message> <br/><br/> </aura:if> <!-- Buttons and Loader section --> <div class="slds-align_absolute-center " style="padding:2%;"> <lightning:button variant="brand" label="Send Email" onclick="{!c.sendEmailAction}" /> <input type="button" value="Cancel" class="slds-button slds-button--neutral" onclick="{!c.closeDialog}"/> <aura:if isTrue="{!v.showLoader}"> <div class="demo-only" style="height: 6rem;"> <div role="status" class="slds-spinner_brand slds-spinner slds-spinner_small"> <span class="slds-assistive-text">Loading</span> <div class="slds-spinner__dot-a"></div> <div class="slds-spinner__dot-b"></div> </div> </div> </aura:if> </div> </aura:component> view raw ListEmailComp.xml hosted with ❤ by GitHub Controller.js: This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters Show hidden characters ({ loadComponent : function(component, event, helper) { helper.getSelctedAccountsOfOpportunity(component, event); helper.getEmailTempaltes(component, event); console.log(component.get("v.accIds")); }, sendEmailAction : function(component, event, helper) { helper.sendEmails(component, event); }, loadTemplate : function(component, event, helper) { helper.getTemplate(component, event); }, closeDialog : function(component, event, helper) { helper.cancelAction(component, event); } }) view raw ListEmailCompController.js hosted with ❤ by GitHub Helper.js: This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters Show hidden characters ({ getEmailTempaltes : function(component, event) { var action = component.get("c.getTemplates"); //action.setParams({"divisionId":selectedDivision}); action.setCallback(this,function(response){ var loadResponse = response.getReturnValue(); console.log('templates..!',loadResponse); if(!$A.util.isEmpty(loadResponse)){ component.set('v.templates',loadResponse); } }); $A.enqueueAction(action); }, getSelctedAccountsOfOpportunity : function(component, event) { var accIdsofOpp = component.get("v.accIds"); if(!$A.util.isEmpty(accIdsofOpp)){ var action = component.get("c.getAccountsOfOpportunity"); action.setParams({"accIds":accIdsofOpp}); action.setCallback(this,function(response){ var responseVal = response.getReturnValue(); console.log('responseVal..** ',responseVal); if(!$A.util.isEmpty(responseVal)){ component.set("v.accRecords",responseVal); } }); $A.enqueueAction(action); } }, sendEmails : function(component, event) { component.set("v.shoMsg", false); component.set("v.showLoader", true); var selRec = component.find("lookupRes").get("v.lstSelectedRecords"); var templateId = component.get("v.selTempl"); var oppRecIds = component.get("v.oppIds"); console.log('oppRecIds ', oppRecIds); console.log('sel records ', selRec); console.log('sel template ', templateId); //var addnlEmails = document.getElementById("addnlEmail").value; var subjMatter = document.getElementById("subjMatter").value; console.log('subjMatter ',subjMatter); var emailBody = !$A.util.isEmpty(component.get("v.Opportunity").SampleRichText__c) ? component.get("v.Opportunity").SampleRichText__c : ''; console.log('emailBody ',emailBody); if(!$A.util.isEmpty(selRec) && (!$A.util.isEmpty(emailBody) || !$A.util.isEmpty(templateId)) ){ var accIds = []; for (var i = 0; i<selRec.length; i++) { accIds.push(selRec[i].PersonContactId); } console.log('---accIds--- ', accIds); var accIdStr = !$A.util.isEmpty(accIds) ? accIds.join() : ''; console.log('---accIdStr--- ', accIdStr); if(!$A.util.isEmpty(accIdStr) || !$A.util.isEmpty(addnlEmails)){ console.log('---accIdStr--- ', accIdStr); console.log('--Opportunity--', component.get("v.Opportunity")); var action = component.get("c.sendAnEmailMsg"); action.setParams({"templateId":templateId, "accIds":!$A.util.isEmpty(accIdStr) ? accIdStr : '', "opty":component.get("v.Opportunity"), "subj" : !$A.util.isEmpty(subjMatter) ? subjMatter : '', "addnlEmails" : '', "oppIds" : oppRecIds }); action.setCallback(this,function(response){ var emailMsgResp = response.getReturnValue(); console.log('--emailMsgResp--', emailMsgResp); //isSuccess errMsg component.set("v.showLoader", false); if(emailMsgResp.isSuccess){ component.set("v.shwSucesMsg", true); this.cancelAction(component, event); } else { component.set("v.shoMsg", true); component.set("v.errorMsg", emailMsgResp.errMsg); } }); $A.enqueueAction(action); } } else { component.set("v.showLoader", false); component.set("v.shoMsg", true); component.set("v.errorMsg", "Please provide Recipient, Template or Email Body"); } }, getTemplate : function(component, event) { var templId = component.get("v.selTempl"); component.set("v.showLoader", true); if(!$A.util.isEmpty(templId)){ var action = component.get("c.getTemplateDetails"); action.setParams({"templteId":templId}); action.setCallback(this,function(response){ component.set("v.showLoader", false); var responseVal = response.getReturnValue(); console.log('responseVal..@getTemplate ',responseVal); if(!$A.util.isEmpty(responseVal)){ component.set("v.templDetail",responseVal); component.set("v.subjTxt",responseVal.Subject); if(!$A.util.hasClass(component.find("emailBodyDiv"), "slds-hide")){ $A.util.addClass(component.find("emailBodyDiv"), 'slds-hide'); } } }); $A.enqueueAction(action); } else { component.set("v.showLoader", false); if($A.util.hasClass(component.find("emailBodyDiv"), "slds-hide")){ $A.util.removeClass(component.find("emailBodyDiv"), 'slds-hide'); } } }, cancelAction: function(component, event){ var urlEvent = $A.get("e.force:navigateToURL"); urlEvent.setParams({ "url": '/006/o' }); urlEvent.fire() } }) view raw ListEmailCompHelper.js hosted with ❤ by GitHub EmailComp Apex Class: This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters Show hidden characters public class ListEmailOppCntrlr { @AuraEnabled public static list<EmailTemplate> getTemplates(){ //RelatedEntityType='Account' AND list<EmailTemplate> emailTemp = new list<EmailTemplate>(); emailTemp = [SELECT Id,Name,Subject,TemplateType FROM EmailTemplate WHERE TemplateType IN ('custom','text')]; return emailTemp; } @AuraEnabled public static list<Account> getAccountsOfOpportunity(string accIds){ list<string> accIdsList = string.isNotBlank(accIds) ? accIds.split(',') : new list<string>(); list<Account> accRecords = accIdsList.size()>0 ? [SELECT Id,Name,PersonContactId FROM Account WHERE ID IN:accIdsList] : new list<Account>(); return accRecords; } @AuraEnabled public static EmailTemplate getTemplateDetails(string templteId){ EmailTemplate emailTemp = new EmailTemplate(); list<EmailTemplate> emailTempLst = new list<EmailTemplate>(); emailTempLst = [SELECT Id,Name,Subject,TemplateType,body FROM EmailTemplate WHERE ID=: templteId]; emailTemp = emailTempLst.size()>0 ? emailTempLst[0] : emailTemp; return emailTemp; } @AuraEnabled public static sucesMsg sendAnEmailMsg(string templateId, string accIds, opportunity opty, string subj, string addnlEmails, string oppIds){ try { List<Messaging.SingleEmailMessage> mails = new List<Messaging.SingleEmailMessage>(); Map<Id,Account> accMap = new map<Id,Account>(); list<Opportunity> oppList = new list<Opportunity>(); list<string> accIdList = string.isNotBlank(accIds) ? accIds.split(',') : new list<string>(); list<string> oppIdList = string.isNotBlank(oppIds) ? oppIds.split(',') : new list<string>(); list<string> addnlEmailList = string.isNotBlank(addnlEmails) ? addnlEmails.split(',') : new list<string>(); system.debug('---accIdList-- '+accIdList); system.debug('---templateId--- '+templateId); system.debug('---oppIdList--- '+oppIdList); if(accIdList.size()>0 && oppIdList.size()>0) { accMap = new Map<Id,Account>([select id,name,personEmail,PersonContactId from Account WHERE PersonContactId IN: accIdList]); oppList = [select id,AccountId from Opportunity WHERE ID IN: oppIdList]; for(opportunity oppRec : oppList) { if(oppRec.accountId!=null && accMap.containsKey(oppRec.AccountId)) { Account persnAcc = accMap.get(oppRec.AccountId); if (persnAcc.personEmail != null) { Messaging.SingleEmailMessage mail = new Messaging.SingleEmailMessage(); if(string.isNotBlank(templateId)){ mail.setTemplateId(ID.valueOf(templateId));//00XW0000000MjvI 00XW0000000MjuyMAC mail.setTargetObjectId(persnAcc.PersonContactId); mail.saveAsActivity=true; mail.setWhatId(oppRec.id); //006W000000DYyeL } else if(string.isNotBlank(opty.SampleRichText__c)){ mail.setSubject(string.isNotBlank(subj) ? subj : ''); List<String> sendTo = new List<String>(); sendTo.add(persnAcc.personEmail); mail.setToAddresses(sendTo); mail.setHtmlBody(opty.SampleRichText__c); mail.saveAsActivity=true; mail.setWhatId(oppRec.id); } // Step 5. Add your email to the master list mails.add(mail); } } } } if(mails.size()>0){ try { Messaging.sendEmail(mails); return new sucesMsg(true, 'Sucess!'); } catch(Exception e) { system.debug('*************--Exception @SendEmail method ---*********'); System.debug('****--Exception type caught: ' + e.getTypeName()); System.debug('****--Message: ' + e.getMessage()); System.debug('****--Cause: ' + e.getCause()); System.debug('****--Line number: ' + e.getLineNumber()); System.debug('****--Stack trace: ' + e.getStackTraceString()); return new sucesMsg(false, e.getMessage()+' - '+e.getCause()+' - '+e.getStackTraceString()+' - '+e.getLineNumber()); } } return new sucesMsg(true, 'Sucess!'); } catch(Exception e) { system.debug('*************--Exception @sendAnEmailMsg method ---*********'); System.debug('****--Exception type caught: ' + e.getTypeName()); System.debug('****--Message: ' + e.getMessage()); System.debug('****--Cause: ' + e.getCause()); System.debug('****--Line number: ' + e.getLineNumber()); System.debug('****--Stack trace: ' + e.getStackTraceString()); return new sucesMsg(false, e.getMessage()+' - '+e.getCause()+' - '+e.getStackTraceString()+' - '+e.getLineNumber()); } } public class sucesMsg { @AuraEnabled public boolean isSuccess; @AuraEnabled public string errMsg; public sucesMsg(boolean isSuccess, string errMsg){ this.isSuccess = isSuccess; this.errMsg = errMsg; } } } view raw ListEmailOppCntrlr.java hosted with ❤ by GitHub I did not mentioned the snippet for the component "c:reUsableMultiSelectLookup" here. Because it is a custom look up component that can be available from many places like salesforce forums and blogs. All you need to do is to tweak the init section of your look up component by passing the selected items to display them automatically. ...

Hi there, At the time of this blog post, There is no standard Lightning component available for Email composer, So I created a custom compo...

Formula Field to calculate hours from Date Time field in Salesforce

Hey there, This is sample formula field to get difference in hours from date time field to current time. I have considered Event standard field ActivityDateTime to calculate hours in this example See formula below screenshot. formula: This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters Show hidden characters (FLOOR(( NOW() - ActivityDateTime)*24)) + FLOOR(((( ((NOW() - ActivityDateTime )*24)- FLOOR((NOW() - ActivityDateTime)*24)) *60)/100)) view raw sampleFormulaHours.java hosted with ❤ by GitHub...

Hey there, This is sample formula field to get difference in hours from date time field to current time. I have considered Event standard...