[offline81]

Hi Curt,

thanks for your input. can you clarify what you mean with this sentence?

Originally Posted by curt.clifton

As you've seen, this means that actions in the Waiting For context will block subsequent actions in sequential projects, which is what I want and what it sounds like you want.

in sequential workflows the next action blocks always the remaining actions, right? so if the context of the next action is on hold or not has no impact on the other actions. but it does have impact if the next action is available or not and therefore displayed in the next action or remaining view.

is this so correct?

best regards
patrick

[curt.clifton]

Originally Posted by offline81

in sequential workflows the next action blocks always the remaining actions, right? so if the context of the next action is on hold or not has no impact on the other actions. but it does have impact if the next action is available or not and therefore displayed in the next action or remaining view.

is this so correct?

Patrick,

If I understand you correctly, then that's correct.

You may want to experiment a bit with the program. Your concern seems to be with three settings:

• on-hold vs. active status for your "waiting" context
• sequential vs. parallel projects, and
• available vs. next actions display.

That gives 8 possible combinations. So you could make an experimental project with two actions, assign the first action to your "waiting" context, then experiment with the various settings to see what you like.

OF is a very powerful tool. People use it in a variety of ways. It may take some experimentation to figure out how to make it work for you, but for people who like to have a lot of control over their system, OF is great.