Release-Submit Workflow

Requirements

• Ability to separate the final release of a revision from its distribution (e.g. the Submittal)

• NOK wants a final Freigabe that occurs after all the approvals have been successfully completed

• To reduce the number of workflows, we will also implement a N/A approval status:

  • If an approval status is set to N/A, then the approval is note required

  • This means that the a four-approval workflow can always be used and the unnecessary approvals be set to N/A.
  • When a status is set to N/A then:
    • The complete date must be empty
    • The plan data can be set or be empty
    • A user can be assigned to the step (who might be the user that decided that N/A is correct), but is ignored
• Requested by NOK, using the following terminology:

  • Zustimmung = Approval

  • Freigabe = Release

  • Verteilen = Submit

Technical Solution

• Table ApprovalStatusTypRef - Add new record:

  • N/A - Not required

• Table DocumentWorkFlowTypRef - Add new records:

  • DCAAAARS - Design-Check-Approve..-Release-Submit

  • RCAAAARS - Receive-Check-Approve..-Release-Submit

• app/Settings-Validations.php - Add/modify validations:

  • Implement main validation rules for:

    • DCAAAARS

    • RCAAAARS

  • Implement special status rule (exception) for N/A status
  • Implement complete date check exception for N/A status