- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2024 01:35 AM
When an RITM is logged we have a task for our L1 team that gets created in the workflow for that catalog item to assess the request and move it along. The assess task should be left with L1 and closed by them but alot of the team they are re-assigning this task to a different assignment group to progress the ticket. Is there a way to lock down a this task which always has the same description so it can't be reassigned to a different group while all other tasks can?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2024 02:40 AM
Hello @lynchr02 ,
You can use before business rule, there you can check the condition and if that satisfied then use current.setAbortAction(true);
That's it, now your issue solved.
Mark ✅ Correct if this solves your issue and also mark 👍 Helpful if you find my response worthy based on the impact.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2024 02:40 AM
Hello @lynchr02 ,
You can use before business rule, there you can check the condition and if that satisfied then use current.setAbortAction(true);
That's it, now your issue solved.
Mark ✅ Correct if this solves your issue and also mark 👍 Helpful if you find my response worthy based on the impact.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2024 08:28 AM
Yeah that worked short description is and assignment group changes as the conditions with additional message in the script