Follow

Why can't the status be changed and thus the release/expired workflow not be started?

The most common reasons why a process cannot be sent for approval or expiry are the following:

  • Mandatory attributes are not maintained. This also applies to processes that should be set to Expired.
  • Validation rules are not adhered to. This is also valid for processes that should be set to Expired.
  • There is already another version in the release or expiry workflow. In the expiry workflow, the status of the process remains unchanged "Released" or "Released & Valid" until fully approved by all participants.  Please verify in life cycle tab whether a release is still open (green tick missing).

FAQ-lifecycle.png

  • Assigned responsible persons no longer have an "Approver" user roleFAQ-einstellungen.png
  • User has application role "Author", but is not entered as "Author" but under "Additional authors".  Additional authors do not have the authorization to start workflows.
    • If one of the "Additional authors" wants to take over the (main) author function - in this case starting workflows - he/she has to be set as (main) author as well as being deleted as "Additional author". The initial author may be added as "Additional authors" if necessary.
  • User has application role "Approver" or "Architect", but is not entered as "Author". In this case, he/she is not able to initiate the workflow.
    • If an "Approver" or "Architect" want to start the release or expiry workflow, he/she has to be set as (main) author. The initial author may be added as "Additional authors" if necessary.

 

0 Comments

Please sign in to leave a comment.
Powered by Zendesk