Explain the difference between a Navigate action and a Flyout action on a FlexCard, and when you would choose each.

Both open something; the difference is whether the user keeps their place.

1. A Navigate action takes the user somewhere else — a record page, another OmniScript, a custom component. The current page is left behind. Use it when the new destination is the user's next task and there is nothing to come back to.
2. A Flyout action renders a child FlexCard or an OmniScript in an overlay or adjacent region while the parent stays on screen. Use it for a drill-down, a quick edit, or a short sub-task after which the user should return to what they were doing.
3. Flyouts are particularly good for console-style work where an agent is mid-call and losing the page context is expensive.
4. The trade-off: flyouts add complexity around refreshing the parent afterwards, and a deeply nested flyout chain is disorienting. If the sub-task is long or has its own multi-step flow with its own saves, a navigate is often the honest choice.