Skip to content

Commit 4175d71

Browse files
Merge pull request #20 from OpenSPP/revert-19-refactor-structure
Revert "change_request and enrol_beneficiaries updates"
2 parents 7f933cf + 33ef671 commit 4175d71

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

docs/user_guide/program_management/enrol_beneficiaries.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ In the case of more than 1000 beneficiaries, a yellow notification will display
7676

7777
![](enrol_beneficiaries/4.png)
7878

79-
To manually enrol registrants into a program, first confirm that the import process has been completed. This can be verified by observing the green notification popup for fewer than 1000 beneficiaries, or, for more than 1000 beneficiaries, by refreshing the page until the yellow notification popup is no longer displayed. Once confirmation is received, proceed and click **Enrol Eligible Registrants**.
79+
To manually enroll registrants into a program, first confirm that the import process has been completed. This can be verified by observing the green notification popup for fewer than 1000 beneficiaries, or, for more than 1000 beneficiaries, by refreshing the page until the yellow notification popup is no longer displayed. Once confirmation is received, proceed and click **Enrol Eligible Registrants**.
8080

8181
![](enrol_beneficiaries/enrol_beneficiaries_enrol_beneficiaries_button.png)
8282

docs/user_guide/registry_management/using_change_requests.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
review-status: reviewed
33
review-date: 2025-07-08
4-
reviewer: Mark Penalosa
4+
reviewer: mark penalosa
55
migration-notes: "Added during 2025 documentation reorganization"
66
---
77

@@ -11,7 +11,7 @@ migration-notes: "Added during 2025 documentation reorganization"
1111

1212
This guide explains how to update registrant information in OpenSPP using the Change Request module. The process follows a defined workflow, requiring users with specific roles to initiate and validate requests. Permission-based access and thorough documentation help ensure data accuracy and reliable operations.
1313

14-
## Prerequisites
14+
## Prerequisite
1515

1616
Before submitting or approving change requests, ensure the following:
1717
- Have existing individual records in your registry, either by creating records manually {doc}`register_individual` or importing records into OpenSPP {doc}`import_data`.
@@ -36,7 +36,7 @@ After completing this tutorial, you will be able to:
3636
- Navigate role-specific approval workflows.
3737
- Attach supporting documentation and track updates efficiently.
3838

39-
## Process
39+
# Process
4040

4141
To update a registry record, a change request is initiated by a System Administrator or Registrar. The request is drafted, applicant information is updated for validation, and supporting documents are attached to have a reference for the updating of information. Once submitted, the request undergoes validation by a Local Validator. If approved, it proceeds to an HQ Validator for final review. Upon HQ validation, the change request is applied to the applicant’s record and can be verified through the registry.
4242

@@ -97,7 +97,7 @@ Click **Validate** to partially approve the change request. A success notificati
9797

9898
![](using_change_request/change_request_success_partial.png)
9999

100-
Partially approved change requests are then reviewed by users with HQ validator roles.
100+
Partially approved change requests are then reviewed by user with HQ validator roles.
101101

102102
### Review request by HQ Validator Role
103103

0 commit comments

Comments
 (0)