Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Production Management

About states and transitions

  • Last UpdatedMar 19, 2025
  • 2 minute read

AVEVA™ Production Management supplies a default record state workflow. In most cases, this is sufficient and you are not required to alter the supplied record states and the standard workflow.

Studio project hierarchy view showing the default record state workflow, from Available, Active, Closed, to Error with their corresponding transitions,.

For each record state, the possible transitions appear beneath the record state. It is not possible for any state to transition to the Error state, so the Error state does not appear as a valid transition.

When you add a new custom record state, each available transition appears beneath the new custom state and the new custom state appears as a valid transition beneath existing states.

Studio project hierarchy view showing the default record state workflow, from Available, Active, Closed, to Error with their corresponding transitions. It also shows a custom record state node with the available transitions.

Example of workflows

This diagram illustrates the standard Recipe workflow that is supplied with AVEVA™ Production Management out-of-the-box.

A diagram showing the standard recipe workflow supplied with the application by default, which consists of New, Archived, Active, and Pending Active.

This diagram shows a possible new Recipe workflow scenario with custom states introduced to the workflow.

A diagram showing a custom recipe workflow, which consists of New, Archived, Active, Pending Active, and On hold custom states.

In This Topic
Related Links
TitleResults for “How to create a CRG?”Also Available in