Last updated on MARCH 08, 2017
Applies to:Oracle Demantra Real-Time Sales and Operations Planning - Version 22.214.171.124 and later
Information in this document applies to any platform.
The workflow step has a recovery option "Abort".
Expected system behavior is that, in the situation of workflow failure at any step, the engine should terminate the workflow instance.
But this is not happening, instead it is sending a task to the admin user.
The workflow failure is tested by creating a dummy workflow with a "Stored Procedure Step" in it. This points to a procedure name that doesn't exists in the database in order to make that workflow fail. Selected the recovery option for the step as "Abort".
Checked wf_process_log and the status is 1 (active). Expected status should be -2 (failed).
In the Collaborator Workbench, My Tasks section, the workflow is waiting for user acknowledgment
If the workflow fails due to a missing procedure, the expectation is for the workflow to abort and not wait for user to acknowledge that there is a failed step.
How can you force the workflow to abort in such cases?
In addition when the workflow step is set to Continue, the workflow does not continue but is stuck in the Failure in Process Execution status.
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