Supervisory Nodes Configuration Errors

Description

Create a table that lists all configuration errors for Supervisory Node assignment and links to where to fix.

Acceptance Criteria:

Ability to generate a list of all Supervisory Nodes with missing assignments
There are two tables that generate in this report: First is "Supervisory Node missing a Requisition Group", the second is Supervisory Node missing Approve right
Supervisory Node is missing Requisition Group assignment: Supervisory Node does not have an assigned Requisition Group Report should list the records that are missing assignments and the following columns:

Supervisory Node Code	Supervisory Node Name	Requisition Group Code	Requisition Group Name
SN01	FP Approval Point	null	null
SN1.1	FP Approval Subpoint	null	null

(These records are missing an assigned req group. This scenario can happen when there is a bulk upload, but is not possible when creating a Supervisory Node via admin UI)
Supervisory Node missing an Approve requisition role: A Supervisory Node is missing a Supervision role type assignment, and/or the Requisition Approve right.

Supervisory Node Code	Supervisory Node Name	Username	Role Type	Role Name
SN01	FP Approval Point	dsrmanager	Supervision	requisition viewer
SN1.1	FP Approval Subpoint	psupervisor	null	null

(The first example shows the Role type is Supervision, but the Role is as requisition viewer, and does not have approve rights. The second example the Supervisory Node is missing a user that is assigned a Supervision Role Type.)
When records are updated correctly and the report is rerun the records should not appear anymore
When the report is run and there are no records, the report shows both tables with "No records missing assignments"
Report shows the date it is generated
This new report is located in View Reports and is called "Supervisory Nodes Missing Configuration"
User with Admin Type rights for MANAGE_ and Report Type rights of VIEW_REPORTS, is the only user able to run these reports. Users without these rights should not be able to view the report in View Reports tab
Report formats should match existing Jasper formats

Assumptions:
In version 2.0, an example of this type of report is under Reports > Admin Reports.

QAlity Plus - Test Management

Checklists

Activity

Sebastian Brudziński

August 10, 2017 at 8:23 AM

@Sam Im A few comments
1. The first table shows SupervisoryNodes that do not belong to any requisition group. I believe it doesn't make sense to have columns for RG name and code as those will always be null.
2. Is the second table meant to show all supervisory nodes that do not have any user role assignments? I guess I do not understand why is it connected with user. If my instance has got 300 users, am I supposed to list a supervisory node and 300 users?
3. One thing that the Malawi was validating is that all final supervisory nodes (no parent) are assigned to SupplyLines. Note, that this may not necessarily be an error though. For programs that do not want to convert to order, final supervisory nodes do not need supply lines. For ordering programs though, if final SN does not have a supply line, the requisitions of that program would not be eligible for conversion to an order.

Sam Im

August 9, 2017 at 9:57 PM

@Sebastian Brudziński here is another ticket we want to work on in the coming sprint. This report is supposed to identify any configuration errors for a Supervisory Node. Any missing data that could cause the requisition approval process to fail should be reported here. Do you have any suggestions for scenarios I haven't covered here?

Resize work item view side panel

Pinned fields

Click on the next to a field label to start pinning.

Details

Assignee

Unassigned

Reporter

Sam Im(Deactivated)

Labels

Administration

Components

Reference Data

Priority

Major

Parent

OLMIS-4070 Admin screens after 3.3 release

Time Assistant

Created June 27, 2017 at 9:28 PM

Updated February 8, 2023 at 1:29 PM