Hi Team,
In our project, we see that the sys_attachment table is growing rapidly because attachments are being copied from the RITM record to the related SCTASK.
We now have a requirement where:
Attachments should not be copied from RITM to SCTASK.
Attachments should still be visible in SCTASK across all views (Classic, Native, and Service Operations Workspace).
Attachments should be downloadable from SCTASK in every view.
I created a relationship so that attachments from the RITM are visible in SCTASK. With this setup:
In the Classic UI, I am able to view and download the attachments.
In SOW (Service Operations Workspace), I am able to view the attachments, but when I click on them, they open in a new tab instead of directly downloading.
Has anyone implemented this scenario where RITM attachments are referenced (not copied) in SCTASK, and download works seamlessly in SOW as well?
Any suggestions or best practices would be greatly appreciated.
Thanks,
ND
