1.7 Error message improvement

If you are entering an invoice line item and do not enter a product, then the error message is "Failed to validate Product of Product: Product is required"

This is being generated this was because the Label for the product node of the act.customerInvoiceItem is 'Product' and that of the target node in entityRelationship.productLink is also 'Product'.

I understand the work savings of automatic error message generation, but is some cases the results are a somewhat confusing message.

With regex espression assertions, it is possible to put in you own error message.

Is it possible to generate one's own message is a mandatory field is not present?

Alternatively, so we can continue the use of system generated messages, could the error message be altered to say just "Failed to validate: xxx is required" or "Failed to validate xxx: It is required" where xxx is the Label for the node which is set as mandatory. ie we omit the "of yyyy" where yyyy is the Label of the target none in the entityRelationship archetype.

I can't see that omitting the 'of yyyy' qualifying information is significant because if there are two mandatory fields on the screen, then their Labels cannot be the same because the user would have two fields with the same label.

Regards, Tim G

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: 1.7 Error message improvement

I'd like to get away from the popup dialog validation error message and instead highlight the field that is in error and shift the focus to it.

Raised as OVPMS-1417

-Tim A

Syndicate content