Migrating to Change Models

Go to solution
shloke
Tera Contributor

‎11-21-2023 03:41 AM

Hi,

 

We already have change request module implemented in our instance and we are planning to design an enterprise change using new flow designer and change model concept in ServiceNow.

 

I would like to get some thoughts on some of the best practice recommendations from experts here, like can we have both legacy thing running and implement new change flow for enterprise change management.

 

Issue: We cannot deactivate the legacy change using workflows all of a sudden and will require a phased approach. 

Can we tweak the OOTB interceptor to redirect users to new model UI and also keep the legacy interceptors as well?

 

Technically , it is feasible but would like to know on best practices on above.

 

Regards,

Shloke

0 Helpfuls
  • 3,567 Views
1 ACCEPTED SOLUTION

Go to solution
scott barnard1
Kilo Sage
In response to shloke

‎11-21-2023 05:46 AM

Hi Shloke

Looking at change flows rather than workflows they seem to evaluate the records based on type and model. So for example If I have a change model called "normal change" and create a change request of the "Normal" type, that does not have a model defined, the old workflow fires.

 

If  I then create a change with the model defined as "normal change" and the type as "normal change" the workflow does not fire and the flow design based on normal change does.

 

This is in a PDI so it looks possible but I need to check on the run conditions for the customized workflows that we use but it looks like it's possible to run in parallel as long as you have set models for alternate paths.

 

So In my case no model and normal change means follow the workflow and old behaviour.

Then I would need models for my local, regional and global pathways.

 

Regards

 

 

 

View solution in original post

5 REPLIES 5

Go to solution
Dr Atul G- LNG
Tera Patron
Tera Patron

‎11-21-2023 04:03 AM

Hi @shloke 

 

We already have change request module implemented in our instance and we are planning to design an enterprise change using new flow designer and change model concept in ServiceNow.

Atul: It is really good, if you are want to use flow designer and build a new model.

 

I would like to get some thoughts on some of the best practice recommendations from experts here, like can we have both legacy thing running and implement new change flow for enterprise change management.

Atul: Both (Model and Interceptor) running at same time, I doubt but. You need to do some property changes if i remember correctly. But yes, flow and WF both can work.

 

Issue: We cannot deactivate the legacy change using workflows all of a sudden and will require a phased approach. 

Can we tweak the OOTB interceptor to redirect users to new model UI and also keep the legacy interceptors as well?

Atul: That's not an issue, build new model and make it visible for few team for a good testing. Check these properties. Give a try in PDI. In my training, i showed both old and new way and with help of these properties only.

 

AtulyaLNG_0-1700568187771.png

 

 

Technically , it is feasible but would like to know on best practices on above.

 

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************
0 Helpfuls