To easily store a set of data, image(s) or styles, Salesforce provides StaticResources. This is often nicely used to develop sweet-looking-pages, or enable external scripts to be loaded. However, one should tread this like public data.
Accessing any of these static resources, being on a Site or Community page, is of course just a matter of copy-paste. In below table you find the references. If needed, one can optionally add a timestamp (Epoch) between resource and the resource name, to enforce Salesforce to retrieve the latest version (e.g. customDomain.com/resource/1608809470000/APXTConga4__ComposerLogoRed).
|Standard Site Page||https://mydomain.force.com/sitePath||https://mydomain.force.com/sitePath/resource/[namespace__][name]|
|Standard Community Page||https://mydomain.force.com/sitePath/s/||https://mydomain.force.com/sitePath/resource/[namespace__][name]|
With this post I hope to make one aware of the potential risk of putting too much in a static resource, assuming nobody knows the name, or not making it ‘Public’. All resources are as easy to retrieve, so be aware and threat those with caution! ?
We are sorry that this post was not useful for you!
Let us improve this post!
Tell us how we can improve this post?