PhraseryPhrasery homeGet Phrasery
CRM & sales ops21 categories

Design a Salesforce Flow before building it

A Salesforce automation request, worked out on paper before you discover the limits in production.

Design a Salesforce Flow for the requirement below.

Specify: the flow type (record-triggered, scheduled, screen) and why, the trigger object and whether it runs before or after save, entry conditions, the elements in order, and what runs in the fault path.

Then the parts that bite later: governor limits if it fires on a bulk load, recursion if it updates the record that triggered it, what happens when a lookup returns nothing, and which parts should be before-save for performance.

Say if this should be a validation rule, a formula field, or nothing at all instead of a flow.

Requirement:

Making it yours

  • Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
  • Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
  • If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.

Automation and admin. Workflows, validation, field design and the documentation nobody wrote at the time.

Related prompts

Keep this one

Phrasery saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.

Add to your browser โ€” free