Set up a data patcher role
A Data Patcher role lets an authorised user correct form input values or submission statuses directly through the form interface. This reduces the need to raise a service request for backend data patching, which may be chargeable. The role has no users by default. You add a user when a correction is needed, and you can remove them afterwards.
This guide creates the role and gives it the access it needs. Set it up while you configure the scheme.
Before you enable the role
Review your agency’s internal policies and compliance requirements first. Decide:
- Which approvals you need before you give someone access.
- Which users are authorised to correct data.
- Whether access covers all components or only selected components.
- Whether to remove users from the role after each correction.
- The standard operating procedure and audit requirements for data patching.
Who this applies to
- Audience: Configurators.
- Access required: The Edit permission on the scheme.
- Assumed knowledge: You have a form with its states, edges and components. Refer to Build your form.
Steps
- Create a role named Data Patcher. Refer to Manage scheme roles.
- Give the role the Edit form permission for each relevant form type, in every applicable workflow state. Refer to Set form permissions.
- Give the role transit edge permission for each relevant form type, on every applicable workflow edge. Refer to Set edge permissions.
- Give the role the View and Edit component permissions for each relevant component, in every applicable workflow state. Refer to Set component permissions.
- When a correction is needed, add the authorised user to the role, following your agency’s procedure. Remove them afterwards if your procedure requires it. Refer to Manage scheme roles.
The user can now correct the form inputs and move the submission to the state that it needs.
Constraints and limitations
| Constraint | Detail |
|---|---|
| Set up during configuration | Add the permissions in steps 2 to 4 while you configure the scheme. For what you can edit after go-live, refer to Change a scheme after go-live. |
| Default access | New roles and new states start with no component access. Set component permissions for every combination that the role needs. |
Related features
- Manage scheme roles: create roles and add users to them.
- Set component permissions: apply permissions to many components at once.
