What can I do, if a ADONIS Release Workflow (RWF) step is missing?

Problem

A user wants to perform an workflow step, but there is no suitable step available

​

 
The following possible causes help determine where the issue originates.

Important: It is advisable to export your component settings before making any changes to the configuration. This way, you can always restore all settings to how they were before the changes were made.
 

Possible cause 1: User does not have the correct RWF role​

Only certain RWF roles are able to execute certain transitions. Who can do what, can be fully customized using the Administration Toolkit (ATK).
 

Web-Client

This guide applies to ADONIS 16 and later versions. For instructions applicable to earlier versions, please click here

Solution Steps
Open your Administration Toolkit and go to Settings.
Search for Release Workflows (1). Open Models (2) and Model release workflow (3) then General (4).  After that go to Configuration of Transitions (5).
Choose the transition you want to edit.  Open the transition by clicking on the three dots (1) and then Edit (2).
Go to the Conditions tab, there you will find the which RWF roles are allowed to execute the transition.
Make sure, your user has one of the checked RWF roles assigned.  Open User Management (1), click on your user and switch to Groups and Roles (2), check the System roles.  If the System role is missing click on Select System Roles (3) to add it.

Rich-Client

These instructions apply to versions prior to ADONIS 16. For instructions that apply to later versions, please click here.

Solution Steps
Open your Administration Toolkit and switch to Library Management (1).  Switch to the tab Component Settings (2) and open the setting for Release Workflow (3).  Now you need to open Configuration of Transitions (4).
Double-click the transition (1) you want to edit and switch to the tab Conditions (2). Under RWF roles (3) you can see, which RWF roles are allowed to execute the transition.
Make sure, your user has one of the checked RWF roles assigned.  Open User Management (1), click on your user (2), check the System roles (3).  If the System role is missing click on Add System Roles (4) to add it.

Possible cause 2: User is not listed as process responsible

Web-Client

This guide applies to ADONIS 16 and later versions. For instructions applicable to earlier versions, please click here

Solution Steps
Open your Administration Toolkit and go to Settings.
Search for Release Workflows (1). Open Models (2) and Model release workflow (3) then General (4). After that go to Configuration of Transitions (5).
Choose the transition you want to edit. Open the transition by clicking on the three dots (1) and then Edit (2).
Switch to the tab Conditions (1). The setting Process responsible who are allowed to execute the transition (2) could be the reason why you cannot execute the transition. Once active, the user has to have an RWF role and needs to be entered in the notebook of the model. For example Process owner (3).
In this case, only one can execute the transition who is noted as the process owner.

Rich-Client

These instructions apply to versions prior to ADONIS 16. For instructions that apply to later versions, please click here.

Solution Steps
Open your Administration Toolkit and switch to Library Management (1). Switch to the tab Component Settings (2) and open the setting for Release Workflow (3). Now you need to open Configuration of Transitions (4).
Double-click the transition (1) you want to edit and switch to the tab Conditions (2). The setting Process responsible who are allowed to execute the transition (3) could be the reason why you cannot execute the transition. Once active, the user has to have an RWF role and needs to be entered in the notebook of the model. For example Process owner (4).
In this case, only one can execute the transition who is noted as the process owner.

Possible cause 3: A newer version of the same model already exists

Example: You want to create a new draft version of the version 3.0, but there already is a version 4.0 present. Even if the model version 4.0 is in the archive folder, you still cannot create a version 3.1, unless 4.0 is deleted.