[Sumit]

With flow triggers, you can automate complex business processes—create flows to perform logic, and have events trigger the flows via workflow rules—without writing code. For example, your flow looks up and assigns the relevant entitlement for a case.

[Sumit]

1. From Setup, click Create | Workflow & Approvals | Flows and open a new or existing flow.
2. From the Palette, drag the Fast Lookup element onto the canvas.
3. Enter the general settings for the element.

[Sumit]

1. Create a new Flow with Salesforce as the Service used for identity.
2. Drag a Data Load element into the Flow.
3. Create a new Data Action.
4. For the Value to load, either select a Value of Kind: Object, Type: Contact or create a new Value of Kind: Object, Type: Contact.
5. Use the Contact binding for loading the data.

[Sumit]

You can find base Lightning components in the lightning namespace to complement the existing ui namespace components. In instances where there are matching ui and lightning namespace components, we recommend that you use the lightning namespace component. The lightning namespace components are optimized for common use cases. Beyond being equipped with the Lightning Design System styling, they handle accessibility, real-time interaction, and enhanced error messages.

[Sumit]

soapUI is most common tool available to test Soap based web services, it also has capability to test REST web services. soapUI can be used to test Partner WSDL, enterprise WSDL, Tooling API, Metadata API to study capability and response from Salesforce before writing any code in Java, C# or any other language.

[Sumit]

Single sign-on (SSO) lets users access authorized network resources with one login. You validate usernames and passwords against your corporate user database or other client app rather than Salesforce managing separate passwords for each resource

[Sumit]

Use 'force:hasRecordId' interface in your lightning component and set the params-action.setParams({"accountId": component.get("v.recordId")});

[Sumit]

Order of Execution: It is a sequence of events that occur when a record is saved in Salesforce. These events are executed when an insert, update, or upsert operation occurs. All events need to <b style="font-family: inherit; font-size: inherit;">execute successfully before the data is committed to the database.

[Sumit]

There can be only one @testSetup method per test class.

[Sumit]

Test.setCreatedDate is used when you want to set CreatedDate for a test-context sObject. This method takes two parameters—an sObject ID and a Datetime value—neither of which can be null.

[Sumit]

• It does not support bulk record operations. ( ...
• If record gets updated from outside page, like using Dataloader or some other user, it will not be refreshed. ...
• Not all standard objects are supported (at the time of writing this post)
• Its not yet GA.

[Sumit]

To create a record using Lightning Data Service, declare force:recordData without assigning a recordId. Next, load a record template by calling the getNewRecord function on force:recordData. Finally, apply values to the new record, and save the record by calling the saveRecord function on force:recordData.

[Sumit]

FlexiPage represents the metadata associated with a Lightning page. A Lightning page represents a customizable screen made up of regions containing Lightning components. FlexiPage components have the suffix .flexipage and are stored in the flexipages folder.

[Sumit]

<div>If we use the DML statement (Insert) in bulk operation, then if error occurs the execution will stop. In that case Apex code throws an error and none of the record will insert to the database.</div>If we use DML database methods (Database.Insert) in bulk operation, then if error occurs the remaining records will be inserted/updated means partial DML operation will be done. The only record throwing an error will not be inserted/updated.

[Sumit]

Several examples of Lightning Base components: badge, button, buttonGroup, buttonIcon, buttonMenu, card, formattedDateTime, formattedNumber

[Sumit]

Hello Marziya,Lightning Data Service is built on a publically accessible API called: User Interface API.

[Sumit]

<div eid="8jckX_TICt2M1fAPqsekuAs" data-async-context="query:What%20is%20force%20recordData%3F" id="rso"><div lang="en-IN" data-hveid="CA0QAA" data-ved="2ahUKEwj0iay15vfqAhVdRhUIHaojCbcQjDYoAHoECA0QAA"><div data-md="61" lang="en-IN"><div aria-level="3" role="heading" data-attrid="wa:/description" data-hveid="CA0QAQ"><b style="background-color: transparent; font-family: inherit; font-size: inherit;">force:<b style="background-color: transparent; font-family: inherit; font-size: inherit;">recordData component defines the parameters for accessing, modifying, or creating a record using Lightning Data Service. You have granular control on how you want to display or render the data in your custom component.<div eid="8jckX_TICt2M1fAPqsekuAs" data-async-context="query:What%20is%20force%20recordData%3F" id="rso"><div lang="en-IN" data-hveid="CA0QAA" data-ved="2ahUKEwj0iay15vfqAhVdRhUIHaojCbcQjDYoAHoECA0QAA"><div data-md="61" lang="en-IN"><div aria-level="3" role="heading" data-attrid="wa:/description" data-hveid="CA0QAQ">
</div></div></div></div>
</div></div></div></div>

[Sumit]

The main difference between the two is that one is intended for scripted access to records (force:recordData), while the other is for providing a UI to edit a record (lightning:recordEditForm).

[Sumit]

The action attribute of <aura:handler> sets the client-side controller action to handle the event. The event attribute specifies the event being handled. The format is namespace : eventName . In this example, when the event is fired, the handleComponentEvent client-side controller action is called.

[Sumit]

Initiates requests to delete the external data that corresponds to the specified external object records.

[Sumit]

The Test. isRunningTest() method is used to identify, if the piece of code being executed is invoked from a Test class execution or from other artefacts such as a Trigger, Batch Job etc. Returns true if the code being executed is invoked from a test class otherwise returns a false.

[Sumit]

<div data-md="61" lang="en-IN"><div aria-level="3" role="heading" data-attrid="wa:/description" data-hveid="CA0QAQ">After you activate a process, you can no longer edit that process. However, you can click Clone to save the process as a new inactive process.
<div><div data-hveid="CA0QAg" data-ved="2ahUKEwju_u6bivjqAhX38XMBHZL6DVYQFSgBMAF6BAgNEAI"></div></div></div></div>

[Sumit]

<div data-md="61" lang="en-IN"><div aria-level="3" role="heading" data-attrid="wa:/description" data-hveid="CAoQAQ">Use the error messages that appear in the Process Builder and the emails you receive when a process fails to help solve problems that arise when you're working with processes. When all else fails, look at the Apex debug logs for your processes. The API names for criteria nodes and actions are created in the background.
<div><div data-hveid="CAoQAg" data-ved="2ahUKEwiW8N_-jPjqAhXBgeYKHXM8BMoQFSgBMAF6BAgKEAI"></div></div></div></div>

[Sumit]

Below are 2 conditions:Only when record is createdWhen record is created or edited and while define criteria select the checkbox for below settingDo you want to execute the actions only when specified changes are made to the record?3. Is it possible to edit the process once it is activated?No, You need to clone and while cloning you can create new process or create new version.

[Sumit]

Lightning Data Service is a centralized data caching framework which is used to load, save, create and delete a record without server-side apex code. ... Lightning Data Service improves performance by eliminating the multiple SOQL query call for a single record from the multiple instances.