The platform now includes enhanced logic to ensure historical accuracy of records while maintaining clear ownership of in‑flight (Open) work when referenced users become inactive. These enhancements apply across all modules and are designed to prevent workflow bottlenecks, preserve audit integrity, and ensure accurate representation of past user actions.
The behavior varies depending on record status (Open vs. Cancelled/Closed/Resolved) and the activation state of referenced users.
Core Behavior Enhancements
1. Preservation of User Details for Historical Records
For records in Cancelled, Closed, or Resolved status:
When a referenced user becomes inactive, the record continues to display the user’s name and details exactly as they were at the time of closure.
No fields are cleared, replaced, or automatically updated.
This ensures historical accuracy and prevents alteration of past work ownership.
2. Automatic Clearing of User Fields on Open Records
For records in Open status:
When a referenced user becomes inactive, applicable user fields—such as Assigned To, Owner, or other role‑based selectors—are automatically cleared.
Cleared fields become immediately editable, ensuring smooth reassignment.
This prevents inactive users from blocking active workflows.
3. User Selectors Show Only Active Users
When editing Open records:
User selection fields list active users only.
Inactive users are excluded from dropdowns, searches, and lookup dialogs.
This avoids accidental reassignment to non‑active users.
4. Reopening Records with Inactive User References
When a Closed or Resolved record is reopened:
If any user field contains a reference to an inactive user, the system:
Clears the affected fields.
Flags them for required reassignment.
This ensures the reopened record reflects current organizational ownership.
5. Auditing Deactivation‑Triggered Changes
Whenever the system clears a field due to user deactivation:
An audit log entry is created capturing:
The previous value (e.g., user name)
The event (user became inactive)
The affected record
Audit entries preserve traceability and support compliance requirements.
6. Reactivation Does Not Restore Cleared Values
If a user is later reactivated:
The system does not automatically repopulate any fields that were previously cleared due to deactivation.
Reassignment remains a manual, intentional action to avoid accidental ownership reversion.
Summary of Status‑Based Behavior
Record Status | If Referenced User Becomes Inactive | Behavior |
|---|---|---|
Open | Assigned user becomes inactive | User fields cleared → editable → active users only in selectors |
Closed / Resolved / Cancelled | Referenced user becomes inactive | User fields preserved as‑is for historical accuracy |
Reopened Closed/Resolved | Contains inactive user references | Fields cleared + flagged for reassignment |
Any | User reactivated | Previously cleared fields not restored |
Notes
These rules apply to all modules using status‑based workflows and user‑referencing fields.
No changes occur until the user activation state transitions from active → inactive.
System‑generated audit entries ensure compliance and maintain a reliable historical trail.