Unable To Open Webviewable File When Using Custom Metadata Field in File Store Provider Weblayout Path
(Doc ID 1350507.1)
Last updated on FEBRUARY 02, 2022
Applies to:Oracle WebCenter Content - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
In WebCenter Content (WCC) (formerly Universal Content Management or UCM), using a FileStoreProvider (FSP) storage rule that adds a custom metadata field to the vault and weblayout paths works fine for the vault directory, but fails for the weblayout directory. The indexer fails to rename the weblayout file, which means that the file name in the weblayout directory contains a ~1 after checkin. This causes the webviewable URLs not to work.
To reproduce the issue:
- Create a custom metadata field; for this example, the field created is named StorageTier. Make it a text field with an option list with a single value; for this example, the value in the option list is named tier1.
- Create a new FSP storage rule using this custom metadata field in the paths as follows:
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
Symptoms Cause Solution References
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.