The service ERES 2.0 incorporates new integrations with AOC services and the application of model standards eSET
Share
From 03/11/2026 the service ERES incorporates some modifications with the aim of optimizing its operation, making use of other AOC services and standardizing document management criteria, for the application of the model eSet current. The improvements applied are summarized below:
Application of new document nomenclature to adapt it to the model eSet:
Currently, theERES already applies a validation on the structure of the title of the documents, with the aim of promoting the application of common criteria to the organizations that use the service. This structure, which obeys the one defined by the model eSet, has been updated in recent months so that we have adapted it to the new model.
Thus, when previously it was necessary to define the titles of the files that are attached to the records and files complying with the structure Type Code + Description + Date (YYYYMMDD), with the new version this is simplified, making the date optional. So the following criterion for defining the document name must be taken into account: Type Code + Optional Date (YYYYMMDD) + Description
To continue adapting the application to the modifications of this model, we are also working on modifying the classification table and predefined document typologies, which will be applied to future versions of the service.
Incorporation of new integrations with AOC services:
On the one hand, the application starts using DESA'l as a document repository, shared with the rest of AOC services. This integration does not imply changes at the user level, but it does optimize the processing of documents that are managed from a common place in the rest of the services that are also integrated with theERES, as is the MUX for the operation of the unified registry.
D'altra banda, integration with the is enabled Portasignatures of the AOC Consortium to facilitate the document signing process, avoiding dependence on the GENBPM desktop tool and making document signing compatible with the solution's case module, from mobile devices (Android or iPhone).
This new integration means that documents sent for signing from theERES, from now on, they will have to be signed from the Portasignatures and not from theERES (those pending signature, prior to the launch of this new functionality, can continue to be signed from the Signature Holder tab of theERES).
The application will display a message like the one below when creating a new circuit or signature.
Additionally, the service Portasignatures will send emails notifying of documents pending signing, as well as monitoring of defined circuits and completion.
