Moving change management to OOB

karthikbabu · ‎10-16-2019

Hi All,

Our change management is highly customized, changed the workflow,built many scripts, ui policies,ACL's, business rules e.t.c. We are thinking to move our change management to OOB.

I can do it by switching off all the scripts, policies,ACL's, and change the workflow to look exactly like OOB. The trouble we will facing is the history of records. I tried to do it in one of our lower instance and lost all the records.

Please suggest the best way.

Thank you,

Karthik

Sanjay Bagri1 · ‎10-16-2019

Hi ,

I think this is not a best solution to back. if you are feeling /thinking this change management is very critical so you can customize according to you business requirement but you can not revert back to only change management .

If there are major changes to be modified in the SN app then the best practice is to create a new scoped application and capture all the changes within that application scope. All the SN app artifacts can be inherited by creating a dependency with in your custom scoped app. This way you get the option to publish an app on multiple instances via "make the app available to other instances". On the other hand, if the changes are minor then you can create an update set in the same SN app /scope and move the changes through the update set.

Please mark as correct and also helpful. if it helping to you .

Thanks

Sanjay Bagri

View solution in original post

Ankita Namdeo · ‎09-23-2020

Hi Karthik

Can you elaborate on how capturing the updates in the scoped application will be helpful. We are in a similar situation where we are planning to shift to the OOB change module from a highly customized one. I understand that changing to OOB workflow would not impact historical change records. However, removing fields from the layout would result in loss of data from the old records. How was that handled and what best practices should be kept in mind before making this shift?

Thank you,

Ankita