Remove ability for HR Agents to be able to create a new task without a Parent Task
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2024 06:36 AM
Hi ,
Currently there's an option NEW to create a task via Agent Workspace, this allows HR Agents to keep a stand alone task and so need to remove the option so tasks can only be created from an HR Case. could you please help how to remove this ?
Thanks

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2024 10:41 AM - edited 12-18-2024 10:42 AM
@Bindhu1 You have to deactivate the Action Assignment record. Here is the path to the record and an Image as well. This will remove the New button for all of the lists for HR Task. URL - YOUR_INSTANCE.service-now.com/now/nav/ui/classic/params/target/sys_declarative_action_assignment.do%3Fsys_id%3D17c13e7273131010a0a79329faf6a794%26sysparm_view%3Dlist_action%26sysparm_domain%3Dnull%26sysparm_domain_scope%3Dnull%26sysparm_record_row%3D2%26sysparm_record_rows%3D4%26sysparm_record_list%3Dmodel%253dc3547169534723003eddddeeff7b126c%255elabel%253dNew%255etable%253dglobal%255eORDERBYDESCsys_updated_on
Here is the record
Here is the result:
If my answer has helped with your question, please mark my answer as an accepted solution and give a thumbs up.
Regards,
Mike
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-19-2024 12:33 AM
Hi Michael,
I did what you suggested , but i still see the New button on HR task, could u please let know where i be wrong ?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-19-2024 04:26 AM
@Bindhu1 I can only assume this is a cache issue. What version is your Agent Workspace for HR Case Management? I can toggle the New button on and off just by activating, then deactivating so if you are at the latest version of the Agent Workspace this should work for you. Try a cache.do, logging off, then on again and let me know the outcome.
Regards,
Mike