| Deletions are marked like this. | Additions are marked like this. |
| Line 8: | Line 8: |
| * Ability to separate the final ''release'' of a revision from its ''distribution'' (e.g. the Submittal) | 1. Ability to separate the final ''release'' of a revision from its ''distribution'' (e.g. the Submittal) |
| Line 10: | Line 10: |
| * NOK wants a final ''Freigabe'' that occurs after all the approvals have been successfully completed | 1. NOK wants a final ''Freigabe'' that occurs after all the approvals have been successfully completed |
| Line 12: | Line 12: |
| * To reduce the number of workflows, we will also implement a N/A approval status: | 1. To reduce the number of workflows, we will also implement a N/A approval status: |
| Line 20: | Line 20: |
| * Requested by NOK, using the following terminology: | 1. Requested by NOK, using the following terminology: |
| Line 27: | Line 27: |
| * Table '''Approval``Status``Typ``Ref''' - Add new record: | 1. Table '''Approval``Status``Typ``Ref''' - Add new record: |
| Line 30: | Line 30: |
|
* Table '''Document``Work``Flow``Typ``Ref''' - Add new records: * '''DCAAAARS''' - Design-Check-Approve..-Release-Submit |
1. Table '''Document``Work``Flow``Typ``Ref''' - Add new records: * '''DCAAAAR''' - Design-Check-Approve..-Release * '''RCAAAARS''' - Receive-Check-Approve..-Release-Submit * '''DCAAAAR''' - Design-Check-Approve..-Release |
| Line 34: | Line 36: |
| * '''app/Settings-Validations.php''' - Add/modify validations: | 1. '''app/Settings-Validations.php''' - Add/modify validations: |
| Line 36: | Line 38: |
| * '''DCAAAARS''' |
* '''DCAAAAR''' * '''RCAAAARS''' * '''DCAAAAR''' |
| Line 40: | Line 44: |
|
* Maturity rules for new workflows 1. Implement new '''workflow templates''': * For display in document detail (output templates) * For data entry in revision new/update (input templates) 1. 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) |
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:
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 main validation rules for:
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)