Details
-
Type:
Bug Fix
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 0.9, KEW (2.4.1) - 0.9, KFS Release 2.0 - 0.9.0.2, KFS Release 2.0
-
Component/s: Development
-
Labels:None
-
Similar issues:
KULRICE-2618Prevent policy violations from blowing up routing simulations KULRICE-2637Implement "true" routing simulation in the SimulationEngine KULRICE-1877Simulation Engine has a bug when using Node Name or Rule Template Name criteria and doing report by Route Header Id KULRICE-10934Cannot route documents and workflow simulation is broken KULRICE-2636Exclude splits and joins from flattened node evaluation in the simulation engine KULRICE-6848 RouteLog: future action requests show invalid nodes when document is disapproved KULRICE-2546simulation engine does not work KULRICE-5080 Implement Loops within the Engine KULRICE-3328Change Workflow Engine to update database fields on 'save' action KULRICE-2729The "Future Action Requests" tab on the Route Log does not work properly with a client application using "embedded" mode -
Rice Module:KEW
Description
The Workflow Simulation engine... which is currently used by the WorkflowInfo.documentWillHaveAtLeastOneActionRequest() method... needs to gracefully handle the potential exception thrown by Mandatory Route Nodes when they don't generate a proper request. This method is used extensively by the PURAP documents and it is not currently a blocker issue but if a certain implementation alters the routing of the documents it very well could become one.
Issue Links
- is related to
-
KFSOLD-7515
content routing did not work - doc ID 305855 req # 1003
-
This about as fixed as we can get in that it's throwing a customized DocumentSimulatedRouteException that should indicate that the document would go to Exception. This at least allows KFS to find this exception as the cause to decide how to handle the scenario. This is all PURAP really needs which is why i created this issue.