Protected Date Attribute Persistence Issue (Doc ID 1607063.1)

Last updated on DECEMBER 13, 2013

Applies to:

Oracle Business Process Management Suite - Version 11.1.1.6.0 to 11.1.1.6.0 [Release 11gR1]
Information in this document applies to any platform.

Symptoms

 
A process has 4 project data objects of type Time for example. These project variables are mapped to protectedDateAttribute1, protectedDateAttribute2.. etc in WFATTRIBUTELABELMAP.
 
In this test:

 ex_date     is mapped to protectedDateAttribute4
 record_date is mapped to protectedDateAttribute2
 pay_date    is mapped to protectedDateAttribute3
 report_date is mapped to protectedDateAttribute1
 

When the workflow is initially created, all attributes have the correct values.


 SELECT * FROM WFTASK order by createdDate desc;
 
 PROTECTEDDATEATTRIBUTE1: 01-JAN-01
 PROTECTEDDATEATTRIBUTE2: 02-FEB-02
 PROTECTEDDATEATTRIBUTE3: 03-MAR-03
 PROTECTEDDATEATTRIBUTE4: 04-APR-04
 
 

When it enters human task, the value of PROTECTEDDATEATTRIBUTE4 is replaced with PROTECTEDDATEATTRIBUTE1. No data obejects are being used in this human task.


  PROTECTEDDATEATTRIBUTE1: 04-APR-04
  PROTECTEDDATEATTRIBUTE2: 02-FEB-02
  PROTECTEDDATEATTRIBUTE3: 03-MAR-03
  PROTECTEDDATEATTRIBUTE4: 04-APR-04

Cause

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