Case Scenario:
Customer modified the Customer Support - Resolve Page so when the order is flagged as Resolved, the Problem, Cause and Repair codes were mandatory.
[Mimics the functionality for Workflow (Service) of setting these codes mandatory when resolved which Workflow (Cust. Support) does not have the same functionality.]
This was working in the UI properly for the Customer Support module however when the same orders were to be invoiced by a batch via Audit Queue they did not invoice and event log errors appeared such as ‘Problem Code Description is mandatory’. It was not possible to invoice the orders from the queue in the batch but was possible to invoice from within the customer support order itself.
The setup of the mandatory condition by the customer was as below:
While this works in the UI for the resolve page, it does not work for other batch processes not using the page.
Solution:
Note the red text in the dialog window which warns that you must add the underlying column with a check if the value is null.
If you want to mark a computed column as mandatory, you must add a condition connecting this computed column to the underlying real column stored in the database. For performance reasons many computed columns are populated only for UI.
In the batch process these computed columns remain empty and you are getting the mandatory exception because you are validating the computed column and not a real id column stored in the database. In case of the Problem field, you need to make it mandatory only when the underlying pcode_id field (Problem Code) is empty.
The corrrect setup would look something like this:
After this configuration change for all three codes (Problem, Cause & Repair) invoicing customer support orders in a batch from the Audit Queue was again possible.