Latest version: 7.131.0.1, SU-ERRU131
Release date: April 16th, 2024

This extension adds the ERRU functionality to EUCARIS, and is deployed by EUCARIS System Updates. General information about system Updates can be found here.

Requirements

The latest release of this extension requires:

Service plugin

This extension installs the required service plugin and adds the ERRU services, authorisation, logging, and XSDs to the EUCARIS core. After installation EUCARIS is able to receive and transfer ERRU 1.5 and ERRU 2.x messages.

Installation

The latest core update must be installed prior to the installation of latest release of this extension. The installation process is described in detail in the “EUCARIS – Installation and Operation Manual.pdf” document, available on this site. To be able to communicate with countries directly connected to the EC Central Hub, the EUCARIS Broker Core Components and EUCARIS Broker ERRU extension must be installed on the same or on a separate system. These components are included in the EUCARIS Core and this Extension.

Upgrade notes

This is a cumulative update. Any previous System Updates do not have to be uninstalled prior to this update. Any existing translated languages, local services configuration, user profiles and logging configuration is retained.

Configuration

Please check for (and install) a new Configuration Update after the installation of this update. If there is no new Configuration Update available make sure to reload the last received Configuration Update using the Configuration Tool (Menu > File > Load Configuration Update > Reload latest downloaded Configuration Update).

Known issues

No known issues.

Testing

The NL test & acceptance server will be available for testing ERRU messages. Please contact EUCARIS Operations if you want to start testing.

Change History

SU-ERRU131

  • 7.131.0.1 Released: April 16th, 2024
  • Updated Broker Translations to meet updated EC MoveHub XSD’s (version 3.3)

SU-ERRU130

  • 7.130.0.1 Released: April 2nd, 2024
  • Added ERRU3.0 Broker translations

SU-ERRU129

  • 7.129.0.1 Released: March 7th, 2024
  • Removed Memberstate from CGR response
  • Added penaltycode 102 to requested penalties of NCR
  • ERRU3 prework

SU-ERRU128

  • 7.128.0.1 Released: December 14th, 2023
  • Added ERRU 3.0 functionality

SU-ERRU127

  • 7.127.0.2 Released: June 26st, 2023
  • Bugfix: Adjusted the description of ERRU Infringement Types 202 and 204

SU-E125-10

  • 7.0.125.10044 Released: July 21st, 2022
  • Added new ERRU Infringement Type Codes

SU-E125-9

  • 7.0.125.9038 Released: September 24th, 2021
  • Removed country ISO code AN from vehicle registration country list

SU-E125-8

  • 7.0.125.8028 Released: April 15th 2020,
  • Bugfix for “Error storing response message in download queue” error when sending ERRU 2.0 messages.

SU-E125-7

  • Released: March 30th 2020,
  • Bugfix: Create NYSIIS key when empty

SU-E125-5

  • Released: February 27th 2020,
  • Bugfix: Incorrect error handling caused incorrect country code ED / EDR, leading to XSD validation error.

SU-E125-4

  • Released: October 25th 2019,
  • Bugfix: Missing file for v7 website. Only a problem by fresh install of server.

SU-E125-3

  • Released: July 17th 2019,
  • Hotfix: Convert EU to NA (countries in body) from CheckGoodReputeResponse version 4.2 to ERRUCheckGoodReputeResponse

SU-E125-2

  • Released: April 18th 2019,
  • Bugfix: ERRU infringement notifications were deleted from the download queue when the business case ID was reused for other ERRU service requests.

SU-E125-1

  • Released: March 18th 2019,
  • Fix which prevents sending statuscode timeout and notavailable to the EC central hub.

SU-E125

  • Released January 30th 2019,
  • MessageID’s are now checked and uniqueness is enforced, in order to prevent errors from the EC Central Hub.
  • Improved translation of coded attributes
  • ERRU Broker (adapted timeout values CGR message)
  • Bug fix 3238: ERRU2.0 – Infringement Response cannot be related to an infringement request

SU-E109-3

  • Released September 21st 2018,
  • ERRU_REQUESTED_PENALTY_TYPE_CODE missing value ‘other’ added in the Coded Attributes

SU-E109-2

  • Released July 16th 2018,
  • Added coded attributes for ERRU 2.x
  • Added support for EC ERRU specifications version 2.4

SU-E109

  • Released May 14th 2018,
  • First release with ERRU 2.0 services. All ERRU 2.0 services implemented.
  • ERRU 1.5 services available for backward compatibility
  • RSI services which will be released in a seperate RSI extension.
  • WebClient is not updated in this release. ERRU 2.0 will be implemented only in WebClient NG

SU-E90-2

  • Released November 23rd 2016,
  • Fixed an issue where responding on a received notification (Send Infringement Notification Response) resulted in an error.

SU-E90

  • Released November 17th 2016,
  • Fixed issue with Regular Expression in the ERRU XSD (simple type RSPDateCCYYMMDD),
  • Fixed time stamps causing issues when composing statistics,
  • Added option to send ERRUStatistics to one or more countries in CC,
  • Translate ERRU StatisticsAck message “HUB already received…” to OK in EUCARIS.

SU-E81

  • Released September 13th 2016,
  • Added support for the ERRU v1.5 message specification, including Serious- and Very Serious Infringements (SI & VSI).
    There are some important notes on the ERRU specification changes in EUCARIS release 7. These notes can be found in the EUCARIS Knowledge base on: https://www.eucaris.net/kb/erru/erru-v1-5-specification-in-eucaris/

SU-E74-3

  • Released May 25th 2016,
  • Bugfix for the CheckGoodRepute MCI requests.

SU-E74-2

  • Released April 12th 2016,
  • This updates fixes an issue that has been raised in the ERRU statistics process. This issue is solved in both SU-U18-2 EUCARIS Core & SU-E74-2 ERRU extension.
    • Detailed information: In the current situation the EUCARIS Broker receives an ACK from the Central HUB, and gives an immediate HTTP OK. Subsequently it happened that the ACK could not be saved in EUCARIS, because the EUCARIS database was down (or any other reason), resulting in a retry of the same statistical records in a retry. The Central HUB does not accept this dataset because they already had received and processed them. Instead of an ACK the request to the Central HUB results in a NACK and this resulting in a process loop. This update contains a fix for this behavior.

SU-E74

  • Released March 24th 2016,
  • Updated XSD’s
    • CheckGoodRepute: FirstName has become mandatory instead of optional.
    • CheckGoodRepute: For DateOfBirth, an incomplete date is no longer allowed.
    • All messages: Tightened date validation.
    • On all date elements, a pattern validation is applied. This pattern will accept all full, valid dates formatted CCYYMMDD (which is the format dates already had), between 19000101 and 29991231.
    • Invalid or incomplete dates are rejected. Examples of dates that were accepted in the past, but will now be rejected : 20160431, 20150229 (the pattern knows about leap years, so it will accept 20160229), 991231 (date without century), 0, 00000000 or 99999999.
  • Bugfix EUCARIS broker: If a CheckGoodRepute request without PlaceOfBirth results in an error, the response messages contained an empty PlaceOfBirthTag that was rejected by Central Hub. Fixed this,
  • Fix for startdate and time recalculation in statistics process,
  • SQL scripts for newly created errorlabel (attribute) when firstname is missing in webclient,
  • Fix for missing StatusCode Node in INAckReceived nodes in ERRUStatistics messages. Always used the default enum value of OK instead of retrieving it from the database. Fixed.
  • For specification changes, please refer to this document.

SU-E63

  • Released: February 18th 2016,
  • Initial release for EUCARIS Release 7.
  • Functional identically to SU-E54.