Salesforce Facts by Abhishek

Suppose we want to keep a field editable only during the record creation, and once record is created it should be read only in the UI level(for non-admin users). Apart from validation rule, we can make use of field section in lightning app builder to implement the same. In this example, the LeadSource field on opportunity is made read only once it is created by keeping two field instances with two different filters. Note: Field section does not work for community. Attached are the screenshots.

Intelligence views are available for Leads and Contacts in Sales cloud. It is a one stop place for all the engagement activity and insights of the records. In order to enable it, go to Setup -> Lead Intelligence View Setup / Contact Intelligence View Setup -> Turn the setting on -> Add the Intelligence View Button in the list view button layout. Reference:  https://help.salesforce.com/s/articleView?id=sf.leads_intelligence_view.htm&type=5    https://help.salesforce.com/s/articleView?id=sf.contacts_intelligence_view.htm&type=5

In LWC, if there are multiple lightning record pickers present and suppose we need to set/reset the value of a particular one, we can make use of the lwc:ref option. Attached are the screenshots.

In LWC, Many times we deal with the scenario of adding an object conditionally in JS array of objects. And it needs to be added in the middle based on some condition. In this case the spread operator and the ternary operator combo works together. Reference:  https://stackoverflow.com/questions/70385371/js-conditionally-adding-adding-in-the-middle-of-an-array Attached is an example screenshot.

Suppose we have a use case where we have a toggle in the screen flow and we want to allow the user to activate it only once. Once activated it will be disabled. We can use the toggle's value in Disabled attribute in this case. Attached are the screenshots.

The custom property editor is a useful feature in screen flow. It can work as a container of several base components and can pass the data to the screen as set by admin. Flow builder has a JavaScript class for this purpose that uses the inputVariables and validate interfaces. In order to pass the data, the event propagation attributes need to be specified and the custom event name must be 'configuration_editor_input_value_changed'. Reference:  https://developer.salesforce.com/docs/platform/lwc/guide/use-flow-custom-property-editor-lwc-example.html