ARTICLE: Flow Designer Tips and Tricks

[RiteshSwarnakar]

1) Where Flow Designer can be used:

• Flow - Inbound Email Action
• Subflow  - Scripted Rest API
• Flow - After / Async Business Rule
• Flow / Subflow - Workflow replacement
• Flow - Scheduled Job (up to certain extend)
• Subflow - As a function on any Server- Side Script including Script Include

2) Replace Business Rule with Flow (Equivalent):
Run in Foreground == After BR
Run in Background == Async BR
Trigger Record Created == After BR on Insert

Trigger Record Updated == After BR on Update

Many a times the After BR does not work even though the conditions are met, try changing it to Async BR OR use Flow it will work.

3) Inbound Email Flow:

Flow should be created in a domain and the user who will be sending the email should also be in same domain. User creation in same domain is necessary with same email id from where email will be coming from.
To access Inbound action FD
fd_data.trigger.inbound_email.body_text

To access Flow variables:

fd_data.flow_var.<variable_name>

4) If Flow is in different domain and you want to use a record(ex: group/user) of some other domain, then use inline script and return sys_id of the group/user of different domain.

Some Issues and how to fix it:

Error	Cause	Fix
Flow is empty. Unable to compile the flow	When Flow Domain is changed manually in the sys_hub_flow table, and then trying to save and activate	Copy the flow and then save and activate