5.11.2

Release date: 2019-04-01

Remarks

This release uses the latest version of Gazelle X Validation module, see changes below.

Gazelle X Validation 1.4.1

Bug

  • [XVAL-162] [Cross-Validator] Edition des ID

5.11.1

Release date: 2019-03-15

Remarks Management of the datasource has changed. Refer to the installation manual to configure your Jboss when updating to this version.

Improvement

Message Content Analyzer 2.3.1

Bug

  • [MCA-97] [ASIP XDM] No CDA file in archive should generate an error

5.11.0

Release date: 2019-03-05

Improvement

  • [EVSCLT-801] Add AssertionCoverageProvider API reference from X Val WS
  • [EVSCLT-806] The administration menu for X validator shall be moved under add-ons

Gazelle X Validation 1.4.0

Story

  • [XVAL-157] Detect files resulting from XDM Detection in MCA and send them back

Improvement

  • [XVAL-159] Review the XSL stylesheet to display the abort reason to the user

Message Content Analyzer 2.3.0

Bug

  • [MCA-84] ZIP architecture not properly displaying in analysis results
  • [MCA-85] MTOM Not detected when X509Certificate xml tag in content
  • [MCA-86] The MCA looses the information on calling tools when called from remote validator
  • [MCA-94] XValidation results are not persisted in analysis results
  • [MCA-95] Prevent User from sending an archive to validation
  • [MCA-96] Not logged in User is able to filter analysis logs on users

Story

  • [MCA-87] Create XDM Detection
  • [MCA-88] Send Subparts to Cross-Validation
  • [MCA-89] Find analysis log from analysis subpart oid

EVSClient-connector 1.3.0

Bug

Story

5.10.3

Release date: 2019-03-02

Gazelle X Validation 1.3.0

Improvement

  • [XVAL-149] Add a MANIFEST in input’s MessageType enumeration
  • [XVAL-150] Manage input optionality in the cardinality

5.10.2

Release date: 2019-01-02

Bug

  • [EVSCLT-797] No Validation Result when xml document is not well formed

5.10.1

Release date: 2018-12-20

Remarks For the task EVSCLT-792, part of the work was done in Gazelle Test Management size. To benefit from the harmonization of validation results between those tools, it is required to work with Gazelle Test Management version 5.9.5 or higher. There is however no compatibility problem if another version is used.

Sub-task

  • [EVSCLT-792] Harmonize style of the result between TM and EVS

Bug

  • [EVSCLT-739] No status given when validating with dciovfy
  • [EVSCLT-755] DICOM Validation result does not show correct Dicom Operation
  • [EVSCLT-776] Impossible to delete a tool referenced in Calling Tools menu
  • [EVSCLT-790] MBValidation stub timeout is not working

5.10.0

Release date: 2018-10-31

Remarks

The “version” module with version 2.0.0 is only compliant with Widefly 8 and thus not applicable to this version of EVSClient.

Bug

Message Content Analyzer 2.2.1 changes

Bug

  • [MCA-80] Performance issue due to overly complex regex for xml tag detection
  • [MCA-81] Missing translation from 2.1.0

Gazelle X Validation 1.2.0 changes

Bug

  • [XVAL-120] Add an input button is not working after saving a validator
  • [XVAL-121] Problem after resetting validator during cross validator selection
  • [XVAL-122] Fix cross validation inputs number detection in EVSClient
  • [XVAL-123] Add a rule button is not working after saving a validator
  • [XVAL-124] Fix the link in Edit Rule to go back to Validator Editor instead of Validator Documentation
  • [XVAL-128] Add inherited inputs in validator inputs table when calling a validator
  • [XVAL-129] Validation log page is empty

Story

  • [XVAL-140] Hide create unit test file button when no textual expression has been created

Improvement

  • [XVAL-127] Add REST method to POST validator status

Dependencies

5.9.0

Release date: 2018-10-11

Remarks

WARNING : When deploying EVSClient version 5.9.0 , make sure that EVSClient version 5.8.x has been deployed on the server and that the migration of analysis data is over. You can then deploy this version and apply the SQL script without loosing any analysis data.

Message Content Analyzer 2.2.0

Bug

  • [MCA-31] Blank page when trying to access an analysis result report with unappropriated rights.
  • [MCA-76] XML part download does not show the popup + file extension

Task

  • [MCA-69] Add Sample field in configuration
  • [MCA-74] Improve the MCA Config page
  • [MCA-75] Add import/export functionality for MCA configurations
  • [MCA-79] Change GUI info to popovers

5.8.1

Release date: 2018-10-10

Bug

  • [EVSCLT-788] Confusion between the integration of new SchematronValidator webservices

5.8.0

Release date: 2018-10-05

Remarks

The sql script “update-5.8.0.sql” shall be completed with values depending on the installation where the tool will be deployed. This version of EVSClient is not compliant with versions of SchematronValidator prior to 2.4.0.

Improvement

  • [EVSCLT-786] Update to be consistent with SchematronValidator 2.4.0 improvement

5.7.2

Release date: 2018-10-03

Bug

  • [EVSCLT-768] Legend for statistics on result status is not complete
  • [EVSCLT-777] Missing acces rule
  • [EVSCLT-784] Missing preference causes XValidators oid to contain ‘null’

5.7.1

Release date: 2018-09-21

Bug

  • [EVSCLT-783] PDF validation log page does not display all results when arriving on the page

5.7.0

Release date: 2018-09-14

Remarks

A new module has been released : Gazelle Calling Tools 1.0.0. This module is now in dependence in a jar with EVSClient and Gazelle X Validation module embedded in EVSClient.

Bug

  • [EVSCLT-774] TM does not display the right result for PDF validation from EVSClient (sample validation)

Message Content Analyzer 2.1.0

Epic

  • [MCA-60] Define and Externalize MCA configuration

Cross Validation 1.1.0

Story

  • [XVAL-19] API Implement a web service for remote validation
  • [XVAL-104] Each X Validator shall have an OID
  • [XVAL-105] “Tag” the inputs
  • [XVAL-116] Remote validation - Handle the case where the validator OID is not provided
  • [XVAL-119] Allow the user to access the XValidator documentation knowing the OID of the validator

EVSClient 5.6.2 changes

Release date: 2018-07-19

Remarks

MCA data migration will suppress all record in database that are not linked to a file or that are linked with a file that does not exist.

Story

  • [EVSCLT-772] Display validator version in the validation result

Message Content Analyzer 2.0.0

Bug

  • [MCA-17] FileToValidate model serialization bloc migration and model evolution

Story

  • [MCA-9] API improvement

gazelle-assets 2.0.24

Added stacked icon style class “gzl-icon-stack-small-bottom-right” for MCA “Validate without known Validation Type” button.

5.6.1

Release date: 2018-05-30

Remarks

The sql script ‘update-5.6.1.sql’ allow to update the preference of the ‘fhir_repository’ which contains one more space in the ‘update-5.3.0.sql’.

Bug

  • [EVSCLT-753] Impossible to validate messages with FHIR validation service
  • [EVSCLT-760] User is not informed that the validation result is in TM test step
  • [EVSCLT-761] Error when we validate sample which is download from EVSClient
  • [EVSCLT-763] File validation permanentlink is not updated

5.6.0

Release date: 2018-05-28

Remarks

In addition to the update_5.6.0.sql script, there is also update_5.6.0.sh to execute to migrate validated files on disk.

Bug

  • [EVSCLT-736] The upload widget is not available on XML based validation page
  • [EVSCLT-752] Cannot access all logs for PDF validation
  • [EVSCLT-753] Impossible to validate messages with FHIR validation service
  • [EVSCLT-756] Signature validation report is not displayed in the validation report

Message Content Analyzer 1.0.0

Epic

  • [MCA-5] Isolate Content Analyzer as module

Bug

  • [MCA-23] Infinite loop on SAML Assertion detection in Content Analyzer

5.5.0

Release date: 2018-03-31

Epic

  • [EVSCLT-705] [KELA] Validation of Digital Signature

Test

Bug

  • [EVSCLT-734] After logging, the parameters are not passed in the URL

Story

  • [EVSCLT-733] [KELA] Detect signature in CDA documents and validate

Improvement

  • [EVSCLT-706] [KELA] Add a Digital Signature validation module
  • [EVSCLT-735] Use of the IOUtils.closequietly in finally’s in order to clean up the code

5.4.0

Release date: 2018-03-02

Bug

  • [EVSCLT-698] When several menu entries reference the same standard type, it is impossible to access all of them

Story

  • [EVSCLT-723] [KELA/GDPR] Execution of GDPR rules

Improvement

  • [EVSCLT-696] Try to really apereo cas logout
  • [EVSCLT-702] [KELA/GDPR] Allow the administrator of the tool to enable/disable the GDPR-checks
  • [EVSCLT-725] [KELA/GDPR] Writing of GDPR rules (javascript)

5.3.0

Release date: 2017-12-21

Remarks

From version 5.2.10, EVSClient is making use of the new Gazelle SSO (Apereo). Configuration of the SSO is no more done in database. Make sure the configuration file is available on the server hosting EVSClient at /opt/gazelle/cas/file.properties.

Bug

Story

  • [EVSCLT-672] Description field of standard could support HTML tags
  • [EVSCLT-673] Display description field of validation service on validator page

Improvement

  • [EVSCLT-676] We shall be able to call the FHIR Validator from EVSClient

5.2.10

Bug

  • [EVSCLT-645] [EFS] No specific errors when DFDL error happens
  • [EVSCLT-659] Problem in the view of the XML

    5.2.9

Bug

  • [EVSCLT-655] [EVS Client] Pb with buttons “Make this result public” / “Share this result”
  • [EVSCLT-657] Bad label for menu visibility

5.2.8

Bug

  • [EVSCLT-637] Template tree has been tested, remove the “experimental” word

    5.2.7

Bug

  • [EVSCLT-617] When there are only one schematron in CDA validation, it is selected for validation even if you deselect it
  • [EVSCLT-628] Button validate again is not working, when revalidating a CDA document
  • [EVSCLT-641] Missing translation strings
  • [EVSCLT-642] Unexpected entries in Model-based report (PDF version)
  • [EVSCLT-644] [EFS] Revalidate button in EVS Client does not load the existing file
  • [EVSCLT-648] When we validate a CDA document that contains a PDF as a and not embeded B64, we still propose to validate it using the PDF validation

Story

  • [EVSCLT-646] [EHEALTHBEL] The XSL of CDA.xsl cannot be configured in EVSCLient

Improvement

  • [EVSCLT-620] [Sequoia/CDA] Make the SchematronValidation exportable as PDF

5.2.4

Bug

5.2.3

Improvement

  • [EVSCLT-636] Add the ability for a menu to be only accessible to logged in users

5.2.2

Improvement

  • [EVSCLT-623] Improve verbosity of mail send by EVSClient when access to External validation service does not work

5.2.1

Story

  • [EVSCLT-630] URL to assertion manager is hard-coded

5.2.0

Release date: 2017-06-17

Improvement

  • [EVSCLT-627] Update to newest version of gazelle-x-validation

5.1.6

Improvement

  • [EVSCLT-626] Add a delete validation result for admin

5.1.5

Bug

  • [EVSCLT-562] Cannot navigate among issues in the CDA (Firefox)
  • [EVSCLT-563] Issues with some documents
  • [EVSCLT-612] Unsubscribe DSUB messages are not detected in the Content Analyzer

Story

  • [EVSCLT-122] NPE when validating a message with bad MSH-1

Improvement

  • [EVSCLT-340] Content Analyzer should recognize MTOM even if we do not start by the MTOM section

5.1.4

Release date: 2017-05-02

Bug

  • [EVSCLT-618] Message Content Analyser edited message not taken into account
  • [EVSCLT-619] The link on the eye icon to goto the error in the code on the validation page does not work in some cases

Story

  • [EVSCLT-538] [Sequoia/CDA] Make the report exportable as PDF

5.1.3

Release date: 2017-03-30

Bug

  • [EVSCLT-604] Link to validation result bound to a proxy URL does not lead to a valid page
  • [EVSCLT-606] Call to DCCHECK validation service does not work

5.1.2

Release date: 2017-02-08 Bug

  • [EVSCLT-602] GetValidation*ByExternalId does not return accurate result

5.1.1

Bug

  • [EVSCLT-601] Automated message analyzer truncates some of the DSUB messages

Improvement

  • [EVSCLT-600] File extensions of files that can be uploaded shall be configurable

5.1.0

Release date: 2017-01-13 Remarks

This version (5.1.0) of EVSClient will be able to communicate only with instances of Schematron Validator 2.1.0 and higher. This version also embeds the scorecard service for CDA document, the one is available in CDA Generator 2.1.1 and higher.

Technical task

  • [EVSCLT-539] [Sequoia/CDA] Display advanced filters
  • [EVSCLT-541] [Sequoia/CDA] Display statistics on template usage part of the scorecard
  • [EVSCLT-542] [Sequoia/CDA] Display statistics on document part of the scorecard
  • [EVSCLT-543] [Sequoia/CDA] Define how EVSClient retrieves the scorecard from Gazelle Object Checker
  • [EVSCLT-544] [Sequoia/CDA] EVSClient shall retrieve the scorecard for a given CDA

Bug

  • [EVSCLT-404] DB Script to add WS Trust is missing
  • [EVSCLT-450] Allow user to perform a new validation
  • [EVSCLT-455] DICOM validate again button does not work
  • [EVSCLT-493] Validation result information panel is displayed differently
  • [EVSCLT-514] The user is no more able to validate a new document
  • [EVSCLT-555] When you show the result of validation, we don’t see the documentation from CDAGenerator but we see the link to the assertion
  • [EVSCLT-559] Stastitics are not displayed for the validation kind selected by the user
  • [EVSCLT-561] Schematron validation results: cannot hide/unhide reports
  • [EVSCLT-564] Improve display of information section
  • [EVSCLT-566] “Make this result public” does not work as expected
  • [EVSCLT-569] Privacy of HL7v2 validation result is not accurate
  • [EVSCLT-570] HL7v2: Reset button does not work
  • [EVSCLT-571] Review display of header of HL7 message profile selection table
  • [EVSCLT-577] I see no difference between two methods of DICOM3TOOLS
  • [EVSCLT-579] DICOM Web Validation does not work
  • [EVSCLT-580] CDA Validation: Notification filter based on template tree does not work
  • [EVSCLT-584] No data available in Sequoia CDA validation Staistics page
  • [EVSCLT-585] [Add-ons/Schematrons] The list of schematrons : filters for label and name don’t work

Story

  • [EVSCLT-529] compute statistics is twice in EVSClient
  • [EVSCLT-534] [Sequoia/CDA] Display the CDA scorecard (produced by GOC)
  • [EVSCLT-556] HL7v2 : Validation result is never send to the proxy

Improvement

  • [EVSCLT-565] Allow user to “unshare” a result
  • [EVSCLT-572] Consider showing the privacy in the log table
  • [EVSCLT-574] H7v2: Add a faces message or scroll down to validation report
  • [EVSCLT-575] HL7v2: Filtering of notifications do not work on validation page

5.0.14

Bug

  • [EVSCLT-408] In CDA validation result, if user try to sort by extension it doesn’t work
  • [EVSCLT-495] Gazelle Cross Validator doesn’t work
  • [EVSCLT-553] Admin user should see as much as the users with the monitor role

Epic

Improvement

  • [EVSCLT-441] Make sure the tool creates directories with 775 rights
  • [EVSCLT-516] Allow the same feature in MBV and Schematron validation reports

5.0.13

Bug

  • [EVSCLT-533] HL7v3 validator doesn’t load properly the XML file.

Story

  • [EVSCLT-113] add pretty formatting when validating XDS metadata
  • [EVSCLT-530] The errors are not CSS displayed in validation of XDS metadatas

Improvement

  • [EVSCLT-330] Harmonisation of xsl files for validators.
  • [EVSCLT-536] Page for the management of CDA templates did not make it through the migration to Jboss 7
  • [EVSCLT-537] Cannot sort/filter validation logs by schematron or model based used
  • [EVSCLT-552] Problem rendering non ascii characters when using jhighlight

5.0.10

Technical task

  • [EVSCLT-550] [Sequoia/CDA] Integrate the new report for CDA in EVSClient

5.0.9

Improvement

  • [EVSCLT-549] Add a preference to hide the add-ons menu.

5.0.8

Release date: 2016-11-25

Bug

  • [EVSCLT-545] Webservice to get last validation permanent link return last validation date
  • [EVSCLT-222] DiskStorePathManager for CacheManager is set to /tmp
  • [EVSCLT-525] Validation of PDF embedded in CDA does not work
  • [EVSCLT-526] UserAdmin.css is not used but embedded in the EAR. Should be removed.
  • [EVSCLT-527] Calling tool page : Table scrolling does not work.
  • [EVSCLT-463] EVSClient - epSOS Validators - Reset button changes validators
  • [EVSCLT-468] When Schematron validation is performed, the validation result is empty
  • [EVSCLT-472] XD* Validation : XSL model based report has old style
  • [EVSCLT-477] HL7v2 validation report : “Profile exceptions” panel has old style
  • [EVSCLT-482] AuditMessage validation report xsl has old style
  • [EVSCLT-483] DSUB validation report XSL has old style
  • [EVSCLT-519] Missing EVSClient-dist.zip for 5.0.0 on nexus
  • [EVSCLT-522] The creation of a new reference standard does not save the name of the referenced standard

Improvement

Story

  • [EVSCLT-521] in Manage referenced standards the filtering related to extension disapeared

5.0.0

Release date: 2016-09-05

Remarks This is the first release of the EVS Client application for the Jboss 7 Application Server. The entire design of the application has been reviewed. The application now uses the harmmonized layout of the Gazelle Test Bed applications.

This version does not yet include the Gazelle Cross Validator component.

Bug

  • [EVSCLT-396] Errors in ovh3 logs
  • [EVSCLT-414] Message content analyzer fails to show re-analyze of edited message/content
  • [EVSCLT-415] Revalidate doesn’t work anymore for Content Analyzer
  • [EVSCLT-423] Empty element not recognized
  • [EVSCLT-425] Infinite Loop when validating the WS-TRUST response file
  • [EVSCLT-426] Bug in the javascript of the list of checks
  • [EVSCLT-451] Update Schematron validation report stylesheet to new style
  • [EVSCLT-452] Missing translation keys
  • [EVSCLT-453] CDA HTML view is not rendered
  • [EVSCLT-454] DSUB content is not displayed as HTML
  • [EVSCLT-466] A broken image is displayed next to the username when you are logged in with the CAS (Firefox)
  • [EVSCLT-467] When a FacesMessage is displayed, it never disappear
  • [EVSCLT-469] Show templates tree : no tree is displayed
  • [EVSCLT-471] On permanentlink result, the font is changed (blue, with smaller pixels)
  • [EVSCLT-473] User can’t access the list of Schematron
  • [EVSCLT-474] HL7v2 validation : Error The given Id is unknown
  • [EVSCLT-476] Revalidate an HL7v2 message trigger a Null Pointer Exception
  • [EVSCLT-479] PDF validation have old style
  • [EVSCLT-481] In statistics if user click on compute stat the application crash
  • [EVSCLT-485] HL7v3 validation report XSL has old style
  • [EVSCLT-486] Assertion (SAML) validation report XSL has old style
  • [EVSCLT-487] There is no check to verify that the XSL input is really an URL
  • [EVSCLT-488] HPD Validation report XSL has old style
  • [EVSCLT-489] SVS Validation report XSL has old style
  • [EVSCLT-490] Administration -> Manage referenced standards : inconsistency with gazelle style
  • [EVSCLT-491] Title of “Reuse message” button (refresh icon) displays crowdin key
  • [EVSCLT-492] Change referenced standard create / edit layout
  • [EVSCLT-494] CDA validation report : HTML file content XSL is inconsistent with new Gazelle style
  • [EVSCLT-496] CDA Validation Report : Check “show template tree (experimental)” change layout.
  • [EVSCLT-497] When editing a referenced standard, transaction failed when adding an XSL location
  • [EVSCLT-500] HL7v2 validator list : “Validate with the profile” has an old-styled icon
  • [EVSCLT-501] EVSClient menu : icons that are not a brand should be font-awesome icons
  • [EVSCLT-502] Manage calling tools : If you create an already existing preference property, there is a transaction failed, it should instead be handled with a message saying that the property already exists
  • [EVSCLT-503] Create calling tools :If you register the same tool (same label and oid) there is a transaction failed instead of a message
  • [EVSCLT-505] Can’t acces to previous validation in Dicom SCP Screener
  • [EVSCLT-506] Menu configuration : No confirmation popup when deleting an entry
  • [EVSCLT-508] Manage Validation Services -> Edit : Inconsistency with the database
  • [EVSCLT-515] link to assertions in CDA result is not correct
  • [EVSCLT-518] for dcmcheck we are not able anymore to edit the service in V7 version

Epic

Story

Improvement

  • [EVSCLT-341] Integrate the Gazelle X Validation module
  • [EVSCLT-345] Add HTTP detection in Content Analyzer
  • [EVSCLT-386] Can we have the checkbox to hide the passed requirement when we validate a HL7 V2 message?
  • [EVSCLT-419] Fix GUI issues
  • [EVSCLT-420] Review menu layout
  • [EVSCLT-421] migrate pixelmed-jar
  • [EVSCLT-459] remove Cache from results webservices
  • [EVSCLT-511] As an administrator of the tool, I need to know which instance of EVSClient is reporting issue in order to manage it
  • [EVSCLT-512] remove ear from EVSClient-dist.zip