Architectural Considerations
When it comes to regulatory needs, Spira platform follows the strict compliance of the "state-driven" workflow engine. These needs are often different from adaptive/hybrid team needs.
State Driven Compliance Needs
The workflow engine controls both the state level controls and the transition level governance includes the following:
State Level Controls
- The available operations to move a single artifact item from its current state to another state
- The visible, mandatory, and immutable nature of the fields at these states
Transition Level Controls
- The roles and responsibilities of the people that can perform the operation (following the RACI standards upheld by auditory compliance)
- The electronic signature controls on specific operations to uphold the 21 CFR Part 11 considerations
Adaptive and Hybrid Team Needs
In high-speed team delivery (Lean, Scrum, Kanban, and ScrumBan) approaches, their needs revolve around the need to minimize friction and eliminate delay. This is one of the reasons why boards were created for the team to drag-and-drop artifact items across the state because team level decisions exist as part of the definition of done or acceptance criteria instead of mandating compliance. So, the convenience to move items override the need for transition and state level controls.
List View: Challenges in Resolving Convenience over Compliance
The following challenges arise when the need to honor the workflow rules are needed with the convenience of the bulk edit in the list views.
- When a user selects multiple items in a list view, those items may have different statues (e.g.: Item A may be in Draft, Item B in Under Review, and Item C in Tested).
Each status exposes a completely different set of available transitions and downstream rules. For example, an item A in "Draft" may require the "Review Artifact" transition to move to "Under Review" whereas an item B already in "Under Review" has two distinct options: "Approve Artifact" (moving to "Approved") or "Reject Artifact" (returning to "Rejected"). This makes it difficult to evaluate at run time in these list/board views what sequential transitions need to be performed validating the workflow rules before moving it to the final state.
Even within the same status, different transitions carry different gated compliance needs. For instance, the "QA Approve Artifact" transition may require an electronic signature by a "QA role" followed by "SIT Approve Artifact" with another level-2 electronic signature by a "Validation Manager" besides the various mandatory sign-off fields.
Therefore, executing a bulk edit across heterogeneous states with various transitions, fields, and governance rules forces the system to flatten or bypass item-level workflow rules. Consequently, enabling unrestricted bulk edits breaks state-machine compliance, while enforcing compliance requires disabling heterogeneous bulk edits.
Board View: Challenges in Resolving Convenience over Compliance
Teams practicing Agile, Scrum, or Lean/Kanban prioritize visual flow, team-level autonomy, and the elimination of handoff delays. Dragging a card across columns on a Kanban board is designed to be an instant, low-friction status update.
A drag-and-drop gesture on a board simply changes a status value; it is not built to pause execution to render complex, state-specific forms, enforce newly mandatory fields, or validate entry/exit criteria.
Allowing a user to drag a cards from one status to another status column without inspecting the full record bypasses the transition-level electronic signature challenges
As a result, teams use tasks on the requirements as a means to evaluate the definition of done and move them along the status spectrum. The same logic applies on the incidents observed by using acceptance criteria.
Solution
When compliance is really important, then, the convenience of bulk edit should be disabled so that the appropriate compliance lifecycle can be enforced by governance. But, if convenience is desired more, then, the bulk edit can be enabled but compliance workflow rules cant be enforced.