on 02-28-2018 5:53 AM
Hi,
improving already existing complex WF developed by someone is tough 🙂
well question is, there is a STAND ALONE 'std-task' which has 2 triggering events, no terminating events.
if any of the event starts, this eventually starts main WF.
during the course of this process both these events can trigger at any point of time.
So say it triggered both event ONCE, but when I see in SWI6 I see this 'std-task' triggers more than twice.
Is it a good idea to have a separate 'std-task' and have 1 event in each 'std-task' or is there another way like may be terminating event or something else.
Thanks,
Aditya V
Not sure I fully understand the question, but there is nothing wrong with having multiple start events.
"So say it triggered both event ONCE, but when I see in SWI6 I see this 'std-task' triggers more than twice."
I'd say the first assumption is wrong, or it was started by other mechanisms. The technical log should tell you how each instance was started.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mike,
we manually start these 2 events, so there is no way it started from any other mechanism.
since we know we have manually started it, say I triggered event-1 and then later event-2, ideally in SWI6 I should have seen this 'task' triggering twice, but I see it triggering more than once.
Aditya V
So as per the other part of my comment, what do the logs say how each task was started?
Hi,
I can only say, introducing of terminating event is great design.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
9 | |
8 | |
6 | |
6 | |
6 | |
5 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.