Audit Compliance Issues: Task Updatedby Reflects "Random" User Not Connected With The Task
Last updated on NOVEMBER 03, 2016
Applies to:Oracle(R) BPEL Process Manager - Version: 10.1.3.3.1 to 10.1.3.5.0 - Release: AS10gR3 to
Information in this document applies to any platform.
In some workflow scenarios, approvals are made which have financial impact. One such case is discount approvals. This issue can be related to audit compliance because the task history shows users updating a task when they in fact these users should not even have visibility of it. What seems to be happening is when "system" activities are executed, the system is using some "random" user to make the update, sometimes it uses "bpeladmin", other times it doesn't.
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