
- 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
23 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
20 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
23 hours ago
understood @Ankur Bawiskar ,
but i as a fulfiller i should have the ability to attach one existing incident to the interaction right?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
23 hours ago
but why?
If Interaction is the starting point and then INC is created from it.
Why would someone attach Interaction later for already existing INC?
If you still want to achieve, steps below
1) ensure "Omit if Empty" is unchecked on that list control
2) ask that user to click New button in that related list (see if that fulfiller has Create access to that table, you might have to tweak the ACL)
3) then on this form populate the relevant fields (you will have to check if fulfiller has edit access, play with the WRITE ACL)
a) Interaction
b) Document table
c) ID of related record
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
22 hours ago
As mentioned, this is not best practices and you should not do it. You can explain to Incident Process Owner why it is not recommended and they should not ask for such requirements in the first place if they follow best practices.
Only for theoretical understanding, if you add table 'interaction_related_record' using custom related list you will get this mapping directly
For workspace, below are the steps
If this helped to 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
20 hours ago
So in that case the best practice is interaction to incident is one to one relation not many to many
as a fulfiller one interaction can create one incident.
Correct me if my understanding is wrong.
Thank you so much for your answers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
20 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