Community mailing list archives

Re: Sale and purchase workflow

Fabien Pinckaers (fp)
- 09/16/2015 04:59:38
> Overwriting a function to trigger actions if not more complex than
> overwriting a workflow. And overwriting a computed fields "like To Invoice
> or To Deliver" is way easier than revamping a workflow to adapt to all
> possible transitions on all states.

Could you maybe hint which method we'd have to overwrite when there is
no more workflow activities but only function fields? Function fields
mean no more trigger we can hook on, or do I miss a new feature to
handle that?

The way that most looks like workflows is to use "Automated Actions" as it does not even requires development. (e.g. when invoice status goes from "Not Invoiced" to "Fully Invoiced") That's pretty much the same behaviour than workflow as it does not requires to develop a module, it's just customizations. (but IMHO, more powerful than workflow as you can do anything without having to worry about the global state of the document)

Example: doing "send an email to France customers, 3 months after the invoice creation if it's not paid" --> That's a pain with workflows and easy with Automated Actions.

If you develop as a module, you can also connect on the action (generate invoice, validate delivery order, ...), instead of connecting on the status change. (invoiced, delivered)