1. Users
1.1. Issues
1.1.1. The user could be the only actor in some departments
1.1.2. The user could be the only actor in some groups
1.1.3. User could be in active flow instances
1.1.4. The user could be an actor in workflows
1.2. Approach
1.2.1. Check if the user is in issue state (4)
1.2.1.1. Yes
1.2.1.1.1. Don't let them continue
1.2.1.1.2. List the issues we detected
1.2.1.1.3. Nice to have (base on cost) - provide the user a warning about condition (1) & (2)
1.2.1.2. No
1.2.1.2.1. Archive user
1.2.2. Notes
1.2.2.1. Any running flow instances (3) that refer to this group will need be manually withdrawn/cancelled
1.2.2.2. Any empty groups/departments (1) (2) will also be will
2. Department
2.1. Issues
2.1.1. Dept could have several workflows published to them
2.1.2. Users must exist in a department
2.1.2.1. User must be reassigned
2.1.2.2. Or constraint removed
2.1.3. The dept could be an actor in workflows
2.2. Approach
2.2.1. Check if the department is in any of the issue states (1) (2)
2.2.1.1. Yes
2.2.1.1.1. Don't let them continue
2.2.1.1.2. provide a detailed error message
2.2.1.2. No
2.2.1.2.1. Archive dept.
2.2.1.2.2. All in progress flows would still refer to the archived dept.
2.2.2. Notes
2.2.2.1. Any running flow instances (3) that refer to this group will need be manually withdrawn/cancelled
3. Entities
3.1. User
3.2. Departments
3.3. Groups
3.4. Catergories
3.5. Other candidates
3.5.1. Flows
3.5.2. Clients
4. Categories
4.1. Possible issues
4.1.1. Category exists has some published flows
4.1.1.1. Can't run things
4.2. Approach
4.2.1. Check if there are any flows published under this category (1)
4.2.1.1. No
4.2.1.1.1. Simply mark the DB record as archived (flag)
4.2.1.1.2. The system no longer ever sees that category
4.2.1.2. Yes
4.2.1.2.1. Don't let them proceed & provide them the user a detailed error message
5. Groups
5.1. Issues
5.1.1. The group could be an actor in workflows
5.1.2. Groups could have several workflows published to them
5.1.3. The groups could have some flow instances that are running
5.2. Approach
5.2.1. Check if the group is has issues (1) or (2) above
5.2.1.1. Yes
5.2.1.1.1. Don't let them continue
5.2.1.1.2. provide a detailed error message
5.2.1.2. No
5.2.1.2.1. Archive group
5.2.1.2.2. All in progress flows (3) would still refer to the archived group
5.2.2. Notes
5.2.2.1. Any running flow instances (3) that refer to this group will need be manually withdrawn/cancelled
6. Generic features
6.1. Add archived flags to Groups/Users/Dept/Category
6.1.1. Archived X's are not visible in the portal by default, but there is a "show archived X" type functionality