To ensure better data integrity within the Organization Management (Admin) module, we have implemented a feature that blocks the ability to delete referenced and related departments, roles, users, and groups. This improvement addresses a critical issue that caused forms to crash after their referenced data was deleted.
How It Works:
- If a user, role, department, or group is directly associated with any form or process in the system, the application will automatically prevent its deletion.
- Data Integrity Scenarios
For example, let’s consider the role of Auditor in our system.
- If the Auditor role is referenced in a form or workflow, it will be blocked from deletion.
- If the Auditor role is referenced in a form or workflow and the users assigned to that role are not directly implicated, only the role will be blocked from deletion.
- If the Auditor role is referenced in a form or workflow and the users assigned to that role are directly implicated, both the role and its assigned users will be blocked from deletion.
- If the Auditor role is referenced in a form or workflow and the users assigned to that role are not directly implicated, only the role will be blocked from deletion.
- If a form or workflow references a specific user assigned to the Auditor role (rather than the role itself), the role can be deleted.
- If a form or workflow designates the Auditor role as the assignee, and a specific user under that role submits the form, the role will be blocked from deletion.
This concept of direct implication also applies to departments and groups.
- If the Human Resources department is referenced in a form or workflow and the role assigned to that department is not directly implicated, the assigned role can be deleted.
- If the Documentation Team group is referenced in a form or workflow and the users assigned to that group are not directly implicated, the assigned users can be deleted.
- If the Auditor role is referenced in a form or workflow, it will be blocked from deletion.
Post your comment on this topic.