How To Use Siebel OpenUI Content Expiration Feature for Custom Files?
(Doc ID 2487063.1)
Last updated on JULY 08, 2019
Applies to:Siebel CRM - Version 18.8 and later
Information in this document applies to any platform.
For OOTB Content files, it appears the file(s) are versioned based on Siebel Patchset version. Client browser will automatically fetch new Siebel OOTB content files related to the appropriate patchset.
How is the above stated versioning/expiration features are to be configured and used for custom files?
Ifcustom CSS/files are deployed as part of the Siebel patchset rollout then it appears to work. But after the Siebel patch set is deployed to PROD and there are subsequent updates made to custom CSS and/or JS files alone then how are those being pulled down automatically as part of Content versioning?
In this scenario since there are no changes in Manifest definition but the referenced files are changed and deployed to AI. How is content versioning being handled in this case?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document