| Table of Contents | ||
|---|---|---|
|
Version 02.02.11 - to be announced
Fixes
Changes
The Merchant Id is now displayed on the detail page of a POI.
Version 02.02.10 - 2021-01-19
Fixes
ATHD-134 : Message d'un POI indisponibles
ATHD-138 : Valider la présence des TimesConditions si le exchange policy CYCL (ou DATE) est sélectionné
ATHD-140 : POI Shortname : mise à jour impossible par API et CSV
ATHD-73 : Modification du Short Name non gérée
Removed “Merchant Group” from the documentation of the POI file upload page.
The configuration decoder for the POI messages (ACU) now decodes the E6 template 9F 6E tag and the E8 template tag DF 08.
Changes
A filter on the message type is now available on the POI messages search page.
ATHD-122 : Obtenir un seul message avec API POIMESSAGE
Two v02 API methods (GET and PATCH) has been added to fix ATHD-73.
Slight improvement on how the template data are displayed when clicking on a row. It applies to the E0, E1, E3, E4, E7, EB, EC, ED and EE templates.
ATHD-101 : Afficher le détail des tables E2, E6 et E8.
The tags DF03 in templates E2, E8 and EC are now of variable length. From 2 up to 4 bytes is now allowed. No changes are required for the existing templates.
A new tag, DF67, is added to the template E1. DF13 and DF67 are mutually exclusive. Thus, only one of them can be put in a given template. No changes are required for the existing templates.
Version 02.02.09 - 2020-12-17
Fixes
ATHD-136 : POI configuration creation fails if the POI is using multi-merchant ids and created using the API
Action required: The impacted POI needs to be redeployed since the merchant data was not included in the configuration.
ATHD-139 : Exception sur creation d'un rôle Lecture is fixed.
Changes
ATHD-132 : Liste des AID et services dans template E2
Action required: Usage of the new API calls available in the API V02
ATHD-133 : Liste tables E2 dans POI Profile API
Action required: Usage of the new API calls available in the API V02
Gateway Control File processor now returns more information about exceptions to make the troubleshooting easier.
Added support for the Tag DF5E Quasi Cash Maximum Amount in Application Profiles (E6).
Added support for the Tag DFF5 Quasi Cash Minimum Amount in Application Profiles (E6).
NexoFastConfigurationParser no longer uses dynamic libraries and is now statically linked.
DGNP, DCCQ and DCRR have been added to the messages to send in the Acquirer Protocol Parameters section of the POI configuration.
Action required: A configuration needs to be redeployed to add these new messages.
Introduction of the API V02. See the documentation on the page API V02. The introduction of this new version of the API have no impacts on the existing one. In the future, some functionality will be available in both version of the API. It is encouraged to use or migrate to version 2.
With the introduction of the version 2 of the API, it is now possible to archive the POI messages and the application log entries based on a retention period given in days.
Action required: Call the two new API methods as described in the documentation. The database user given in the web application configuration file (.env) must have the MySQL access right FILE. The deployment strategy might need to be adjusted since the data is archived in file. These file should be preserved. More information is available in the API documentation.
Four new methods are available in the API V02. They return information about the POI profiles, and the Application Log Events. It worth noting that the POI profile methods returns almost all the related details which solves tickets ATHD-132 and ATHD-133.
Version 02.02.08 - 2020-12-03
Fixes
ATHD-130 : The API call templatesE2 returns an error
ATHD-136 : POI configuration creation fails if the POI is using multi-merchant ids and created using the API.
Action required: The impacted POI needs to be redeployed since the configuration was not created.
ATHD-137 : "Configuration not found" lors du TLP si Short Name non renseigné.
Action Required: The impacted POI needs to be redeployed since the configuration created was not readable. It is not required if the POI had its short name filled and redeployed.
Changes
The security tokens “View the Initiating Party Parameters” and “Edit the Initiating Party Parameters” have been renamed to more general names “View the General Parameters” and “Edit the General Parameters“. It also gives access to the newly supported parameter “Protect Card Data” parameter. The default value is the same as before.
The online and offline completion exchange parameter groups now support the ExchangeFailed and ExchangeDeclined parameters. The default values are the same as before.
...