Closed jbaudoux closed 2 weeks ago
They are mandatory at the portal. In the backend, it could be that a powerless user could not fit an RMA into the existing operation options... but I don't have a strong opinion about it :)
It isn't mandatory because certain flows create the RMAs without that operation defined (and the state in draft), and it should be filled later. If I don't remember bad:
To make it required, these flows should be fixed somehow.
IMO, it would be better to make this configurable in the rma_sale module as a company policy: RMA: Operation required. If it is activated, the field becomes required in the wizard and the RMA form view, so a salesperson cannot create the RMA order without setting the reason. However, for other automatic flows, the creation continues, and the RMA team will fill in the operation later, but cannot process it before doing so.
Thanks for your feedback. I updated the description with this proposal: In rma:
In rma_sale:
Make the rma operation required
As multiple rma operations (return, refund, replace...) are available, I find it important that the user explicitly choose the operation for each product
In rma:
In rma_sale: