#80 Asynchronous/decoupled validation of messages

[Maarten Ligtvoet]

Feature request/performance enhancement:
Browsing to testen/berichten (tab validate) it starts validating when I click on separate messages. The results of validation are not stored.
Validating could also have taken place before viewing messages.
When clicking through various testaccounts on this page, sometimes the messages are not always updated, the cause could be inline validation which costs performance.

Suggested feature:
- Validate incoming messages after they are stored to the database (possibly a trigger on the messages collection?). Messages can already be uploaded or sent to server through the SOAP-interface.
- Store the validation results and display these when viewing testen/berichten.
- Optional: create a 'revalidate' button to trigger re-validation. Use case is that messages might have been changed in the messages collection (with oxygen/..), after the first validation.

[Alexander Henket]

Validation results are currently saved and retrieved if present. Button to clear those stored results is implemented.
Trigger is still not implemented so no decoupling between user action and validation.

Is that necessary to close this issue?

[mgraauw]

This request does not seem correct to me (maybe it's outdated).

Validation is done immediately after uploading, and validation results are stored. Validation is never done twice, unless a user clicks 'Clear validation and test results', in which case removal is intentional. The 'Clear...' button is there in cases where the HL7 materials are changed (quite often suppliers pick the wrong one, or materials are changed due to a bug there), thus enbaling re-validation without removing and re-uploading all messages.

[Alexander Henket]

Fixed