Job Manager - Bulk Update suggested Notification Process
Incorrect Bulk Update and Suggested Notification Process
Example Scenario:
On Job Manager, a staff member accidentally selected all active jobs and changed their status from “In Progress” to “Completed” using the bulk update feature.
Impact:
Over 150 jobs were marked as completed.
Workflow visibility was disrupted, and deadlines were missed because jobs disappeared from active lists.
Root Cause:
Bulk update permissions were too broad.
No audit trail or alert triggered when job states changed.
Recommended Controls:
Trigger Email Notifications for Job Status Changes/Setting up email alerts
Detecting incorrect bulk updates
Reverting changes quickly Options
Require confirmation before applying changes to more than X jobs.
Any bulk status change sends an email to the Job Manager or Admin team.
Include details: User who made the change, number of jobs affected, old status → new status.
Arnie Francisco
shared this idea
Thanks for sharing this idea with us. We appreciate you outlining how safeguards around bulk updates could help teams manage workflows in XPM.
This idea is now in Gaining support status, meaning the community team have reviewed it and it's open for community support through votes and comments. We encourage others who'd find this helpful to add their votes and share their experiences.
In the meantime, it is worth noting that a custom job notification for job state change could be created in your XPM account if you haven't done so already.
