| |
| 712:consistency [2025/09/15 14:55] – created - external edit 127.0.0.1 | 712:consistency [2025/12/15 20:10] (current) – Fryer, Kathryn |
|---|
| Process consistency is especially important when creating new processes. | Process consistency is especially important when creating new processes. |
| |
| To perform consistency checks, go to ''Management > Process Versions'' and choose the ''Check Readiness'' operation in the "Working Version" menu. | To perform consistency checks, go to ''Management > Process Versions'' and choose the ''Check Readiness'' operation from the context menu for the Working Version. These checks also run automatically when you click Add version to create a new process version. |
| |
| [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=51d1dc&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/72/checkreadiness.png|{{ https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/72/checkreadiness.png?direct&900x370 }}]] | [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=51d1dc&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/72/checkreadiness.png|{{ https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/72/checkreadiness.png?900x370 }}]] |
| |
| Several consistency checks will be performed in parallel, e.g. | Multiple consistency checks are performed in parallel, for example: |
| |
| * Does every activity have a responsible role? | * Does every activity have a responsible role? |
| Customized consistency checks can be added upon request. | Customized consistency checks can be added upon request. |
| |
| They show either a green checkmark if there are no findings, a yellow warning if there are minor findings that might be ignored, or an orange warning if there are major findings that should be corrected before release. | The results show a green checkmark if there are no findings, a yellow warning for minor findings that you could ignore, or an orange warning for major findings that should be corrected before release. |
| |
| {{ https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/72/consistencycheck.png?direct&800x412 }} | {{ https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/72/consistencycheck.png?800x412&direct }} |
| |
| To fix inconsistencies, open the list of findings and go to the respective elements. If you are using a desktop browser, you can open the link in a new tab or new window, edit the element, and close the tab or new window again. Then use the browser reload function to re-run the consistency checks. | To fix inconsistencies, open the list of findings and go to the respective elements. If you are using a desktop browser, you can open the link in a new tab or new window, edit the element, and close the tab or new window again. Then use the browser reload function to re-run the consistency checks. |
| |
| The consistency checks are customizable, so contact your Stages consultant to get more info on its flexibility. | You can also purchase a separate Readiness Check report that can run even more consistency checks against one workspace or a hierarchy, and can generate Excel output for easier tracking. The The consistency checks and the report are both customizable; contact your Stages consultant for more information. |
| |
| |