Workflow UI: Support of Workflow-Identifying Fields of the Second Level

This topic describes how a workflow-identifying field of the second level can be implemented by using Workflow UI.

In the Customization Project Editor, the customizer can define workflow selection to be based on the value of a type identifier and then further based on the value of the subtype identifier. A workflow defined for the subtype identifier value inherits its configuration from the workflow defined for the type identifier value. The following diagram shows the types and subtypes of workflows based on their workflow-identifier field values.

Figure 1. Types and subtypes of workflows

In the Customization Project Editor, the customizer uses the Subtype Identifier box on the Workflows page to the specify the workflow-identifying field of the second level. This box appears on the page only if the workflow-identifying field for the workflow has been specified in the code.

Support of the Workflow Subtype: Sales Order Example

In MYOB Acumatica, the workflows for the Sales Orders (SO30100) form are based on the predefined automation behavior, which can be one of the following:

Sales Order
Transfer Order
Invoice
Quote
Credit Memo
RMA Order
Blanket Order
Mixed Order

Tip: The customizer cannot create custom automation behaviors.

On the Order Types (SO201000) form, the customizer can create multiple order types that are based on the same automation behavior. Suppose that the customizer has created two custom order types (T1 and T2) that are based on the Sales Order automation behavior.

In previous versions of MYOB Acumatica, it was not possible to create separate workflows for these custom order types, because for a particular order type, the system used the workflow of the automation behavior this order type was based on.

In MYOB Acumatica 2024.1.1, for each form that has a workflow-identifying field specified in the predefined system workflow (as is the case with the Sales Orders form), the customizer can select a workflow-identifying field of the second level (the Order Type field in the following screenshot).

Figure 2. Selection of the workflow's subtype identifier

Then in the Add Workflow dialog box, which opens when the customizer clicks the Add Workflow button, the customizer can select one of the created order types (T1 or T2) as a workflow subtype (see the following screenshot).

Figure 3. Selection of the workflow subtype

Important: Only one workflow per order type is supported.

The customizer then can mark both created workflows as active (see the following screenshot).

Figure 4. Two separate workflows for different order types

After the customizer creates a separate workflow for each custom order type, they can perform the usual operations with these workflows: add, remove, or modify states, actions, fields, and transitions.

If the customizer does not need to create separate workflows for each of the order types, they can keep the workflow with the Default subtype active. The system will use this workflow for sales orders that meet the following criteria:

The behavior used for the sales orders is the same as the workflow type (for example, the behavior is SO and the workflow type is SO).
Separate workflows have not been defined with this type and with a subtype that is the same as the order type