Problem Note 64745: You can incorrectly have multiple active nodes in the same SAS® Risk and Finance Workbench process thread
 |  |  |  |  |
In SAS Risk and Finance Workbench, you are able to start a new iteration on a task that is downstream of the currently active tasks. When you take this invalid action, the active tasks remain active in the new iteration. This issue results in having multiple active nodes in the same process thread.
For example, you encounter this issue if you perform the following steps:
Note: In the scenario below, assume that the process definition contains six tasks: Task 1 - Task 6.
- Complete Task 1, Task 2, Task 3, Task 4, and Task 5. All tasks show a Completed status. Task 6 shows an In Progress status.
- Start a new iteration from Task 5 back to Task 1. After you take this action, you see the following status changes:
- Task 6 shows a Reset status.
- Task 1 shows an In Progress status.
- Task 2, Task 3, Task 4, and Task 5 show a status of Completed.
- Complete Task 1 and Task 2.
- On Task 3, which now has an In Progress status, start a new iteration, and navigate to subsequent Task 5. After you take this action, you see the following status changes:
- Task 3 shows an In Progress status.
- Task 4 still shows a Completed status.
- Task 5 shows an In Progress status.
- Task 6 still shows a Reset status from the first iteration.
In this example, you could keep starting new iterations and every task would have an In Progress status. This is not expected behavior.
Click the Hot Fix tab in this note to access the hot fix for this issue.
This hot fix introduces two new SAS Risk and Finance Workbench application properties that you can set in SAS® Management Console. These application settings are independent. You can elect to enable only one of them, both of them, or neither of them.
rfw.consider.traversed.paths.only: (optional) If you do not set this option, it defaults to FALSE. If you set it to TRUE, then only nodes that have been visited (that is, nodes with status other than Not_Started) are traversed when determining which nodes need to be reset. For example, if an active node is reachable via multiple paths, but no paths to it from the target node for the new iteration have been traversed, it is left in an Active state.
rfw.iteration.resets.completed.nodes: (optional) If you do not set this option, it defaults to FALSE. If you set it to TRUE, then the status of all active and completed process task nodes downstream of the target node for the new iteration are returned as needing to be reset.
Note: If all process task nodes have been completed, starting a new iteration on any node (except the end node) is permitted.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Risk and Finance Workbench | Microsoft® Windows® for x64 | 3.1 | 9.4 TS1M5 | ||
| Linux for x64 | 3.1 | 9.4 TS1M5 | ||||
A fix for this issue for SAS Risk and Finance Workbench 3.2 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/D4L.html#64745A fix for this issue for SAS Risk and Finance Workbench 3.1 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/C5N.html#64745| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2019-10-04 11:40:22 |
| Date Created: | 2019-09-09 06:26:33 |