Differences between "v1" and "v2" Display Mode

Groups without Group-level requirements

In v2 mode, in order to be considered “complete”, a Group must have some definition of what “complete” means.

  • A Task Group that has Group-level requirements is “complete” when those requirements are met.

  • A Task Group without Group-level requirements will match the status of the overarching Requirements Model. If that model is complete then the Group is considered complete, and vice versa. (In this case the Requirements Model is the only indicator we have of completeness, so we apply it to groups as well)

  • A Task Group without Group-level requirements, and when no Requirements Model exists, will ALWAYS be “incomplete” (blue). If there are no definitions of “complete” to be found, we assume that the notion of “completeness” is irrelevant for this application.

 

Task Group color for Locked Task Groups

In v1 mode, a “locked” Task Group had the same coloring as an active Group. The locked status simply meant that:

  • There was no “Add Activity” button

  • The Complete Activity workflow button was in “passive” mode, with no Quick Actions

In v2, a locked group now has a dedicated color (gray) and a locked icon so that its status is more clearly evident.

 

 

Owner Incomplete tasks show the Passive button label when in a locked Group

In v2 mode, all incomplete tasks within a locked Task Group will show the Passive button text in the Practitioner area.

In v1, an Owner Complete task would have shown the Passive button text, but an Owner Incomplete task would have shown the Active text. Since the user is not able to work on the task in this state, we have switched to use the Passive text.

TODO

In v1 mode:

  • REQUESTED units were used to determine the state of the LPI WF button, but

  • GRANTED units were used to determine the color of a Task Group

The use of granted units in this case was a long-standing defect. It was fixed in v2, which now uses REQUESTED units for both.