- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2024 07:21 AM
User can change the change request type when the states are on new, access and authorize and place the record at new state after the change.
Can we switch from one workflow to other ?
Or is there any other approach to implement this.
Thanks.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2024 07:27 AM
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]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2024 07:27 AM
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]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2024 08:59 AM
As @Dr Atul G- LNG points out, once a Change Request record has been created and starts it's lifecycle it's not a good idea to change the 'Change type' or workflow associated (Although it is technically possible but would require heavy customization which Is not recommended)
Thinking out loud however, if users are unsure of what type of change to raise (or changes are often incorrectly created with the wrong type) a simple OOB (Out Of Box) solution to this would be to either create a Record Producer (which is a form) prior to creating the Change record or use the Change Catalog.
The Change Catalog or Record Producer acts as a tool to guide users and depending on the answers to questions determine which type of change is appropriate and creates appropriately. This is a common approach.
To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Kudos.
Thanks, Robbie