Flex Fields are populated incorrectly when multiple Tasktype definations have been selected (Doc ID 1905956.1)

Last updated on JULY 13, 2015

Applies to:

Oracle Business Process Management Suite - Version 11.1.1.7.0 and later
Information in this document applies to any platform.

Goal

 When multiple tasks have been selected in the tasktype definition for the custom view, then values associated to any one of the human tasks are displayed in the customer view.

For example, if we have have two human tasks hut1 and hut2 and create a custom view by selecting both the tasks for Task Type as below:

http://xmlns.oracle.com/FlexFieldApp/FlexFieldProject/HuT2,http://xmlns.oracle.com/FlexFieldApp/FlexFieldProject/Hut1

and initiate an instance for the task, only values associated with Hut1 are getting populated, leaving hut2 values blank.

If we change the Task Type value to:

http://xmlns.oracle.com/FlexFieldApp/FlexFieldProject/Hut1,http://xmlns.oracle.com/FlexFieldApp/FlexFieldProject/HuT2

then values associated with HuT2 are getting populated leaving values of hut1 blank.



Solution

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