Document with XRegionDefinition="idcnull" vs. "IDCNULL" Sends Different Response Back to WebCenter Portal
Last updated on DECEMBER 15, 2017
Applies to:Oracle WebCenter Content - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
In WebCenter Content (WCC) instance with Site Studio that is integrated with WebCenter Portal (WCP):
Documents with XRegionDefinition value = "idcnull" have difference in processing with documents with xRegionDefinition value = "IDCNULL".
If a document is retrieved from WCC which has xRegionDefintion value = "idcnull" in the IDCTEXT1 and/or IDCTEXT2 database table, WCC returns the document node content with xRegionDefinition as "" to the client WCP.
The same behavior is seen if xRegionDefinition value is null in the IDCTEXT1 and/or IDCTEXT2 database table. WCC returns returns the document node content with xRegionDefinition as "" to the client WCP.
However, once DatabasePreserveCase=1 is added to WCC, and the server is restarted along with the index rebuilt, all existing and new documents get updated with xRegionDefinition = "IDCNULL" in the IDCTEXT1 database table and/or the IDCTEXT2 database table.
The problem with xRegionDefinition = "IDCNULL" is that WCC processes it differently from the case where it is "idcnull" or null.
In the case of "IDCNULL", WCC returns the document to WCP with xRegionDefinition value as "IDCNULL" instead of the empty string.
If WCP finds any value in the xRegionDefinition attribute, it considers it to be Site Studio content even if it is not.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms