
- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on ‎08-18-2018 05:31 PM
For those who have worked with Incident earlier, it's not uncommon to have seen attachments/images directly in Activities when this is added to the form.
In CSM, this is not the case when activating the plugin.
And it is therefore necessary to add an attribute in the associated System Property if the behavior is desired.
In order to achieve this, locate the System Property : glide.ui.sn_customerservice_case_activity.fields, and add "*Attachments*", to the end of the string.
This will add the Attachment field to the Activities filter as shown in the image below.
Attachments will now be visible as a preview in the Activities list.
- 1,892 Views
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Where is *Attachment* defined ?

- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hello,
I suspect without being one hundred percent sure here that this is blackboxed and something we do not see.
The steps above shows how you can include attachments in the activities list.
Product Documentation that mentions this property is located here.
Is there anything special you are looking for given that you are looking for this definition?
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Is there Any way to show deleted attachment to "Atachment Upload" filter activity without creating another Journal Input ?

- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hello,
Unfortunately I do not think you get to that possibility in the same way, as it shows uploaded.
I have seen implementations where you write to work notes when an attachment is deleted. That includes, who removed an attachment and the name of it.
That could be solved with a Flow or a Business Rule on the sys_attachment table on delete, which adds a work note on the relevant record.
But then you should have a good condition etc as it is an essential table.
And of course test performance in relation to this customisation.