Considerations for Working with Flows
Review these points to understand how the provided flows work.
Required Editions
| Available in: Lightning Experience |
| Available in: Professional, Enterprise, and Unlimited Editions |
- Most of the provided flows don’t add or update any records in your org. However, some flows add or update the corresponding record during execution because the subsequent steps in the flow need the new or updated record to proceed. For example, the Add Beneficiary to Policy flow adds the new beneficiary so that the beneficiary’s share percentage can be specified in the subsequent step. These flows add or update records.
-
- Add Beneficiary to Policy
- Add Driver to Auto Policy
- Dispute Transactions
- Initiate FNOL
- Update Billing Date and Frequency
- Update Communication Preferences
- Update Lienholder
- Update Policy Beneficiary Details
- Update Premium Payment Method
- Waive Fees
- The Dispute Transactions flow creates a case and a case gateway request for each transaction selected during the flow. Having a separate case for each disputed transaction makes it easier to track each case against its own service-level agreement (SLA).
- To use a flow, a user must have access to the underlying object and its fields. For example, for the Update Communication Preferences flow, the user must have access to the Do Not Call, Email Opt Out, Fax Opt Out, and Marketing Opt-Out fields on the Contact object.
Did this article solve your issue?
Let us know so we can improve!
