Flexcard actions for flyouts, Omniscripts and events
Which Flexcard action fits a workflow step (Omniscript, Navigate, Flyout, Data, Card actions such as Set Values and Select Card, Event and Update Omniscript), how sequential actions run, how to lock a card while an action runs, and how child cards, other components and Omniscripts exchange data through events.
Recommend the implementation of necessary actions (e.g., links, modals, launching Omniscripts, calling Integration Procedures, Child Flexcards) on Flexcards to drive user workflows and business processes.
~7 min read · 8 practice questions ·
What the exam expects
- Recommend the action type for each workflow step: Omniscript, Navigate, Flyout, Data, Card (Reload, Remove, Select Card, Set Values, Update Datasource), Event and Update Omniscript.
- Recommend a flyout for rarely needed data or a form that must stay over the card, and explain how it closes itself.
- Order sequential actions so navigation comes last, and lock the card while a Data action runs.
- Recommend custom events for child-to-parent updates and pubsub events between components.
- Recommend Select Card with Update Omniscript when a card inside an Omniscript step must send selected records.
Key terms: Data action (calls a data source and stores the result in a response node), flyout (a modal or popover showing a child Flexcard, Omniscript or LWC), sequential actions (several actions on one trigger, run in order), event listener (Setup entry that runs an action when an event fires), Select Card (collects chosen records into a named list).
Key facts
- Detail
- Use the Omniscript action; Navigate is for external pages
- Detail
- A new page has none; call it from a modal flyout
- Detail
- Runs only when the flyout opens
- Detail
- Pubsub event with the flyout's channel name and event name close
- Detail
- Saved to the record object or a Response Node, read as {node.field}
- Detail
- Option on the action, or a merge field such as {requireResponse}
- Detail
- Top to bottom, each waits; a failure skips the rest
- Detail
- Removes from the page, not the data source
- Detail
- selectcards_ plus the list name runs Update Omniscript; Omniscript support on
Sources for this section (7)
- Set Up Navigation on a Flexcardhelp.salesforce.com (opens in a new tab)
- Launch an Omniscripthelp.salesforce.com (opens in a new tab)
- Explore Key Flexcard Featurestrailhead.salesforce.com (opens in a new tab)
- Set Up Flyouts on a Flexcardhelp.salesforce.com (opens in a new tab)
- Get or Send Datahelp.salesforce.com (opens in a new tab)
- Set Up Actions on a Flexcardhelp.salesforce.com (opens in a new tab)
- Set Up Card Actionshelp.salesforce.com (opens in a new tab)
- Why is a flyout a good home for data users rarely open on a Standard Runtime card?
- When should the Navigate action be the last action in a sequence?
- What happens to the remaining sequential actions when one action fails?
- Why does a Remove card action not delete the record?
- Which event name must a Standard Runtime parent listen for when its embedded Select Card list is named pickedlines?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Omnistudio Consultant pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 31 lessons of the Omnistudio Consultant guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (8 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams