| Author |
Message
|
| vinodsasidharan |
 Posted: Mon Apr 28, 2003 9:12 pm Post subject: HOW CAN I ACHIEVE THIS .THE DESIGN INCASE OF PARALLEL FLOWS |
 |
|
Apprentice
Joined: 25 Apr 2003
Posts: 47
Location: Norwich
|
Hi guys,
I have a requirement
I have 2 departments A and B . and my requirment is that as soon as the process starts both the activities at A and B are parallely started .
so I have two activities A and B after my source which starts simultaneously .
after this flow goes to activity c from either a or from b .
so which ever department accepts the case first or confirms to proceed flow reaches c from this activity .
But i am not able to achieve this via this design . because even if say A takes a decision of "Accept" . activity C never starts .
Does workflow does not support this .
If u did not get what i asked , a bit more explanation
A B
- -
- -
decision ="ok" - - decision = "accept"
- -
- -
- -
C
SO A and B started parallelly. Whichever a or b makes a proper decision
flow needs to reach C.But this is not happening . even if a takes decision "ok" and flow reaches c . but c never starts as it is still waiting for b to take decision ????????so is such a flow not possible in workflow ??
_________________
Vinod sasidharan
Ibm Certfied MQ Admin 5.3
Ibm Certfied MQ Admin 6.0
Ibm Certfied WAS Admin 6.0
Ibm Certfied WMB Admin 5.0
Ibm Certfied Db2 Specialist.
Sun certified Java Programmer.
"Ai carte, ai parte ....................." |
|
| Back to top |
|
 |
| Sanju |
| Posted: Mon Apr 28, 2003 11:22 pm Post subject: |
|
|
Newbie
Joined: 21 Apr 2003
Posts: 2
Location: Bangalore
|
I think its not possible as both of the activity comes in ready state as soon as process starts.
Once A or B is started, some action has to be taken on other activity so that it exits and C can come in ready state.
To achive the flow, both activity A and B implemantatoin program code should use APIs which will finish other activity and satisfies its exit condition(Or Force Finish other) so that flow can move to C.
Or someone can tell any design trick or better way to do this?
Sanju |
|
| Back to top |
|
|
| amittalekar |
| Posted: Tue Apr 29, 2003 5:24 am Post subject: |
|
|
Disciple
Joined: 03 Apr 2002
Posts: 166
Location: VA, USA
|
vinodsasidharan,
why do u need 3 activities for this. Same thing can be achieved in only 2 activities i.e A & C. Add a user in buildtime (say supervisor). Assign the activity A to this user. So whenever task is created it will be always for that user. Give proper authorization to the users in two departments ...
By doing so u ensure that at a time only one user from any department is working on case....and one he checks in next actvity i.e. C will start.
If u want to use parallel processing then u have to keep track that dept A user is working on case and then user from dept 2 should not check out the task. Also as sanju said u have to forcefinish the other dept task then only C will proceed. In WF parallel processing is designed to work that way only. |
|
| Back to top |
|
|
| Ratan |
| Posted: Tue Apr 29, 2003 9:27 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
vinodsasidharan,
At a join workflow will continue execution only after all the control connectors have been evaluated (either True or False and you have to check "At Least one incoming connector true for activity start" in activity properties).
So what you are experiencing is how workflow is designed.
I agree with Amit if your Activity A and Activity B do the exact same thing but assigned to different people.
-Ratan. |
|
| Back to top |
|
|
| vinodsasidharan |
| Posted: Tue Apr 29, 2003 10:13 am Post subject: re: |
|
|
Apprentice
Joined: 25 Apr 2003
Posts: 47
Location: Norwich
|
Hi friends,
This is what we suggested to our clients .But they wanted it as a sepearate activities since these A and B are done basically in 2 different departments With lots of logic difference.So A is a huge Vb application with lots of logic involved and screens which needs to be updated related to department A and did by a different role of people .Similarly B has its own huge logic .So a accept decision from either A or B MAKES FLOW TO C. So combining them as one was not agreeable by our clients .That why i made it as seperate activities .But was not able to achieve such a flow .So as u told i cant combine a and b.
As u mean should i need to force finish activity A as soon as activity B is ENDING ????
_________________
Vinod sasidharan
Ibm Certfied MQ Admin 5.3
Ibm Certfied MQ Admin 6.0
Ibm Certfied WAS Admin 6.0
Ibm Certfied WMB Admin 5.0
Ibm Certfied Db2 Specialist.
Sun certified Java Programmer.
"Ai carte, ai parte ....................." |
|
| Back to top |
|
|
| amittalekar |
| Posted: Tue Apr 29, 2003 10:22 am Post subject: |
|
|
Disciple
Joined: 03 Apr 2002
Posts: 166
Location: VA, USA
|
DeptA and Dept2 may have different logic but for both in Workflow wht u gonna do is checkOut and retern WorkItem. So whats the problem. I assume here that for activity A and B datastructure will be same
There is one more easy approch. U can consider this an an alternative
put C activity in parallel path... that means from A, next act will go to C1 and from B next activity will be C2. C1 and C2 will do the same thing...
Good Luck |
|
| Back to top |
|
|
|
|
