Latest articles to keeps you updated about the latest
salesforce tools and apps to grow your business.
The release of this feature has provided great ease to Salesforce admins while dealing with ListView data. The feature lets users view ListView data as well as a selected record, splitting views on the same pane.
Previously, it was a bit messed up and you could only load one record after closing another.
But now users can easily turn on this feature under the Display As icon when required and avail of this function.
For custom objects, the Lightning App builder now lets you pick out related fields. Being Components themselves lets Field have visibility rules and criteria set for them that only let them appear ina section for certain values entered in another visible related field.
This lets forms probe for more information only relevant and limits field visibility to select audiences within the same form.
Coming to Dynamic Actions within Dynamic Forms. Dynamic Actions have options for Follow, Convert, Edit, and New case. With the help of Dynamic Actions and visibility rules, the visibility of these actions can be customized and made available to users per requirement. While separate Lightning Pages have better maintainability if users types can vary widely, for users with similar needs or criteria, you could choose to drop point-and-click actions into a Lightning Page.
Dynamic Forms and Actions area great way to streamline routine, criteria based workflows by strategically exposing field dropdowns and options only to similar users meeting specific criteria.
Turning to Flow updates, you’ll see new Flows, all set to accommodate usage style and batched changes to records in a better way.
‘After Save’ Triggers, contrary to last year’s ‘Before Save’ triggers, can invoke actions after saving may record changes in one go, almost as if all Triggers were cached to go off only once multiple record changes were saved. We also get to see Record Update Flows that run as soon as there’s an insert, upsert, or record update.
Also, two new ‘Screen Flows’, Flow Interview Logs & Flow Interview Log Entries now let you track Flow instances and their screens respectively. In addition to this, ‘Pub-Sub’-style Platform Event Flows now launch (‘publish’) pre-defined Flows when a platform event (‘subscription event’) occurs. This lends itself to ‘platform’-integration with multiple systems that can launch actions to modify records, send communications, and much else.
Earlier, to deal with platform event flow, a combination of ‘Process Builder’ and ‘Flows’ was used, but now any automation on platform events can be done simply with Flows, without Process Builder. And as if that wasn’t enough, with this new release, now you can schedule Flows too. When content is inserted even after 2 days, it can be updated in a record using Flows.
Please fillup the form and send your message.