I do not think it is possible to define a trigger for such temporal event.
Any way there is no point for such notification because stock level is managed by the replenishment of stock supply module and maturity date by the dunning modules.
Thanks for clarification.
I think, a flexible and powerful notification feature is essential for ERM. Dolibarr e.g. has got it. In my small enterprise, I’d like to be notified about:
stock levels under order points
customers’ bills becoming mature
suppliers’ bills becoming mature
tax payments becoming mature
tax declaration and other periodical legal obligations are coming close
I’m not certain whether it makes sense to implement the last two in tryton, but at least the first three I think should. I guess, there are quite some more of these issues I’m not aware of.
It should create purchase requests, internal shipments or production requests.
Indeed to see the result it is better to launch the “Supply Stock” wizard which opens the lists of the results.
Right. It is not easy to understand the proceeding.
When I trigger the action manually, it creates a request. But that’s not very useful, as I need to check manually, if a request is created. As there is no alert, I will normally not get aware of that request. Is there a way to create some sort of alert/notification?
Bthw:
When I run the “supply stock” wizard manually, it opens the “internal shipments” window - which is empty. Under “requests”, I can find results which make sense. This is a little confusing to me…
In a big company - certainly.
But in a one-man-business, I would want IT to do such a job for me.
And if I’m certain about one thing: There are quite some more small businesses, than trusts in this world…
The main problem is that the email is sent to the user created the purchase request with a fallback to admin. So the create user should be root when run from the cron. At least the fallback user must have an email address.
The content of the report can be any thing you want (and even use content of the record of purchase request).
Thank you for these tips. It seems, in order to implement this, one must know much more about models etc than I do.
I found a pragmatic approach:
I added the “supply stock” wizard to “actions”, such it is performed at any client launch. It is quick to dismiss it when I’m sure I don’t need it today - but I’m certain to be reminded. Not perfect, but easy and good enough for now.