Self Service Responsive App (25A) Charge Account not derived
Summary:
Currently implementing the Requisition Self-Service Responsive App. When there is a violation of the CRV rules, it now states "Charge Account not deived" instead of the CRV error message that would normally appear. This appears to be a bug in design.
New message:
Previous message:
This also allows you to submit without a selected Charge Account! - How to stop this???
Content (please ensure you mask any confidential information):
I am concerned that the user has no way of identifying the error in charge account and with the ability to just submit anyway, they will just create orders without any costing. This will become an accounting nightmare!
Tagged:
0