FieldCopier Shows Inconsistent Behavior For Unpopulated Attribute Depending on The Method to Create Asset, WebUI or REST API
(Doc ID 2045803.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle WebCenter Sites - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
A FieldCopier filter is used to copy an attribute to another field defined. However, the filter shows different behavior when handling an attribute which is not populated, depending on the method to create the asset (via Contributor UI or REST API) as follows:
- When creating an asset without populating the source attribute via Contributor UI, the field is not copied.
- When creating an asset without populating startdate attribute via REST API, the field is copied.
Why does such a difference occur? According to <Document 1552570.1>, Contributor UI's case (A) seems to be correct.
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