Attachments are not downloading in CSM Workspace

ramireddysa
Tera Contributor

Hi Team,

 

When an attachment is associated with the RITM, it appears in the Attachments section of the associated Catalog Task in CSM Workspace. However, when I click the attachment, it opens in a new browser tab instead of downloading.

 

In the Classic UI, the same attachment downloads correctly. Is there a way to make attachments download directly from the Catalog Task in CSM Workspace, similar to the behavior in the Classic UI? Any guidance would be appreciated. Thank you!

ramireddysa_0-1784793033163.png

ramireddysa_1-1784793057656.png

 


I have tried the below steps , but it didn't work.


1.Disable the document viewer at the table level by setting the 'use_document_viewer' attribute to false in the sys_dictionary entry for the catalog task table.
2. Ensure the 'com.snc.documentviewer.enable_document_viewer' system property exists in the system, as this is required for the solution to work. I have set this property value as false.

 

@Ankur Bawiskar 

@Dr Atul G- LNG 

@Matthew_13 

@GlideFather 

@Hemanth M1 

@Tanushree Maiti 

 

 

5 REPLIES 5

Tanushree Maiti
Tera Patron

Hi @ramireddysa 

 

Its OOB feature.

 

Refer :

Check this KB: KB2997567 KB Attachments Open In A New Tab Instead Of Downloading The File 

 

Resolution

Steps to Resolve
1. Disable the document viewer at the table level by setting the 'use_document_viewer' attribute to false in the sys_dictionary entry for the knowledge table.
2. Ensure the 'com.snc.documentviewer.enable_document_viewer' system property exists in the system, as this is required for the solution to work.
3. Test the change to confirm attachments now download instead of opening in a new tab.

 

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0785245

 

 

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti

Ankur Bawiskar
Tera Patron

@ramireddysa 

that's default behavior for workspace and I think it can't be controlled.

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  10x ServiceNow MVP  ||  ServiceNow Community Leader

HarishKumar6668
Tera Guru

Hi @ramireddysa ,

It is not possible to configure the Attachment component to only download attachments on click because it is an out-of-the-box (OOB) component provided by ServiceNow. However, I can suggest the following workarounds:

1. Make the Download action visible

HarishKumar6668_3-1784812964756.png

 

You can configure the Attachment component so that the Download option is displayed as the primary action. This allows agents to download the attachment directly without having to open the attachment record first.

Steps:

  1. Open the appropriate record page variant for the CSM Workspace in UI Builder.

  2. If the variant is not editable, create a copy of the variant and either decrease its order or deactivate the OOB record page variant.

  3. Select the Attachment component from the left panel.

  4. In the component properties, set the Primary Upfront Action to Download.

Please refer to the screenshots below for reference.

HarishKumar6668_4-1784813011876.png

 

 

2. Automatically download the attachment when it is previewed

While it is not possible to prevent the attachment preview from opening (as this is the default OOB behavior), I was able to configure it so that the attachment is downloaded automatically when the user clicks the attachment and the preview is opened.

Note: This approach does not prevent the preview from opening; it simply initiates the download at the same time. If you're interested in this workaround, let me know and I'll share the implementation steps.

I hope this helps! If this resolves your issue, please consider marking this reply as Helpful & Accept as Solution.

Regards,
Harish

Hi Harish,

 

Thank you for the response. Can you share the implementation steps for the workaround. Thank you