Declarative

7 Things To Know About Flows

#1MinuteTip Here is a useful article on 7 things to know about Flows on Salesforce Architect’s Website. And here is the snapshot of those 7 things. For an explanation of each of these points, please navigate to this URL.

  1. Don’t hard code
  2. Use generic inputs and outputs in Apex actions
  3. Use subflows for cleaner, reusable, and more scalable flows
  4. Create an error handling strategy for your flow-based automations, just like Apex
  5. Understand how scheduled flows affect governor limits
  6. Build a bypass for data loads and sandbox seeding
  7. Be aware of looping behaviors
7 Things To Know About Flows

How to Show Progress Indicator in Salesforce Screen-Flows

Flows is one of the most powerful declarative features in Salesforce. It is like a Swiss army knife that you can use for different purpose in different situations.

Screen-Flow is one of the five types of Flows that Salesforce currently offers. Screen-Flow allows you to build rich, dynamic custom UIs and can potentially replace your low to medium complexity Visualforce Page, Aura or Lighting Web Components.

If your screen flow comprises of multiple screens that the users have to navigate through to complete a particular business process, you may want to display a progress indicator for a better user experience.

For example, if the user has to enter the Account details first, then Contact details and then Case details, displaying a progress indicator highlighting all the steps that the user needs to complete and an indication of where they currently are in the process can be an icing on the cake. Something like the following image.

Progress Indicator in Salesforce Screen-Flows

Salesforce Introducing New Formula Functions

#1MinuteTip This tweet from CTO @ Salesforce caught my attention today. Salesforce will be introducing new formula functions in the next release (Summer ’22).

This includes ASCII, CHR, DAYOFYEAR, INITCAP, SIN/COS/TAN, ASIN…, ISOWEEK, ISOYEAR, UNIXTIMESTAMP, FROMUNIXTIME, PI, TRUNC. Maybe FORMATDURATION and IFERROR.

Scroll to Top