Differences

This shows you the differences between two versions of the page.

--- 712:dependentelements [2025/12/15 18:56] – [Use state and quality level templates] Fryer, Kathryn
+++ 712:dependentelements [2025/12/15 19:11] (current) – [Behavior of readiness checks with work product states] Fryer, Kathryn
@@ Line 73: / Line 73: @@
 ===== 'Comment' vs. 'State' =====
-Modelers can continue using the commenting feature for work products. To add a comment, the modeler has to be click or tap on the three dots of a work product used as an output or an input and select 'Edit Comment'.
+Before Stages fully implemented work product states, modelers could use comments on an input/output association to represent a work product state.
-**Note**: Once the comment has been entered, hit on return or Enter key of your touch screen/keyboard to save the comment.
+While informative, such comments are not reusable, manually entered and maintained as free text, which is prone to errors. Work product states enable reuse across the process, including propagating name changes, like other elements.
-This comment is a free text field and is not reusable. Hence, any state updates to work products should not be added as a comment, but modeled using the work product ''State'' feature.
+Although you can still add comments to work product associations, we strongly recommend you use the states and quality level features instead. You can still add comments to work product and other associations to add information for other purposes.
+To add or edit a comment, select the context (three-dot) menu to the right of the association and select Edit Comment. After typing the comment, hit Enter or return to save it.
 {{ https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/78/wpcomment.png?400x146&nolink }}
-Unlike commenting, state feature allows synchronization of a change (like renaming of state name) across Stages just like any other process element (''work product'', ''guidance'', etc) modeled in Stages.
-===== 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 }}
 ===== Reporting API Extensions =====
@@ Line 100: / Line 104: @@
 ===== 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