On Thursday, July 2, 2015 at 6:04:57 PM UTC+2, Javier Guerra wrote: > good luck! > > -- > Javier >
Thanks for your input! Indeed, a linear pipeline should be sufficient. What do you think of my idea of organizing this in two database tables? One table models a work flow. A work flow points to the currently active task in another table. Each task has information about its predecessor / successor. In principle like a doubly-linked list. This solution feels a bit brittle / hacked to me. Again, my reason is, I want to store all the work flows with this standard interface. Also, users can easily create new work flows with any number of steps. Maybe there is a better way? In case you are interested: I wrote earlier that I am developing this for a landscape gardening company. Since the company grew quite a bit recently and more people are working in administration, it is necessary to organize the flow of jobs: Quickly see who is responsible, what is currently happening, which jobs are overdue. Also each job is touched by different people (something like acquisition -> execution -> accounting) and the framework should organize this as well. There are different work flows for example to execute work and to make a quotation. Until now this is organized using a combination of paper and memory which is not feasible anymore. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/4576fa8b-b19f-4348-b254-1e7cbf581cc1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
