...
The supported workflow paths are described in detail here.at the following links:
...
The Non-Legacy Workflow Path describes the process by which a concept is mapped independently by two specialists, with conflicts arising resolved by the lead.
INITIAL STATE:
- A tracking record for the concept to be mapped has been created by Compute Workflow.
- No map records exist for this concept and project.
FINAL STATE:
- No tracking record exists for this concept and project.
- A single map record marked READY_FOR_PUBLICATION exists.
...
The combinations of map records that exist for a given
workflow state. Each combination is listed on a new line.
Where multiple records exist for a single combination, they
are linked with a plus sign (+),
e.g. EDITING_DONE + EDITING_IN_PROGRESS.
The current user's record (if any) is marked in bold.
...
[NO RECORDS – INITIAL STATE ]
NEW
EDITING_IN_PROGRESS
EDITING_DONE
...
Specialist clicks Finish from either:
- Map Record editing page, or
- Assigned Work widget.
...
NEW + NEW
NEW + EDITING_IN_PROGRESS
NEW + EDITING_DONE
...
Specialist clicks Save For Later on Map Record editing page.
...
Specialist's record validated. If record valid:
- If EDITING_DONE record exists:
- Compare this record to EDITING_DONE record.
- If conflict detected, set both records to CONFLICT_DETECTED
- If conflict not detected
- Set user's record to READY_FOR_PUBLICATION
- Delete second CONFLICT_DETECTED record
- Delete tracking record
- IF EDITING_DONE record does not exist:
- set user's record to EDITING_DONE
...
Specialist clicks Finish from Map Record editing page.
...
EDITING_IN_PROGRESS + NEW
EDITING_IN_PROGRESS + EDITING_IN_PROGRESS
EDITING_IN_PROGRESS + EDITING_DONE
...
Specialist's record validated. If record valid:
- If EDITING_DONE record exists:
- Compare this record to EDITING_DONE record.
- If conflict detected, set both records to CONFLICT_DETECTED
- If conflict not detected
- Set user's record to READY_FOR_PUBLICATION
- Delete second CONFLICT_DETECTED record
- Delete tracking record
- IF EDITING_DONE record does not exist:
- set user's record to EDITING_DONE
...
Specialist clicks Finish from either:
- Map Record editing page, or
- Assigned Work widget
...
EDITING_DONE + NEW
EDITING_DONE + EDITING_IN_PROGRESS
...
Specialist clicks Finish from Map Record editing page.
...
...
SAVE_FOR_LATER
...
Specialist's record validated. If validation successful, compare this
record to second CONFLICT_DETECTED record:
- If conflict detected, save record. No workflow modification
- If conflict not detected
- Set user's record to READY_FOR_PUBLICATION
- Delete second CONFLICT_DETECTED record
- Delete tracking record
...
Specialist's record deleted.
Remaining CONFLICT_DETECTED record set to EDITING_DONE.
...
CONFLICT_DETECTED
+ CONFLICT_DETECTED
+ CONFLICT_NEW
...
Lead's record validated. If validation successful, lead's record
saved and marked CONFLICT_RESOLVED
...
Lead clicks Finish from Compare Records editing page.
...
CONFLICT_DETECTED
+ CONFLICT_DETECTED
+ CONFLICT_IN_PROGRESS
...
Lead clicks Finish from either:
- Compare Records editing page
- Assigned Work widget
...
CONFLICT_DETECTED
+ CONFLICT_DETECTED
+ CONFLICT_RESOLVED
...
...
Lead clicks Finish from Compare Records editing page.
...
Lead's record set to READY_FOR_PUBLICATION.
Records marked CONFLICT_DETECTED deleted.
Tracking record deleted.
LEADS TO FINAL STATE.
...
Description of workflow combinations
This section describes each possible combination of workflow statuses attached to a tracking record for a concept and project.
...
One specialist has claimed the concept, but has not begun editing
...
Legacy Workflow Path
UNIMPLEMENTED
...
Workflow Status Combination | Action | Result | Trigger |
---|---|---|---|
The combinations of map records that exist for a given | The legal actions that can be requested for each workflow status combination. | Description of map records added, modified, or deleted as a result of the requested action. | User action in Mapping Tool resulting in requested action. |
Specialist Level Work: User's record marked in bold | |||
READY_FOR_PUBLICATION INITIAL STATE: No tracking record | ASSIGN_FROM_INITIAL_RECORD | Map record marked PUBLISHED or READY_FOR_PUBLICATION is | User clicks Edit Record on either:
|
REVISION + NEW | SAVE_FOR_LATER | Specialist's record saved without validation and set to EDITING_IN_PROGRESS. | Specialist clicks Save For Later on Map Record editing page. |
FINISH_EDITING | Specialist's record validated. If validation successful, specialist's record saved and marked REVIEW_NEEDED. | Specialist clicks Finish from Map Record editing page. | |
UNASSIGN | Specialist's record deleted. Record marked REVISION marked as previous workflow state (either PUBLISHED or READY_FOR_PUBLICATION) | Specialist clicks Unassign on Assigned Work widget. | |
REVISION + EDITING_IN_PROGRESS | SAVE_FOR_LATER | Specialist's record saved without validation. No workflow modification. | Specialist clicks Save For Later on Map Record editing page. |
FINISH_EDITING | Specialist's record validated. If validation successful, specialist's record saved and marked REVIEW_NEEDED. | Specialist clicks Finish from either:
| |
UNASSIGN | Specialist's record deleted. Record marked REVISION marked as previous workflow state (either PUBLISHED or READY_FOR_PUBLICATION) | Specialist clicks Unassign on Assigned Work widget. | |
REVISION + REVIEW_NEEDED | SAVE_FOR_LATER | Specialist's record saved without validation. No workflow modification. | Specialist clicks Save For Later on Map Record editing page. |
FINISH_EDITING | Specialist's record validated. If validation successful, specialist's record saved. No workflow modification. | Specialist clicks Finish from Map Record editing page. | |
UNASSIGN | Specialist's record deleted. Record marked REVISION marked as previous workflow state (either PUBLISHED or READY_FOR_PUBLICATION) | Specialist clicks Unassign on Assigned Work widget. | |
ASSIGN_FROM_SCRATCH | Record created with REVIEW_NEW status | Lead clicks Assign on Available Work widget | |
Lead Level Work: User's record is marked in bold | |||
REVISION | SAVE_FOR_LATER | Lead's record saved without validation and marked REVIEW_IN_PROGRESS. | Lead clicks Save for Later on Compare Records editing page. |
FINISH_EDITING | Lead's record validated. If validation successful, lead's record | Lead clicks Finish from Compare Records editing page. | |
UNASSIGN | Lead's record deleted. | Lead clicks Unassign on Assigned Work widget. | |
REVISION | SAVE_FOR_LATER | Lead's record saved without validation. No workflow change. | Lead clicks Save for Later on Compare Records editing page. |
FINISH_EDITING | Lead's record validated. If validation successful, lead's record saved and marked REVIEW_RESOLVED | Lead clicks Finish from either:
| |
UNASSIGN | Lead's record deleted | Lead clicks Unassign on Assigned Work widget. | |
REVISION | SAVE_FOR_LATER | Lead's record saved without validation. No workflow change. | Lead clicks Save for Later on Compare Records editing page. |
FINISH_EDITING | Lead's record validated. If validation successful, lead's record saved and marked REVIEW_RESOLVED | Lead clicks Finish from Compare Records editing page. | |
PUBLISH | Lead's record set to READY_FOR_PUBLICATION. LEADS TO FINAL STATE. | Lead clicks Publish from Assigned Work widget. | |
UNASSIGN | Lead's record deleted. | Lead clicks Unassign on Assigned Work widget. |
Description of workflow combinations
This section describes each possible combination of workflow statuses attached to a tracking record for a concept and project.
...
Workflow Status Combination | Action | Result | Trigger |
---|---|---|---|
The combinations of map records that exist for a given | The legal actions that can be requested for each workflow status combination. | Description of map records added, modified, or deleted as a result of the requested action. | User action in Mapping Tool resulting in requested action. |
Specialist Level Work: User's record marked in bold | |||
[NO RECORDS – INITIAL STATE ] | ASSIGN_FROM_SCRATCH | Record created with NEW status. | User clicks Assign Concept on Available Work widget |
NEW | SAVE_FOR_LATER | Specialist's record saved without validation and set to EDITING_IN_PROGRESS. | Specialist clicks Save For Later on Map Record editing page. |
FINISH_EDITING | Specialist's record validated. If validation successful, specialist's record saved and marked REVIEW_NEEDED. | Specialist clicks Finish from Map Record editing page. | |
UNASSIGN | Specialist's record deleted. | Specialist clicks Unassign on Assigned Work widget. | |
EDITING_IN_PROGRESS | SAVE_FOR_LATER | Specialist's record saved without validation. No workflow modification. | Specialist clicks Save For Later on Map Record editing page. |
FINISH_EDITING | Specialist's record validated. If validation successful, specialist's record saved and marked REVIEW_NEEDED. | Specialist clicks Finish from either:
| |
UNASSIGN | Specialist's record deleted. | Specialist clicks Unassign on Assigned Work widget. | |
REVIEW_NEEDED | SAVE_FOR_LATER | Specialist's record saved without validation. No workflow modification. | Specialist clicks Save For Later on Map Record editing page. |
FINISH_EDITING | Specialist's record validated. If validation successful, specialist's record saved. No workflow modification. | Specialist clicks Finish from Map Record editing page. | |
UNASSIGN | Specialist's record deleted. | Specialist clicks Unassign on Assigned Work widget. | |
ASSIGN_FROM_SCRATCH | Record created with REVIEW_NEW status | Lead clicks Assign on Available Work widget | |
Lead Level Work: User's record is marked in bold | |||
REVIEW_NEEDED + REVIEW_NEW | SAVE_FOR_LATER | Lead's record saved without validation and marked REVIEW_IN_PROGRESS. | Lead clicks Save for Later on Compare Records editing page. |
FINISH_EDITING | Lead's record validated. If validation successful, lead's record | Lead clicks Finish from Compare Records editing page. | |
UNASSIGN | Lead's record deleted. | Lead clicks Unassign on Assigned Work widget. | |
REVIEW_NEEDED + REVIEW_IN_PROGRESS | SAVE_FOR_LATER | Lead's record saved without validation. No workflow change. | Lead clicks Save for Later on Compare Records editing page. |
FINISH_EDITING | Lead's record validated. If validation successful, lead's record saved and marked REVIEW_RESOLVED | Lead clicks Finish from either:
| |
UNASSIGN | Lead's record deleted | Lead clicks Unassign on Assigned Work widget. | |
REVIEW_NEEDED + REVIEW_RESOLVED | SAVE_FOR_LATER | Lead's record saved without validation. No workflow change. | Lead clicks Save for Later on Compare Records editing page. |
FINISH_EDITING | Lead's record validated. If validation successful, lead's record saved and marked REVIEW_RESOLVED | Lead clicks Finish from Compare Records editing page. | |
PUBLISH | Lead's record set to READY_FOR_PUBLICATION. LEADS TO FINAL STATE. | Lead clicks Publish from Assigned Work widget. | |
UNASSIGN | Lead's record deleted. | Lead clicks Unassign on Assigned Work widget. |
Description of workflow combinations
This section describes each possible combination of workflow statuses attached to a tracking record for a concept and project.
...
QA Workflow Path
The QA Workflow Path describes the process by which a concept with publication-ready mappings is inserted into the workflow by an admin or through the QA report process. The concept is available to either specialists or leads, and requires only one-step review before being marked publication-ready.
INITIAL STATE:
- No tracking record exists for this concept and project.
- A single publication-ready (PUBLISHED, READY_FOR_PUBLICATION) map record exists for this concept and project.
FINAL STATE:
- No tracking record exists for this concept and project.
- A single map record marked READY_FOR_PUBLICATION exists.
Workflow Status Combination | Action | Result | Trigger |
---|---|---|---|
The combinations of map records that exist for a given | The legal actions that can be requested for each workflow status combination. | Description of map records added, modified, or deleted as a result of the requested action. | User action in Mapping Tool resulting in requested action. |
Specialist or Lead Work: User's record is marked in bold | |||
READY_FOR_PUBLICATION INITIAL STATE: No tracking record | CREATE_QA_RECORD | Map record marked PUBLISHED or READY_FOR_PUBLICATION is | User clicks Edit Record on either:
|
REVISION + QA_NEEDED | UNASSIGN | NOT YET IMPLEMENTED Will remove the QA record and return the REVISION record to its earlier | N/A |
REVISION | SAVE_FOR_LATER | User's record saved without validation and marked REVIEW_IN_PROGRESS. | User clicks Save for Later on Compare Records editing page. |
FINISH_EDITING | Users record validated. If validation successful, lead's record | User clicks Finish from Compare Records editing page. | |
UNASSIGN | User's record deleted. | User clicks Unassign on Assigned Work widget. | |
REVISION | SAVE_FOR_LATER | User's record saved without validation. No workflow change. | User clicks Save for Later on Compare Records editing page. |
FINISH_EDITING | User's record validated. If validation successful, lead's record saved and marked REVIEW_RESOLVED | User clicks Finish from either:
| |
UNASSIGN | User's record deleted | User clicks Unassign on Assigned Work widget. | |
REVISION | SAVE_FOR_LATER | User's record saved without validation. No workflow change. | User clicks Save for Later on Compare Records editing page. |
FINISH_EDITING | User's record validated. If validation successful, lead's record saved and marked REVIEW_RESOLVED | User clicks Finish from Compare Records editing page | |
PUBLISH | User's record set to READY_FOR_PUBLICATION. LEADS TO FINAL STATE. | User clicks Publish from Assigned Work widget. | |
UNASSIGN | User's record deleted. | User clicks Unassign on Assigned Work widget. |
Description of workflow combinations
This section describes each possible combination of workflow statuses attached to a tracking record for a concept and project.
Status 1 | Status 2 | Status 3 | Explanation |
---|---|---|---|
REVISION | QA_NEEDED | Concept with publication-ready mapping has been marked for QA | |
REVISION | QA_NEEDED | REVIEW_NEW | User has claimed the concept marked for QA, but has not begun editing. |
REVISION | QA_NEEDED | REVIEW_IN_PROGRESS | User has begun QA editing, and has saved work. |
REVISION | QA_NEEDED | REVIEW_RESOLVED | User has completed QA editing. |
...