Best Practice for Data Deletion in Workplace visitor management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hello Community,
We are currently implementing a data deletion for Visitor Management in Workplace Service Delivery (WSD) and would like to validate the best architectural approach.
Requirement
Visitor-related data must be automatically deleted according to the following rules:
- Completed Visits
- Visitor Registration records should be deleted 60 days after the visit date if:
- The visit took place, and
- Policy documents were approved.
2. Visitor records should be deleted immediately if:
- Visit status is Planned, and
- Policy documents were not approved, or
- The visit did not take place.
3. Future Visit Scenario
- If the visitor has another future visit scheduled, the system should:
- Delete Visitor Registration, Visit, and Visitor Policy Confirmation records after 60 days
- Retain the Visitor master record.
- Attachments : All attachments linked to the deleted records must also be removed.
4. Automation
- Deletion must be fully automated and aligned with the 60-day policy.
We are considering the following approaches:
- Scheduled Script Execution + Script Include
- Flow Designer (scheduled flow with subflows)
Because the logic involves cross-table validation (future visit check) and cascading deletion, we are trying to determine which approach is considered best practice for maintainability and performance.
For those who have implemented similar cleanup mechanisms in ServiceNow:
What approach would you recommend for Visitor Management data deletion with conditional logic?
Any insights or architectural recommendations would be greatly appreciated.
@_raj_esh @Arvid
Thank you!!
