Prevent bypassing sync of new life cycle and legacy fields

[John Cuenca]

Hi all! A bit new to ServiceNow and CSDM. Still working in Washington version here.

As per my understanding, the Business Rules that are allowing the synchronization of legacy field values and new Life Cycle values are the "Update life cycle from legacy" (legacy -> new Life Cycle Stage/Status) and "Update legacy from CSDM" (new Life Cycle Stage/Status -> legacy) with both utilizing the life cycle mapping table.

I've ran into an issue where a lot of CI records have Operational - In Use as their Life Cycle Stage/Status but their legacy field (install_status) is not set to "Installed". I believe this is because some scripts or automations that were implemented have setworkflow(false) or has some functionality to bypass these 2 important business rules.

Is there a way to enforce that these business rules are ran to ensure that both new life cycle and legacy fields are synced? If not, what's the best way to maintain the sync between these fields?

[Kieran Anson]

Hi John,

If lower order BR's are setting setWorkflow(false) then they need to be re-evaluated. setWorkflow is a global toggle for the current transaction and there isn't a way to re-toggle it outside of that BR that executes the command. The same BR could set setWorkflow(true) in the same BR...but that might cause issues if there is a reason for the BR setting it to false.

[Mathew Hillyard]

Hi @John Cuenca 

Have you activated CSDM life cycle mapping? Sync will not happen until they're activated.

There is nothing in the baseline instance that will prevent this sync, so do you have something custom at a lower level?

I hope this helps!

Mat