Skip to content

Manage Future Actions#

🔒 Step.ManageFutureActions

Overview#

This operation is used to define Future Actions to be applied to a Material while at a Step.

Setup#

The configuration /Cmf/System/Configuration/MaterialTracking/FutureActions/Hold/AllowDuplicateReasons controls the behavior of duplicated Holds. There are three possible values for this setting:

  • No (default) - does not allow duplicate Hold Reasons for the same Hold context.
  • Yes - allows duplicate Hold Reasons for the same Hold context, provided that the Hold Reason supports multiple concurrent instances (in case that this property is changed later at the Hold Reason, it will not have an effect on existing future Holds).
  • YesUniqueComments - same as Yes, but the system will additionally check that the comments are unique for each Hold context, and, for each Hold Reason, that the comments are not duplicated.

Preconditions#

  • The Step exists and it is Active.
  • To edit a Future Action, it must have been created by you.
  • It is not possible to create a Future Action for a Pass-Through Step if the Action field is Set Resource.
  • It is not possible to create a Future Action for a Pass-Through Step if the Action field is Set Service.
  • It is not possible to create a Future Action for a Pass-Through Step if the State field is Queued.

Sequence of Steps#

Step 1: Manage Future Actions#

The Manage Future Actions operation can be called from the Step page within the Business Data Group, scrolling to the Future Action section in the main Step page. In the wizard:

  1. Using the button, add all any wanted Future Action. For more information, see Manage Material Future Actions.
  2. Select Update to complete the transaction.

Screenshot showing a user interface for managing future actions.

Note

In scenarios where the same Step is repeated within the Flow and the Material is in a Processed state, you may opt to enable Force Queued State. Otherwise, the Material will stay in the Processed state. Additionally, you can define the default value for the Force Queued State by editing the entry Context = Material.ChangeFlowAndStep for the Element = ForceQueuedState in the GUIElementDefaultValue Generic Table.

In the Action Context section of Manage Future Actions you can define a Flow, Product or Product Group for a specific revision or for an entity to serve as the context.

When cloning a Flow as an Entity, if there are Future Actions linked to that Flow (for example, CH-Cookie-Flow), all those actions will be copied to the new clone.

Screenshot showing a workflow management interface with a focus on managing future actions.

However, if you are cloning a Flow Revision, only the Future Actions linked to that specific Revision (for example, CH-Cookies.Flow [B]) will be copied to the new clone.

Screenshot showing the "Force Queued State" option in a workflow management interface.