Future Actions Precedence Keys#

The keys below define context priority when resolving Future Actions. The configured High or Standard precedence value is the first precedence criterion.

Table: Future Action Precedence Keys

The following table lists the execution and configuration properties of each Future Action, including logistical classification, precedence classification, execution mode, uniqueness requirements, copy behavior on Split, and the Security Feature required when feature-level security is enabled.

Table: Future Actions

Split, Merge, and Experiment Actions#

Action Precedence#

The configured precedence (High or Standard) is the first criterion when selecting active Future Actions that match the Material context. Split and Merge actions receive special priority, with Split ordered before Merge. This ordering remains subject to the configured precedence.

Future Actions created during Experiment processing use these precedence values:

• Split and Merge actions use High unless otherwise specified.
• Skip Step creates a Change Flow and Step action with High precedence.
• Other Experiment-generated Future Actions use Standard.

For more information, see Experiment Actions Restrictions.

Pending Merge Behavior#

When a Material arrives at a Step, Experiment action processing stops if the Material has a pending Future Merge.

If automatic processing selects a logistical Future Action configured for manual execution, that action enters the Waiting state. No remaining actions are processed for that trigger. For a manual Merge, this prevents Change Flow and Step from proceeding while the Merge is pending.

After a Merge performed on-flow, applicable actions are evaluated again for the remaining Material. An action executes only when its conditions are met.