Details
-
Task
-
Resolution: Completed
-
Medium
-
None
-
RP Sprint 109, RP Sprint 108
-
GxP
-
A
Description
Problem Statement
Some AFWs have been generated and routed for approval, but never reached the "approved" status.
We have observed multiple entries in the AFW master table with name as “AFW_Role”, which have signature required as “Yes”.
Also, these roles do not have any NTID/email ID tagged to them.
That’s why even when the approvers approve the request, the AFW_Role entry stops the AFW from moving the “Approved” status
Acceptance Criteria
- Enforce the documentation of all stakeholders lines with a proper NTID. This should be a pre requisite for the AFW routing.
- Enforce documentation with a pop up message either mandating the user to document a proper NTID, or asking them to delete the line