Quote:
Originally Posted by whpalmer4
There are two main schools of thought on this, with the key point being whether or not you make your Waiting context one that is On Hold or not (the one in the canned database that Omni ships is On Hold, as you've discovered). Many experienced practitioners choose to make the Waiting context an ordinary one, and simply don't check the item off until whatever is being waited for occurs. That will block subsequent actions in a sequential group, and illustrate what needs to happen before the project can move forward.
|
That's exactly what I need. Will try turning off the on-hold status of the canned database and see if that helps.
This seems to be a case of hybrid context. From
my perspective it is on hold; there's nothing that I can personally do to move it forward. On the other hand I'm not going to let someone indefinitely stall a project, so at some point I'll either do the task myself (if possible) or delegate it to someone else, so from that viewpoint I can still move the project forward if enough waiting-for due dates expire.
- Steve