18
When a user submits a Free Text Invoice (through AR) or a Pending Invoice Journal (through AP) it should validate the Account & Dimension Combinations prior to submitting.
If the combinations don't validate the user should not be able to submit.
This behaviour exists for Purchase Orders and Employee Expense Reports.
Having to withdraw the Invoice, change the dimensions and resubmit through the workflow can take a lot of time, especially if the workflow is quite complex, this process could be missed if the invoice is not able to be submitted without valid dimension/account combination.
If the combinations don't validate the user should not be able to submit.
This behaviour exists for Purchase Orders and Employee Expense Reports.
Having to withdraw the Invoice, change the dimensions and resubmit through the workflow can take a lot of time, especially if the workflow is quite complex, this process could be missed if the invoice is not able to be submitted without valid dimension/account combination.
STATUS DETAILS
Needs Votes
Comments
This is VITAL - currently the workflow for these are unusable without client paid development - why would you not validate a submission prior to Workflow and then when it gets to the end, invalid, it just 'stops' - this is no use to anyone IMO. It is too late to validate at the end of a Workflow.
Category: Workflow
This would save the customer a lot of pain and frustration!
Category: Workflow