[Uganda project - Technoforte team] Registration Officer Unable to Reinstate Archived Records Despite RECORD_DECLARATION_REINSTATE Permission

[theyogender]

Summary

Registration Officers are unable to reinstate archived records even when the permission record.declaration-reinstate (keyword: RECORD_DECLARATION_REINSTATE) is assigned to their role in the country configuration. The Reinstate action does not appear in the UI.

Requirement

• Registration Officers with the permission record.declaration-reinstate / RECORD_DECLARATION_REINSTATE should be able to see and use the Reinstate action on archived records.

• This permission should enable reinstatement functionality for any assigned user role.

Current Observation

• Registration Officers have been assigned the permission record.declaration-reinstate / RECORD_DECLARATION_REINSTATE. Despite this, the Reinstate option is not visible when they open an archived record.

• This indicates that the permission is not being respected or is not mapped correctly in the application.

Expected Behaviour

• Registration Officers with the record.declaration-reinstate / RECORD_DECLARATION_REINSTATE permission should see the Reinstate button for archived records.

• The system should check the permission and allow reinstatement accordingly.

Clarification Requested

1. Is the reinstatement permission record.declaration-reinstate / RECORD_DECLARATION_REINSTATE correctly wired in the core workflow?
2. Is there any additional permission or workflow rule required to enable reinstatement?
3. Is the reinstatement action controlled by any internal logic not documented in the country config?
4. What is the recommended approach from the core team to ensure Registration Officers can reinstate records?

[prinzab]

@theyogender This is not a bug. There is no scope to reinstate a record in v.1.9. If you archive a record, you can recreate the record as a workaround.

CC: @euanmillar