Supervisory Nodes
Target release | 3.3 |
|---|---|
Epic | |
Document status | IN DEV |
Document owner | @Sam Im (Deactivated) |
Technical Lead |
Goals/Scope
The goal of this requirements page is to document the feature of Supervisory Nodes and the associated user stories. Supervisory Nodes are the control point that route requisitions through their approval hierarchy.
Scope: This feature includes stories on:
Viewing existing Supervisory Nodes and their assigned Requisition Groups.
Creating new and editing existing Supervisory Nodes.
Audit logging
Background
Assigning Supervisory Nodes was part of the User Roles feature, and was completed in https://openlmis.atlassian.net/browse/OLMIS-2215 but the additional requirements for Supervisory Nodes may require updates to the assignment process.
Assumptions
User Stories
# | Title | User Story | Label | Importance | JIRA Tickets |
|---|---|---|---|---|---|
1 | View existing Supervisory Nodes | As an admin I want to view existing Supervisory Nodes so that I can see the system's approval hierarchy. Acceptance Criteria:
| Must Have | ||
2 | Create new Supervisory Nodes | As an admin I want to create new Supervisory Nodes so that I can support business needs for new approval points. Acceptance Criteria:
|
|
| |
3 | Edit existing Supervisory Nodes | Currently, right assignments are changed when a user's role assignments are changed, which is fine for direct and fulfillment role assignments. However, for supervisory structural changes, right assignments need to be refreshed in order for them to stay in sync with the supervisory structure. Some scenarios:
|
|
|
|
4 | Audit logging for changes to Supervisory Nodes |
|
|
|
|
Diagrams
Dependencies
Description | Link |
|---|---|
Open Questions
Below is a list of questions to be addressed as a result of this requirements document:
Question | Outcome | Status | |
|---|---|---|---|
| 1 |