Why Does the Label Name For Flex Fields In 11g Have to be Unique?
(Doc ID 1223843.1)
Last updated on OCTOBER 10, 2019
Applies to:Oracle(R) BPEL Process Manager 10g - Version 10.1.2.0.0 and later
Information in this document applies to any platform.
In SOA 11g Human Workflow when using flex fields we have found a limitation vs. what was present in 10g.
In 10g we were able to map the same label to different attributes and use it in different task types. Eg. say a "customerId" label that is mapped to TextAttribute1 and then used in PurchaseOrderTaskType; the same "customerId" label is then mapped to TextAttribute2 and then used in CustomerDetailsTaskType (could even be a different project deployed on the server).
When trying to create the same in 11g R1 PS2 (see section 30.10 Using Flex Fields Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite 11g Release 1 (11.1.1) Part Number E10224-05), we get an error that the label name is already used. Does this mean that we cannot use same label name again like in 10g?
Maybe to prove the above we could see that in WFATTRIBUTELABELMAP table in 10g there is a unique index WFATTRIBUTEMAP_UK over TASKATTRIBUTE and LABELNAME, while in 11g the same unique index is just over LABELNAME column.
Could you please clarify if indeed in 11g this limitation was introduced, let's say by intention, and what is the reason behind? It seems to be a move backwards from 10g at this time.
Is it possible in order to allow multiple label names mapped to different task attributes to change back the unique index mentioned above to same behavior as in 10g? What is the impact?
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