Will "Obsolete" Conditions In The Approval Task Flow Still Work Correctly On Future Releases ? (Doc ID 1964003.1)

Last updated on SEPTEMBER 06, 2016

Applies to:

Oracle Fusion Global Human Resources Cloud Service - Version 11.1.8.0.0 and later
Oracle Fusion Global Human Resources - Version 11.1.8.0.0 and later
Information in this document applies to any platform.

Goal

In BPM Approval task configuration, some of the conditions use comparison parameters that have "obsolete" attached to them. For example:

Task.payload.Worker's Proposed Assignment.result.obsolete_legalEntityId is <<legal_entity_id>

Will these "Obsolete_..." properties still work on future Releases?
 

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