- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2024 07:53 AM
How to lock down Change Task so the user (non-change_manager or non-admin user) cannot move task from the Open state back down to the Pending state? We have users moving their CTASKs back to Pending state while the Change is in Implement state. We need the CTASK to remain in Open state until the user has completed their testing and they should then close their CTASK. I was hoping for something out of the box, but I'm not seeing anything.
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2024 08:50 AM
Easiest way is to use an onLoad client script to check to see if the user does not have the roles you specified and then if the change task is NOT currently in the Pending state remove Pending from the choice selections by using the g_form.removeOption.
Then you should probably add a business rule to abort any update that changes the state to Pending when the users does not have the roles.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2024 08:50 AM
Easiest way is to use an onLoad client script to check to see if the user does not have the roles you specified and then if the change task is NOT currently in the Pending state remove Pending from the choice selections by using the g_form.removeOption.
Then you should probably add a business rule to abort any update that changes the state to Pending when the users does not have the roles.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2024 09:18 AM
Thank you Drew! That worked!