PM5: Improving Pending Approval section

[ei-nghon-phoo]

Background Information:

There are issues with the maker/checker function related to onboarding a participant. Currently, all changes are listed against the participant directly, rather than being placed in the "Pending Approval Requests" section. This lack of consistency creates confusion and makes it difficult for users to manage and track pending approval requests effectively.

Acceptance Criteria:

1. Pending Approval Requests Highlight:

   • The "Pending Approval Requests" menu option should be highlighted or display a number indicating the presence of pending requests that require user action.

2. Pending Approval Subtabs:

   • Add the following additional subtabs under "Pending Approval Requests" to categorize pending requests for better organization and management:
     • Contact
     • Participant Status
     • Account Creation
     • Endpoint
     • Source IP

3. Participant ID in Records:

   • Include the Participant ID in the records, along with other attributes, which are already included in tabs under each participant. This addition will improve the traceability and identification of participants in the system.

Tasks

• [x] Acceptance Criteria pass
• [ ] Unit Tests pass
• [ ] Integration Tests pass
• [ ] Code Style & Coverage meets standards
• [ ] Code Review
• [ ] QA Passed

[PaulMakinMojaloop]

To clarify further: Every action that is subject to maker/checker generates a "pending approval" request. But these requests are not held in one place, despite there being a "Pending Aprroval Requests" sub-menu (which is only used for requests relating to funds movements and NDC changes). All others are all over the place; under individual participants, and under sub-menus within the inndividual participant. When I log on as a checker, I don't want to have to hunt around every where for requests, I want them all in one place so that I know what I need to check and approve.