Will "Obsolete" Conditions In The Approval Task Flow Still Work Correctly On Future Releases ?
Last updated on SEPTEMBER 06, 2016
Applies to:Oracle Fusion Global Human Resources Cloud Service - Version 18.104.22.168.0 and later
Oracle Fusion Global Human Resources - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
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 <
Will these "Obsolete_..." properties still work on future Releases?
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