Joining two instance of a task

[marcosdutto]

I have this diagram

I want to create 2 (or more) instance of "Task1" and join they with only one instance of "Task2".

Any help?

--------------

Another example of my problem is this diagram.

"condition" in diverge gateway is evaluate at runtime, sometimes true and sometimes false.

My problem here is that i want to join two, or more, instance of Task1 with one instance of Task2.

[salaboy21]

Hi,

can I ask based on what business condition you decide to create more than 1 instance of Task 1?

Cheers

[marcosdutto]

The business condition is an external condition, it has not relation with variables of the process.

[salaboy21]

Can you describe that business condition? because probably you can model it in a different way.

Cheers

[marcosdutto]

I have something like this:

    -> Three tasks (Task1, Task2, Task3)

    -> I do not know how many task of each i will have at runtime.

    -> I want to be able to match one Task1 with one or more than one Task2.

    -> I want to be able to match one Task2 with one or more than one Task3.

    -> I want to be able to match more than one Task1 with one Task2.

    -> I want to be able to match more than one Task2 with one Task3.

    So, finally what i want to do is a mapping between Tasks but without knowing how many i have for each task.

Example:

    Task1 = Purchase Request

    Task2 = Purchase Order

    Task3 = Bill

    A purchase request can be order in parts, so i will have more than one purchase order for one Purchase Request.

    But, at the same time, 2 (or 3,4,5...) Purchases Request can be wrapper in only one Purchase order.

    The same thing happend with Purchase Order and Bill.

Thank you "Chabon".

[marcosdutto]

Do you understand the idea?

It can be done it with JBPM?

Thanks in advance

[salaboy21]

I think that now I understand a little bit more about your requirement.

So what are you trying to model is a process to gather Purchase Requests or Purchase Orders?

It doesn't sounds like just one process, it sounds as a bunch of processes and instances gatehering information about a big operation to me.

If you create a business process, you need to clearly identify the goal of that process and build your tasks around that goal.

For example if the process is called: New Purchase Order Process

The process will contain all the tasks required to create a new Purchase Orders, these tasks can be enter in all the purchase requests associated to that order.

The other thing that you need to know is that a same task can be used to store different snapshots of the work, for example if you say that

One Purchase request have multiple parts, you can just have one task which allows you to enter each of these parts in different times. When you have entered all

the required or necessary parts you can complete the task and move the process forward.

Hope it helps..