
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hello all,
I have added "Interaction realated record >task" related record in the incident form but its not visible still on the related records if i go to inteaction and click on icreate incident and if one incident gets created then this related record is visible but without that it is not visible.
I want to achieve this so that the fulfillers can directly attach the interaction from incident form directly.
How i should achieve this?
@Ankur Bawiskar any input on this?
Regards,
Debasis
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
16 hours ago
I will recommend to explain your customer what's the best practice and why you should avoid the reverse flow.
Not all requirements are meant to be implemented as they might require maintenance going forward as they deviate from standard OOTB process.
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
13 hours ago
You can create multiple incident, change, request and case as part of an interaction based on valid needs of the user.
See below for a sample interaction where multiple tasks are created,
Recommendation is do not try to relate existing tasks to an interaction. You can imagine a scenario, you are calling or chatting with Amazon help desk and they are creating multiple requests or support tickets on your behalf. To identify, as part of which interaction these requests are created, you can use interaction reference. For any records, created outside interaction it would not be meaningful to link it to an interaction as source of creation if those records were not created from an interaction.
Go through Interaction Management module in Now Learning if you need more information and below is reference documentation
As per community guidelines, you can accept more than one answer as accepted solution. I hope you appreciate the efforts to provide you with detailed information and mark the responses as helpful & accept solution.
Thanks,
Bhuvan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday - last edited yesterday
As mentioned in my earlier post, this is not recommended and you should not pursue it. Just because you can achieve a functionality by customization, you should not do it always and this is against ITSM best practices. Incident Management is critical process and I would recommend not to make any changes to interaction-incident relation.
You can add related interactions or create a new incident from interaction but do not create interaction from an incident.
I hope you appreciate the efforts to provide you with detailed information. If my response helped to guide you or answer your query, please mark it helpful & accept the solution.
Thanks,
Bhuvan

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Thanks Bhuvan,
I understood this is not best practice but i want to understand if i have a incident already how i can map that incident to the interaction?
I clicked on the "Add" button present in interaction related records if i click on add it is only showing interactions to add there.
So i am not able to map any incident
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
If you want to understand for learning purposes, try below in PDI setup.
Create an interaction and from the interaction, create an incident record. In my example, I created IMS0000013 and created incident INC0010081
This will create a new record in interaction_related_record table with interaction -> incident relation
Suppose I want to map an existing incident to be part of this interaction, go to interaction_related_record table and create a manual entry like below
I hope you appreciate the efforts to provide you with detailed information. If my response helped to guide you or answer your query, please mark it helpful & accept the solution.
Thanks,
Bhuvan

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hey Bhuvan,
Really appreciate your setup and you are making me understand.
But i am thinking as a process fulfiller.
thinking i am working on inteaction and incident.
when a follow up came on interaction at that time i realized that i can map this interaction to an existing incident so how i should do that?
as a fulfiller i will be least bothered about going to a different table and add it right i should have the ability of Attaching an incident to the interaction directly right?
Regards,
Debasis
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
16 hours ago
I will recommend to explain your customer what's the best practice and why you should avoid the reverse flow.
Not all requirements are meant to be implemented as they might require maintenance going forward as they deviate from standard OOTB process.
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader