WorkFlow Group Assignment Logic (Doc ID 2263382.1)

Last updated on MAY 15, 2017

Applies to:

Oracle Argus Safety - Version 7.0.4 and later
Information in this document applies to any platform.

Goal

Oracle Argus Safety Version 7.0.4

Require some further understanding of the WorkFlow Group logic.

At customer site,  there are two WorkFlow (WF) streams - Global WF and Japanese WF.
 
When a case is routed from Triage to DataEntry it is assigned to the DataEntry state and, based on the case data and the Advanced Condition logic, the assigned WF Group is ether DataEntry (Global) or JP DataEntry.
 
This logic works fine when the case is routed as per the defined WorkFlow rule.

But it is sometimes required to route a case to a WorkFlow state where there is no rule defined, i.e. the next Workflow state is selected manually from the list below the dotted line in the Case Routing dialog screen.
 
What is the WorkFlow Group assignment logic and the system behavior when the case is routed to a WorkFlow state where no WF rule is defined?

Note: the behavior is the same whether the case is routed Forward or Backward.
 

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