- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2022 02:44 AM
When you click on "Request Approval" UI action, the following assignment group field is mandatory in change management.
I would like to know how the assignment group become mandatory? Not seen code though!
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2022 03:25 AM - edited 10-18-2022 03:25 AM
Hey.
This is controlled through an OOTB UI policy called Mandatory - Assignment Group
If you go into it, you can see how it works. But it stops a Change moving on from draft/New states until Assignment group is populated.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2022 03:25 AM - edited 10-18-2022 03:25 AM
Hey.
This is controlled through an OOTB UI policy called Mandatory - Assignment Group
If you go into it, you can see how it works. But it stops a Change moving on from draft/New states until Assignment group is populated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2022 10:00 PM
Despite answer is right, the behaviour of UI policies is totally different. Never seen UI policies works with UI action "Request Approval".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2022 10:04 PM
Hello,
The UI action is not directly making the UI policies work. The UI action is setting the field to assess and authorize and the UI action says if state is one of assess/authorize make assignment group mandatory hence the group field is getting mandatory.
Please mark answer correct/helpful based on Impact.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2022 11:40 PM
Not known UI policy is a client side scripting. Thanks!