- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-25-2018 01:26 PM
We are facing a requirement that every time a user replies to a ServiceNow Notification sent out of a task, the reply should be targeted to the task so that it is visible in the activity formatter. This should happen to all task types: Problems, Incidents, Project Task, Demands, Requests and so on...
I really want to avoid the redundancy of creating an Reply Inbound Action for each task table. To do this I created an generic Inbound Action with Type "Reply" and Target Table "Task" with a simple code:
current.work_notes = "E-Mail Reply Received"
current.update()
As "Task" is a parent table I was assuming that the Inbound Action is inherited to all Child Tables as well. However, if I sent an reply mail to an Incident the Inbound Action will always be skipped:
Skipping "Link to task", email is a reply, and the record it matches is not in the Inbound Email Action's table
Business rules and UI Actions are inheriting per default, and UI Policies and Client Scripts are having a "Inherit" checkbox. But where can I enable inheriting of Inbound Action to child tables (e.g. Problem, Incident, Request, Project Task)?
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-25-2018 01:35 PM
Hello Niclas,
I doubt you can extend inbound actions to child tables. An inbound action is only specific to each table.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-25-2018 01:35 PM
Hello Niclas,
I doubt you can extend inbound actions to child tables. An inbound action is only specific to each table.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-25-2018 08:24 PM
Inbound action with Type and Target Table set to "None"
I was just thinking setting Table - None might work for you. But looks like that is also not an option.
You will require to configure inbound action separately then.
A common script include will do the trick but you require to have separate inbound action.