| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| 712:dependentelements [2025/12/15 19:05] – ['Comment' vs. 'State'] Fryer, Kathryn | 712:dependentelements [2025/12/15 19:11] (current) – [Behavior of readiness checks with work product states] Fryer, Kathryn |
|---|
| |
| |
| ===== Tailoring of a Work Product State ===== | ===== Tailoring a Work Product State ===== |
| |
| Work Product states can be tailored in or out, like any other process element. This can be done by selecting specific states using the right arrow selection next to the work product. This tailoring allows further refinement of allowable states in a given project type. | You can tailor a Work Product state or quality level in or out, like any other process element. Tailoring allows further refinement of allowable states and quality levels in a given project or project type. |
| | |
| | When configuring the Tailoring wizard, select specific states or quality levels using the right arrow selection next to the work product. For manual tailoring, you can remove or add a state or quality level using its context menu in the States or Quality Levels widget. |
| |
| {{ https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/78/wptailoring.png?900x645&nolink }} | {{ https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/78/wptailoring.png?900x645&nolink }} |
| | |
| |
| ===== Reporting API Extensions ===== | ===== Reporting API Extensions ===== |
| ===== Behavior of readiness checks with work product states ===== | ===== Behavior of readiness checks with work product states ===== |
| |
| Process version readiness checks that check **association constraints** run **only on the work product** itself, not independently on each state. The input for an association constraint check will be the associations of the work product itself, merged with the associations of all states. For instance: | Process version readiness checks run when you manually add a new version of a process. The checks for **association constraints** run **only on the work product** itself, not independently on each state. The input for an association constraint check will be the associations of the work product itself, merged with the associations of all states. For instance: |
| |
| * "Each work product is an input to at least one activity": It is sufficient that the work product (or any state) is input to an activity | * "Each work product is an input to at least one activity": It is sufficient that the work product (or any state) is input to an activity |