We have the scenario where the person go decides which purchase requests is different than the person that creates the purchase for the requests. In order for the purchase user to know what to purchase we need to add a new state tot purchase_request which indicates what has to be purchased.
The Best Purchase Date is not suficient information to decide what has to be purchased as we need to prioritize purchase request depending on the production planification.
Currently the purchase_request state is a functional field, so we propose a to add a boolean field on the purchase requests to indicate the “approved” purchase requests and add a new state name “Pending” for the purchase request and with the “approved” field set to true. Of course, the pending state will be set with a button like a normal transition.
This change will imply that “Pending” request must not be deleted when computing requests. So we must use the state (it has a searcher method) in purchase deletion instead of the current domain.
Is anyone else interesed on such feature?
Does anyone have better names for the new state?
Does anyone have some problem with the proposed change?
In order to be in concordance with production requests we may rename the purchase requests Draft state into Request, so we use the same naming.