Overview:
A shared resource is often used to optimize storage space and reduce sync times. This allows HTML assets to be shared across multiple Key Messages.
Root Cause:
In some cases, the HTML file is incorrect. When a shared resource is being used, the .zip file is unpacked into a folder named: shared.
Solution:
There are a few items to look at to determine why the Shared Resource is not functioning as expected.
- Ensure that Is_Shared_Resource_vod__c is checked on the shared key message.
- Ensure Shared_Resource_vod__cis populated on the key messages that are using files from the shared key message.
- Ensure the end-user has Field Level Security (FLS) to the fields above.
The .zip file on the Shared Key Message is unpacked into a folder called shared. It is common to have the incorrect path listed in the HTML files. Below are examples of how to call a file in a shared resource into the key message. The examples below assume that the root directory of the .zip file contains three folders: one called: scripts, one called: styles, and one called: images.
- scripts (Header of HTML) - <script type="text/javascript" src="shared/scripts/veeva-library-3.0.js"></script>
- styles (Header of HTML) - <link rel='stylesheet' href='shared/styles/style.css'/>
- images (Body of HTML) - <img src="shared/images/download.png" />
If the .zip file has one folder in the root directory, that contains other folders, the path is:
- scripts (Header of HTML) - <script type="text/javascript" src="shared/YOUR FOLDER NAME/scripts/veeva-library-3.0.js"></script>
- styles (Header of HTML) - <link rel='stylesheet' href='shared/YOUR FOLDER NAME/styles/style.css'/>
- images (Body of HTML) - <img src="shared/YOUR FOLDER NAME/images/download.png" />
Related Documentation:
N/A
Send us your feedback: We're always looking for advice to help improve our Knowledge Base! Please let us know if this article was helpful or provide feedback on how we can improve your experience here.
Thank you