Coversion Change request Normal change to Stanadard change

praveenkumarr
Tera Expert

The ability to translate Normal changes into Standard changes and Standard changes into Normal changes. Only in the New, Assess, and Authorize states should this be permitted. This should not be permitted if a change is changed to Scheduled.

1 ACCEPTED SOLUTION

Dr Atul G- LNG
Tera Patron
Tera Patron

Hi @praveenkumarr 

 

Answer is NO. The reason 

 

- Both type of changes use the different WF/ Flow.

- For standard change , we need standard change template , so once change raised we cant change the template.

- Both change type follow different state transitions, so it is very tough in WF/ flow to sync. 

- Normal change has Approval and Risk assessment , where standard change dont follow same.

 

So , in short it is not an good idea to convert the Normal change to standard or vice versa.

 
*************************************************************************************************************
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]

****************************************************************************************************************

View solution in original post

7 REPLIES 7

Hi @praveenkumarr 

 

There is no UI action for this, when the change in New state or come to new state from Assess / Auth. then the type field is editable and there you can select the type and when you again click on Request Approval button, it get attached to the Workflow / flow based on type. 

*************************************************************************************************************
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]

****************************************************************************************************************

praveenkumarr
Tera Expert
current.u_type ="normal";
current.update();
//new Workflow().restartWorkflow(current, true);
new WorkflowApprovalUtils().reset(current, comment);
gs.addInfoMessage('Workflow has been reset since key fields have been modified');
 
I have tied to conversion to another change , change type is updating
the Ask was we need the flow to restart again 
i have used the above conditions , If you have any idea to restart the workflow conditions 
please suggest me  

Hi @praveenkumarr 

 

From experience I am telling you, it is wrong requirement & it will increase a technical debt for you mate.

 

The workflow restart based on the cancel condition, means we need to find out the field which get changes and then workflow restart and also not only restart, attach new new workflow based on change type must be attached.

*************************************************************************************************************
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]

****************************************************************************************************************