Process Mapping Logo

Process Mapping - Forums

Sharing 19 years of knowledge and experience

 
Metastorm BPM forums
Sign up Latest Topics
 
 
 


Reply
  Author   Comment   Page 2 of 2      Prev   1   2
Jerome

Avatar / Picture

Guru
Registered:
Posts: 5,507
Reply with quote  #16 
Q1: If this were true, why does the flag NOT get raised if I perform an action on another folder?

Q2: What happens when an external event raises a flag? Is the Engine supposed to wait until an action occurs? Obviously not, that would be unacceptable.

The event manager gets kicked off when any event it should respond to occurs, or the next timer is reached.

__________________
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
jsuijker

Senior Member
Registered:
Posts: 93
Reply with quote  #17 
I just added you reaction as my own in an extra reply on the support call.
Let's see what they will reply.

I agree that this is a Bug. Just want to be polite... :)
0
Jerome

Avatar / Picture

Guru
Registered:
Posts: 5,507
Reply with quote  #18 
I understand.

I gave up polite after being told for the 1001st time that functionality that was obviously wrong was 'working as designed' when it clearly was not. It is often a case of people just not understanding how the product is supposed to work.

__________________
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
Jerome

Avatar / Picture

Guru
Registered:
Posts: 5,507
Reply with quote  #19 
Attached example in v7 shows it works perfectly well before, as I suspected it would.

 
Attached Files
xep Test_Raise_Flag_from_Form.xep (1.95 KB, 4 views)


__________________
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
jsuijker

Senior Member
Registered:
Posts: 93
Reply with quote  #20 
I must believe you on your word. I don't have a V7 installation to test this on.
I did recieve a reply from metastorm.

Quote:

I have received your updates to this ticket.
I apologise I haven't been in touch.
I will investigate the matter further and see if there is a workaround for this.
I will also take on board the comments you made regarding the immediate raising of flags.


0
jsuijker

Senior Member
Registered:
Posts: 93
Reply with quote  #21 
Just send an email to aks if there is more information. I do like the polite response(s) support guys need to give... :) To bad it isn't resolving the problem.

Quote:

I am looking at the issue at the moment. I am trying to produce a workaround for you.
Thanks for your continual patience.
 

0
jsuijker

Senior Member
Registered:
Posts: 93
Reply with quote  #22 

I had some replies from Metastorm:

Quote:

There does seem to be a difference in behaviour from version 7 and therefore will be escalating this ticket for further analysis.
As version 9 is a new product, this change may be diliberate or it may be a defect in the system, this needs clarification.
As a workaround, would you be able to change the polling on the engine to check the eWait/eRaisedFlag tables?
This does has side effect in that, it can cause extra load on the system as the engine checks and processes the database at set intervals, rather than being prompted to do so.
The registry key you will need to change is HKEY_LOCAL_MACHINE\SOFTWARE\Metastorm\e-work\Engine\Event manager\Poll Interval (secs).
I tested this to 1 second and saw the required behaviour. 

Is this THE solution or just a work around?

Quote:

The registry key I mentioned is a workaround.
The engine reads this on startup and checks tells the eventManager component to check the eWait/eRaisedFlag table on the programmed time.
The downside to this workaround, is that the sysyem performance can be slow, if the engine continuely check the databse.
So if there are many flag to process, the engine will keep on doing this.

So until Metastorm has find a definitive solution changing the key works, but i haven't tested it on a full loaded system to see what it does with performance


 

0
BMellert

Guru
Registered:
Posts: 688
Reply with quote  #23 
Wow and interesting.

I know we have this setting set to 5 minutes (600 seconds) in our production environment to make sure things don't whither during the relatively idle overnight hours, but that is just to make sure timed actions get fired, not raising flags.  Flags has always forced a check -- but it may be a v7 vs v9 "feature".
0
Jerome

Avatar / Picture

Guru
Registered:
Posts: 5,507
Reply with quote  #24 
I can only think it is down to a multi-engine thing and a bug. If you have one engine, the event manager should just look for the next action and do it every time an action is submitted.

I guess if you are able to delegate event manager jobs to a particular engine, it needs to poll the eWait and eRaisedFlag (or maybe just the latter) table regularly to ensure it picks up the next one placed there by another engine.

I see no engine name in the eRaisedFlag table for these flags, and that could be the problem.

__________________
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
jsuijker

Senior Member
Registered:
Posts: 93
Reply with quote  #25 
I got an update on met support call:
Quote:

I am updating you with the status of DEF15868.
This defect has been scheduled to be fixed in Hotfix 2 for 9.0 SR3.
Again, I would like to make you aware that this defect is still under review and will be fixed upon business value and the time needed to provide a fix.
 

0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:


Create your own forum with Website Toolbox!