Approach to implement Retroactive Change in Emergency type of Change
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2024 07:28 AM
May I know the approach to implement Retroactive Change in Emergency type of Change.
I have a requirement to implement Retroactive Change with a choice field.
If the choice field is selected as Retroactive, then the state allowed should be from New to Review(rather than New to Authorize) and no approvals should be triggered.
If the choice field is selected as Non-Retroactive, the flow should follow OOB Emergency flow.
Any inputs on how this requirement can be implemented would be appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2024 07:35 AM
Hi @Sai Charan8
Greetings!!
OOTB, you can create retroactive change only where type is emergency, where back date are allowed.
There is no need to create a new flag , if you are using the change model, the change model are latest and best in thise case.
You can create a new model, with name retroactive and you can define the state transition as per need.
This video will help you to understand the same. Change model is OOTB and low code.
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]
****************************************************************************************************************