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

Table ApprovalStatusTypRef - Add new record:
- N/A - Not required
Table DocumentWorkFlowTypRef - Add new records:
- DCAAAAR - Design-Check-Approve..-Release
- RCAAAARS - Receive-Check-Approve..-Release-Submit
- DCAAAAR - Design-Check-Approve..-Release
- RCAAAARS - Receive-Check-Approve..-Release-Submit
app/Settings-Validations.php - Add/modify validations:
- Implement main validation rules for:
  - DCAAAAR
  - RCAAAARS
  - DCAAAAR
  - RCAAAARS
- Implement special status rule (exception) for N/A status
- Implement complete date check exception for N/A status
- Maturity rules for new workflows
Implement new workflow templates:
- For display in document detail (output templates)
- For data entry in revision new/update (input templates)
Implement updates to app/lib/DrawingRevisionJoinSet.php:
- Maturity
- Background color
- Other items (search for case statements of workflow codes in app/lib and app/model)