Life Cycle Mapping Legacy Values

[ameliom]

Hi Everyone, we are working through migrating to using Life Cycle Stage and Status and updating our mapping table. However, since we have activated the plugin before our mapping was finalized. We are seeing CIs that have a lifecycle stage and status that does not reflect our mapping table. These would be CIs that received their life cycle stage and status before the mapping was finalized. For example we are seeing some CIs that have CI status Retired and Life Cycle Stage and Status= End of Life Disposed. But our mapping table shows that CI status Retired should be mapped to end of life retired. When you update the record with something like a period in the work notes, it seems to trigger the life cycle stage and status to be updated as well. 

TLDR: Need a solution to trigger updates to record so that they receive the correct life cycle stage and status from the mapping table.

So my question is how do we trigger all of our records to be updated without having to do something like add a "." to the work notes or modify any values on each record.

Let me know if I have missed the mark with a solution for this and if there is a better way to do this. Thank you!

[ameliom]

Anyone that stumbles upon this page looking for a solution... I was able to figure out a fix script that does it without having to modify the records. You can call this method from the OOB lifecycle util.

var util = new global.LifeCycleUtil();

util.updateFromLegacy(className, gr);

Then you can also set 

gr.autoSysFields(false);

So that it doesn't update any of the updated by or updated date fields.