TOPIC: Sequenced actions with delegated - inconsistency?

Hello,
using TR 2.2.1 on Linux
i didn't manage to figure out how to sequence inactive and delegated actions accordingly.

Example:

Project (sequencing and delegated enabled)
+ Active0
+ Delegated1
+ Inactive1
+ Delegated2
+ Inactive2

I would assume that "Inactive1" will be set to DoASAP automatically after "Delegated1" is set to done.

But I have to mark "Delegated1" and "Delegated2" as done to have "Inactive1" become automatically a DoASAP action.

Is that intended behaviour?


--
Product Version = ThinkingRock 2.2.1
Operating System = Linux version 2.6.30-2-amd64 running on amd64
Java; VM; Vendor = 1.6.0_16; Java HotSpot(TM) 64-Bit Server VM 14.2-b01; Sun Microsystems Inc.
Runtime = Java(TM) SE Runtime Environment 1.6.0_16-b01
Java Home = /usr/lib/jvm/java-6-sun-1.6.0.16/jre
System Locale; Encoding = de_DE (tr); UTF-8

Yes. As you have included Delegated actions in your sequencing, TR "sees" them as active actions and thus does not activate the Inactive 1 action in the middle.

If you exclude the Delegated Actions, Inactive1 will become Do ASAP when Active0 is set to Done.

Hello,

thanks for answering my question.
Nevertheless i didn't catch the point...

Let Project be "buy a new car":

Buy new car (Project)
+ Get bank-credit (Active0)
+ Let wife choose a car (Delegated1)
+ Buy the car (Inactive1)
+ Wait for son to damage the car (Delegated2)
+ Call salvage crane (Inactive2)

Without using Sub-Project I have to alternatives:

Sequencing with delegated excluded: the automatic sequence will be
--
1. Get bank-credit
2. Buy the car
3. Call salvage crane
--
while the delegated actions are ignored.

Sequencing with delegated included: the automatic sequence will be
--
1. Get bank-credit
-- stop. System waits for all delegated actions to be finisched:
2/3. Let wife choose a car
2/3. Wait for son to damage the car
4. Buy the car
5. Call salvage crane
--
I have to finish both delegated actions before "Buy the car" becomes active.

Both variants seems to be not very intuitive, and don't satisfy my needs.

Although, using sub-projects for both Delegated1/Inactive1 and Delegated2/Inactive2 solve the problem, but that will add unnecessary complexity to the project.

Regards,
Thomas.

PS: In fact, an additional "depends on" for all action-types would be very beneficial. Indeed, sequencing should be disabled while using "depends on".

EDIT:
I just realised that Sub-Projects are great tools to create very complex process workflow (using the member-plugins). Unfortunately there seems to be no introduction around.
It would be most helpful to have a help/wiki-topic about "creating complex process workflow using sub-projects" ...