I don't see exactly how. If you prepare a job, the "path" is already
fixed.... the idea behind a workflow is to make "turns" between several
"paths" in reply to some events or user interactions or states.
That being said, you could theoretically queue tasks dinamically, and the
added feature will help in case those tasks are "segments" of the same
"path".....this means that a "workflow" that describes how to reach Los
Angeles from Washington can be composed by "scheduler jobs" that connect
1-4 cities in a fixed way, but there still must be something ("workflows")
that will "set the path to follow" interconnecting "jobs".
On Thursday, August 7, 2014 3:18:07 AM UTC+2, Andrew W wrote:
>
> P.S. Although I expect they are not the same thing, I am interested to
> see how this dependency feature may be used to implement the workflow ideas
> expressed in:
>
> https://groups.google.com/forum/#!searchin/web2py/workflow/web2py/0z1BysNp8Gc/aQFdaBqymE8J
>
>
>
>
> On Thursday, August 7, 2014 7:28:11 AM UTC+10, Andrew W wrote:
>
>> Sounds great. Looking forward to testing it out. Thanks
>> Andrew W
>
>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
