Amadis

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 98 Next »

Version 02.02.12 - to be announced

Prerequisites

  • Installation of Atheos Gateway v03.00.00

Fixes

Changes

  • Implemented ticket ATHD-135. An identifier is added to the messages exchanged between the POI and Atheos that ties all the messages of a dialog together. This identifier is available on the User Interface and in the data returned by the APIs.

    • Action required: None.

  • The parameter “Mandatory Security Trailer” has been implemented at the POI / Processors parameters level.

Version 02.02.11 - 2021-05-25

Fixes

  • The title of the page when editing the “Protect Card Data” value in the POI Processor’s attributes was not localized.

    • Action required: None.

  • The initial value was not set properly when editing a boolean attribute.

    • Action required: None.

  • Fixed a few typos and the copyright years

    • Action required: None.

Changes

  • The Merchant Id is now displayed on the detail page of a POI.

    • Action required: None.

  • Some information pop-up has been added to the Poi Processor’s General Parameters.

    • Action required: None.

  • ATHD-142 : Added the support of 4 new processor parameters for the POI. They are Terminal Group ID, Processor Project ID, DID and Transaction URL. They are in the General Attributes in the Processor’s parameters for a given POI. In the POI list, select the Processor’s icon on the left of a POI. Then, edit the parameter for the listed processor. The new attributes will appear in the General Attributes section. The poiattributes API call has been modified accordingly.

    • Action required: None.

  • The UI related to the General Attributes of the POI Processor’s parameters has been improved following the implementation of ATHD-142. This also brings an optional structure modification to the poiattributes API call . See https://teamamadis.atlassian.net/wiki/spaces/agnoswiki/pages/601817188/POI+Attributes#Change-introduced-with-version-02.02.11 for more details.

    • Action required: None.

  • A new general attribute has been added to the POIs. It is now possible to set the Required Software Version of the POI’s software (Arkos) either using the UI (Edit a POI) or the API (POIATTRIBUTES)

    • Action required: None.

  • ATHD-145 : The API call templatesE2 now returns Technology of Profile (DF0F tag)

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.

Version 02.02.07 - 2020-10-15

  • ATHD-129 Exception Erreur : Modification Reconciliation Exchange. Every form using a JSON section were impacted.

Version 02.02.06 - 2020-10-14

  • A POI configuration could be wrong if the tag is only one byte. There is no one byte tag used so far.

  • The POI configuration decoder now support the tag EF of the E6 templates.

  • ATHD-128 : Merchant identifiers are handled properly through the API.

  • An exception was thrown if the initiating party wasn’t set in the POI’s details page.

Installation Notes

  • The content of app/NexoParser must be readable by the web server. Also, the files NexoFastConfigurationParser and NexoFastConfigurationParserWrapper.bash must be executable. This note will apply to all subsequent updates. It will no longer be included in the release notes anymore.

  • The dbscript-v02.02.06.sql must be run using the database user root.

Version 02.02.05 - 2020-10-02

  • The TMS information sent into the POI configuration could be wrong if the TMS definition is modified.

  • ATHD-114: Exception when refreshing details page of a POI deleted by API

  • An issue related to the profile deployment is fixed. The control file sent to the Gateway couldn’t be processed correctly if only one reference profile was used within the configuration.

  • ATHD-76 : The last successfully downloaded POI application version number is now available on the POI detail page and through the API.

  • ATHD-119 : The sort order of the POI Messages is now based on the Gateway Date, the Poi Id and the message sequence number.

  • ATHD-121: The version of the POI configuration is returned when a POI is deployed using the API.

  • ATHD-117: The files available on a POI Software Update Server can now be displayed using the left menu option Software Updates > Manage Servers

  • ATHD-116: Files on the POI Software Update Server can now be deleted using the left menu option Software Updates > Manage Servers

  • A POI configuration contained in an ACU message can now be decoded from the web user interface using the left menu option POIs > Nexo Messages. Click on the open box icon beside an ACU message.

  • A ACU decoder is available using the left menu option Tools > Decode an ACU.

  • ATHD-110: The Back button sometimes does not return the user to the proper page when on a form there is an input error.

  • ATHD-123: The initiating party is now displayed in the details page.

Installation Notes

  • The content of app/NexoParser must be readable by the web server. Also, the files NexoFastConfigurationParser and NexoFastConfigurationParserWrapper.bash must be executable.

  • The dbscript-v02.02.05.sql must be run using the database user root.

Version 02.02.04 - 2020-08-18

  • The database script for release 02.02.03 was not supposed to use some auto-increment values.

Version 02.02.03 - 2020-08-10

  • Added the online transactions, off-line transactions and reconciliation exchange parameters at the POI level.

  • Added the TMS time conditions parameters.

  • Few cosmetic changes.

  • An issue following the update of the development framework prevented the list of users from being displayed.

  • ATHD-112 : ProcessorData attribute returned in a different format than sent in SetSomeAttributes

Notes

Atheos Gateway Controller

Make sure that the user associated to the API token used by the Atheos Gateway Controller has the permission token "Add events to the Application Log" in one of its roles.

Parameters related to the online transactions, offline transactions and reconciliations

These parameters can be found in the Details option of the Processors main list.

It is also possible to specify these parameters for each POIs. The values given for a POI will override the ones given at the Processor level. They are available through the Processors option of the POI list. You must then edit one of the processor to specify the parameters. Take note as of today, only one processor is supported by the system.

It is also possible to set these parameters using the Atheos API. Details can be found at Atheos API Guide.

TMS Time Conditions

The TMS Time Conditions are accessible through the Details page of a POI. A section is given at the bottom of the page. If the user has permissions to do so, they can then be modified.

It is also possible to set these parameters using the Atheos API. Details can be found at Atheos API Guide.

Updated Components

  • Web interface (AtheosServer)

  • Gateway Controllers (AtheosGWController)

  • Database Content

Version 02.02.02 - Never released

Version 02.02.01 - 2020-07-16

  • Implemented ATHD-29 : User interface to load application packages in the Software Provider

  • Improved the left menu organization

  • Removed all the boxes related to the templates on the Dashboard

  • Many cosmetic changes

  • The name of the Time Server must now be unique

  • The name of the Processor must now be unique

  • The name of the TMS Host must now be unique

  • The logs of the Gateways controller are now sent to the Atheos Server Log

  • Fixed a regression when a POI is re-enabled. The profile wasn’t deployed.

  • Fixed ATHD-112: ProcessorData attribute returned in a different format than sent in SetSomeAttributes

Notes

Software Provider

A few changes have been introduced in order to implement the Software Provider. It supplies Arkos upgrades to the terminals.

The module formerly called Host Communication Parameters has been split in two: Processor Hosts and TMS Hosts. They can be found in the Server and Hosts menu.

The module Processor Hosts now only contains the Processor’s servers as previously define in Atheos. The TMS servers have been moved in the module TMS Hosts.

TMS Hosts holds the definition of the TMS servers the same way as in the former option Host Communication Parameters. Nevertheless, there is now two types of server: TMS and Software Update. The later has been introduced in this new Atheos Server version to tag the software update dedicated servers. TMS tags the TMS server as defined in the previous version of Atheos Server.

A Software Update server holds the newest Arkos software packages that can be downloaded by the terminals. The Software Update Port field on the user interface form is only used for the Software Update servers. For a TMS server, set it to zero (0).

Access the menu item Software Updates from the left menu to publish a new version of Arkos. To do so, give a name to that version, choose the servers onto which you want to make available the new version, select the software package (AIP) that contains the new version of Arkos and finally click on the Publish button. Within the next minute, the software packets will be distributed on the chosen servers.

The server list comes from the server tagged as Software Update defined in the TMS module.

Updated Components

  • Web interface (AtheosServer)

  • Gateway Controllers (AtheosGWController)

  • Server Controller (AtheosServerController) - a new component

  • Database Content

  • No labels