
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-16-2019 05:11 PM
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
Solved! Go to Solution.
- Labels:
-
Change Management

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-16-2019 10:46 PM
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

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-16-2019 10:10 PM
Hi Karthik,
I would suggest you to deactivate(change the conditions) the current workflows being used or rename them. Then, make a copy of OOB workflows and make them active. This won't cause any issues in existing records and new Changes will be created w.r.t. to new workflows.
Please mark this comment as Correct Answer/Helpful if it helped you.
Cheers,
Hardit Singh

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2019 12:17 PM
Hi Hardit,
I think your idea is wonderful. Since the historical records follow the old workflow there will be no problem. I have one question, if there are any form changes will that effect the historical records?
Thank you,
Karthik

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-16-2019 10:46 PM
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

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2019 10:02 AM
Hi Sanjay,
Thanks for your response. After few investigations I found out that creating an application and capture all changes within that application scope could be the solution.
Thank you,
Karthik