- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-14-2015 05:42 AM
Greetings everyone,
My ServiceDesk is in need of adding new, blank tasks to existing request items.
Right now, we have a MISC request form that we utilize for any requests that are not featured in our Service Catalog. Currently the workflow only makes on task and assigns that task to our ServiceDesk.
As an Admin, I am able to create new tasks on existing Request Items (see screenshot below), however, I am unable to get normal ITIL users this ability. I have attempted to add the task_editor, rm_task_admin, and rm_task_user roles to a test user but have yet been able to get this new task button to show up for anyone other than admin.
Can anyone provide any insight on how to get the "New" button to show up for ITIL users via a role?
Thank you in advanced!
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-14-2015 05:47 AM
Check the create ACL's on the table and see how it defined.. You might need to edit it to open up the new button .. Once the user has access at table level, the new button will start appearing automatically as it is a global button.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-09-2018 11:10 AM
I know this is an old post but has anyone got a solution to this.
Main Issue: ITIL users need the ability to created Ad Hoc Tasks on the Requested Item
2nd Issue (mentioned by Robert): The Manual Tasks will not affect the workflow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-09-2018 04:06 PM
Hey Zachary,
Typically what happens is that you add a Script activity at the end of the workflow that checks for open sc_tasks with the RITM as the parent. Only if that evaluates as true do you move the RITM workflow to complete. Whenever an sc_task closes a business rule "tickles" the workflow, which will re-evaluate whatever activity its currently on. In this case, the script activity. It *should* prevent the RITM from closing until all tasks (manual or otherwise) have been closed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-18-2018 09:13 AM
This is not helpful. HOW can an RITM close if it still has TASKS??? It should NOT close if it has even one open task. People can bug the human(s) involved to finish / close their task(s), but ... this is a HUMAN problem, and SN should simply wait for its humans.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-24-2022 09:17 PM
because the additional tasks were not taken into account on the running workflow.