TASKTYPE_BREAK vs TASKTYPE_CALLSUBTASKS

Hello,

I do not understand the difference between TASKTYPE_BREAK and TASKTYPE_CALLSUBTASKS.

Here is an extract about CALLSUBTASKS task according to the FlexSim user manual (Task Sequences / Reference / Task Sequence Types):

This task is just like the break task, except that it ensures that as soon as the second task sequence is finished, it will return immediately to the next task of the original task sequence

But with BREAK tasks, the TaskExecuter will also return to the next task of the original task sequence. As it is mentioned in the FlexSim user manual (Pick Lists / TaskExecuters / Break To):

When the TaskExecuter receives a "Break" task, this is a notification that it may now put the currently active task sequence back in its queue and see if there are any other task sequences that it might want to do before it finishes the current one.

So are the two task types identical on this point?

The only differences I see are:

1. to specify whether or not the content of the TaskExecuter should be screened before performing the break task (for the "break" task, var1)
2. to specify whether or not the TaskExecuter should check to receive task sequences from an upstream Dispatcher (for the "break" task, var2)

Am I right?

Thanks for your reply!
David

Call Sub Tasks allows you to call and choose sub tasks from within the current TS where as the Break allows the TE to break to other tasks.

Sub Tasks can be used when the destination and states of downstream processes/resources are unknown at the time the TS is created You could for instance decide at a Call Sub Tasks to proceed to a waiting area or direct to the destination when your reached a point in the travel.

Some of the functionality and it's uses will become simpler with the Task Sequence section of the Process Flow Library.