How to Handle Disconnect Between Site Studio And WCC?
(Doc ID 1914825.1)
Last updated on OCTOBER 16, 2019
Applies to:Oracle WebCenter Content - Version 7.5.1 and later
Information in this document applies to any platform.
There is a disconnect between Site Studio and Content Server as explained in the below Use Cases. Is there a way to resolve this?
EXPIRATION AND DELETION
The content is expired or deleted successfully by the CMS and replicated appropriately to our production site. However, the expiration and deletion of content does _not_ seem to either nullify or remove the references to those content items in the project file. Pages where these content items were assigned (most are XML contribution regions) continue to be referenced. When a user navigates to these pages in Production, the errors are thrown in the CMS as it’s unable to find those content IDs.
There are references in Production to content that is still in workflow and has yet to be promoted from Contribution to Production. The most likely scenario is that not all content within the contribution regions of a template are approved to go live when the page itself is approved to go live. When the page is promoted, it contains references to content that only resides in the Contribution environment as it has yet to be promoted to Production. This is a valid use case that _should_ be supported in WCM as not all components of a page are necessarily ready at the same time.
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