Process Mapping Logo

Process Mapping - Forums

Sharing 19 years of knowledge and experience

 
Metastorm BPM forums
Sign up Latest Topics
 
 
 


Reply
  Author   Comment  
wbehning

New Member
Registered:
Posts: 7
Reply with quote  #1 

I've been beating my head against the wall with this one.  I'm hoping someone can shed some light.

Scenario 1
Attach a Flag Action off of a User Stage.
The other end of the Flag Action is an Archive Stage.
Make sure the folder is in the User Stage.
Raise the flag from a different process.
The Flag Action executes as expected.


Scenario 2
Attach the same Flag Action off of a System Stage.
The other end of the Flag Action is an Archive Stage.
Make sure the folder is in the System Stage.
Raise the flag from a different process.
The Flag Action does not execute, nothing recorded in eevent or elog

Scenario 3
Exactly the same as Scenario 2 with:
Attach a loop back User Action to the System Stage.
This User Action raises the same Flag as scenario 1 and 2.
The Flag Action executes as expected.

The Flag Action contains no code, all it does is move the folder to an Archive Stage. 
The Archive Stage contains no code as well.
We are running versions 7 and 9 in a side by side configuration.  This process is entirely version 9.

Anyone have an idea as to why Scenario 2 fails while Scenarios 1 and 3 execute?

Is there a way to get more logging in eLog?

What is purpose of the "System Stage"?

0
Jerome

Avatar / Picture

Guru
Registered:
Posts: 5,507
Reply with quote  #2 
Note that flag actions only work for folders newly arrived at the stage (or after the folder is updated). Anything sitting at that stage will NOT be affected by any flag actions added, or even modified (although this is not quite true, it is difficult to determine) after they reach that stage. The details are in the eWait table, and are viewable in the Status for in our Library.

You can add logging yourself in the eLog table using the VS activities. Our Debug library also has a 'Trace' function that writes to the log. You can turn of all tracing in a production environment by deploying the 'Release' version, so allowing trace to be left in code with no performance impact.

The System stage is the same as the User stage (although action properties are slightly restricted), but with no To Do list. They also have a few minor additional properties that can be useful.

__________________
Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.
0
wbehning

New Member
Registered:
Posts: 7
Reply with quote  #3 
Thanks...  It all makes sense now.  Since these folders arrived at the System Stage before the Flag Action was in place, there was no record in ewait.  Once I moved the folder back into that stage, I now see the ewait record and the flag responds as expected. 
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:


Create your own forum with Website Toolbox!