Why Folders Might Not Move From a System Stage

Metastorm

The information in this article applies to product: e-Work 5.x 6.x

Issue

• What can cause a folder to get stuck at a system stage?

Resolution

• A folder could get stuck if there are conditional or timed actions leaving the system stage and if either of the following is true:

  1. The "Only start action if" condition for every conditional action or timed action resolves to false.
  2. The code fails in the "When action completed" property of the action.

  These two qualifications reflect improper procedure design. When conditional actions are used with system stages, it is recommended that there is one action that can always move the folder on if all of the others fail.

  A timed loop-back action can also be added to force the folder to re-evaluate the conditions after taking the timed action. Care needs to be exercised with this though as you can create an endless loop if the conditional actions always fail.

Rick Kushner

I can't get a timed loop back action to work in v7.6. The timed action only executes once, and then it never resets.

Jerome_Pearce

As far as I know, timed loopback actions will fire the first time every time. After that, ie on loopback actions, it appears that the action will only fire if the time is in the future when the last loopback occurs.

 

1. I assume this is to prevent the timed action repeating forever

2. I cannot guarantee this is what occurs, but experience tells it does

3. This may not be true of all version of Metastorm BPM / e-work.