View Source

Target release	3.3
Epic
Document status
Document owner	Sam Im (Deactivated)
Technical Lead	Technical Lead who reviews or supports document

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 but the additional requirements for Supervisory Nodes may require updates to the assignment process.

Assumptions

What are technical or business specific details and characteristics that should be known to explain the environment? List the assumptions you have such as user, technical or other business assumptions. (e.g. users will primarily access this feature from a tablet).

User Stories

Short, simple description of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system.

#	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: View list of all Supervisory Nodes in the system and details associated: SN code, Assigned Facility, Parent & Child relationships, Requisition Groups assigned	Relevant labels to distinguish source. From which system, or which country?	Must Have	Open bug:
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: Ability to create new Supervisory Nodes Assign new Supervisory Nodes an associated facility Assign new Supervisory Nodes to user through User Roles
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: When a requisition group is added to/removed from a supervisory node When a supervisory node is added to/removed from another supervisory node
4	Audit logging for changes to Supervisory Nodes

Diagrams

Include any business process mapping, mockups, diagrams or visual designs relating to these requirements. Describes the tasks and the personas who perform those activities. The diagram provides the context for the user stories and serves as a focal point for achieving clarity and agreement among stakeholders. Looks like a standard flow chart.

Dependencies

Identify initial dependencies that are on the critical path for this functionality and may affect the delivery time and serving of business goals. Include links to stories.

Description	Link
Name of story or release	Link to JIRA

Open Questions

Initial communication between stakeholders and the development team to help understand scope and estimates.

Below is a list of questions to be addressed as a result of this requirements document:

#	Question	Outcome	Status
1	(e.g. How we make users more aware of this feature?)	Communicate the decision reached	Open, In Progress, Closed, and date of closure

Out of Scope

List the features discussed which are out of scope or might be revisited in a later release.