Inbound mails are not added to activity

[tomopl]

Hi there,

I have an inbound action against "sys_data_source" table. This action triggers the Scheduled Imports (hence it is against that certain table) when the mail has an attachment or creates a new task in our table (it extends the default "Task" table) when there is no file attached. The problem is, I don't know how to add the whole mail to the activity field (I've seen this working in other applications). It probably doesn't add the mail to that field because the first created record in the script is against the "sys_data_source" table, but I'm not sure about that. I have "Sent/Received Emails" filter selected when I right click the field, also there was an option in SN to show emails only to certain groups, that didn't work either. I know I can add an extra field to our table and just copy the mail body to it, but we want to use the default activity functionality.

Instance details:

Build name: HEAD (Fuji)

Build date: 10-29-2015_1529

Build tag: glide-fuji-12-23-2014__patch10-10-21-2015

[Gurpreet07 · Accepted solution]

Not actually ,I   misunderstood that you are having two issues... one for attachments and other is emails in activity log.

I remember when our client requested to show SLA emails on related Incident itself. The only way possible is to create a duplicate record of that email (sys_email record) and change the target table and target field values in new record.

[tomopl]

That reply helped me a lot! After manually changing those 2 fields in the sys_email record of the inbound action mail, the mail was properly showing in my activity field. So what I did was just updating the correct sys_email record from one of the business rules and it's working like it should.

So in summary if anybody would encounter the same problem. If you are trying to attach an email to the activity log field in some ticket AND your inbound action is not against that table, you have to update 2 fields in sys_email record (inbound action has access to global sys_email object where you can get it's sys_id like sys_email.sys_id) called Target (instance) with sys_id of your record and Target Table (target_table) with name of your ticket table.

Thanks again!