How to rename BCM Plans No Matter the State
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
We are using the ServiceNow BCM module and need to be able to safely rename our BCP (business continuity plans) no matter what state they are in (for BCM administrators). For example, if they are submitted for approval, we need our BCM admins to be able to rename the plans and have the action be recorded in the activity log (old and new). Can the community please advise?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
To allow BCM admins to safely rename Business Continuity Plans regardless of their approval state, you need to relax/loosen the field-level restrictions while keeping table-level auditing active. By default, ServiceNow locks down records once they enter states like Pending Approval or Approved. To bypass this specifically for plan names, you will want to update or create a field-level write ACL on sn_bcm_plan.name (or your specific BCM plan table) that explicitly grants edit permissions to the sn_bcm.admin role without state conditions. Additionally, check your UI Policies and Data Policies on the plan form—make sure the name field is set to "Leave Alone" or excluded from the policy rules that make fields read-only when a plan is submitted, ensuring admins aren't blocked on the client side.
As long as auditing is enabled on the BCP table, any title changes will automatically log directly into the Activity Stream. The moment a BCM Admin updates the name, ServiceNow generates an entry showing the exact timestamp, who made the change, and the old value transitioned to the new value (e.g., Old Plan Name ➔ New Plan Name). Any in-flight approval tasks will automatically reference the updated plan name when approvers view the record, ensuring complete transparency without breaking active workflows or losing historical context.
