Change management approval policies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-30-2026 05:11 AM
Hello All,
There is a requirement in change management to add one more user or group in assess state. So for this i created ui action button in ui action button i called ui page to show popup to select user/ group. And created one Script include to generate approval for that perticular user/group once they selected. It is working fine.
Now the issue is if someone approve/reject the existing approval then adhoc approvals will be no longer required and videversal if adhoc approval one approves then existing one will be no longer required. so how can i implement this that if change assignment group approves then adhoc approval should remain requested and if adhoc one approves the assignment group approval should remain requested.
Please let me know if any solution i can implement.
Thanks
- Labels:
-
Change Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
Hi @swapnilsoni,
If selecting a user or group is mandatory in the Assess state via the popup, here's an approach you can consider:
- Remove the existing approval policy decisions that are currently triggered for the Change Request in the Assess state
- Deactivate the OOTB Flow(Change - Normal - Assess) associated with it.
- Continue the Change Request process entirely through the Sub flow that is being called from your UI Action
- Within the Sub flow, define the same conditions that were previously handled by the approval policy decisions and drive the Change Request forward from there.
Hope this helps! If this resolves your issue, please mark it as Helpful or Accept it as the Solution.
Regards,
Harish
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
Hi @swapnilsoni,
If selecting a user or group is mandatory in the Assess state via the popup, here's an approach you can consider:
- Remove the existing approval policy decisions that are currently triggered for the Change Request in the Assess state
- Deactivate the OOB Flow(Change - Normal - Assess) associated with it.
- Continue the Change Request process entirely through the Sub flow that is being called from your UI Action
- Within the Sub flow, define the same conditions that were previously handled by the approval policy decisions and drive the Change Request forward from there.
Hope this helps! If this resolves your issue, please mark it as Helpful or Accept it as the Solution.
Regards,
Harish
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
Hi @HarishKumar6668 ,
Deactivating the oob change "Change - Normal - Assess" and driving through a subflow is not the best practises , try to use some custom fields , tweak the flows and approvals policies
Thanks regards
Badrinarayan
