Changes in messaging Representa: implications for integrators

As we informed you on September 4, from the service Representa have been carried out new functions and various changes to improve the operation of the platform. These new features and changes have meant changes to messaging, with implications for integrators.

These changes have been operational since last October 16 in the pre-production environment and the next one January 15th they will go into production, for this reason, please review them carefully, especially the schema change, which you will need to modify if you validate it.

Schema modification: mandatory if you validate it

IMPORTANT: There have been several changes to the schema (listed in the following points) that may affect how you function when you call us, if you validate the schema. They are optional fields (we always put it that way so that it does not affect), therefore, if you are protected, there will be no impact. But if you do a schema validation, and even if they're optional, you return an error, we'll need to review them and confirm that your calls are working properly.

Below is the diagram so that you can see these new fields, discussed in the following points.

Extension of contact data with the “Mobile phone” field (optional field)

With the aim of expanding the notifications sent to citizens, the “Prefix” and “Mobile Phone” fields have been incorporated into the database, to be able to send notifications by SMS in relation to possible changes in the status of the representations.

Both fields are optional. 

Modification of the “Surname” field to adapt to the REA NTI (optional field)

In relation to the tasks arising from the adaptation of the platform Representa In the new Technical Standard for Interoperability on Electronic Registers of Powers of Attorney (currently still in draft) for integration with Apodera, the Electronic Register of Powers of Attorney of the General State Administration, the fields referred to "Surnames" of the database have been expanded. Representa. Therefore, the fields “Surname1” and “Surname2” have been added to the current “Surnames” field (which included both surnames).

In this sense, the three fields will coexist, it being possible to continue sending the "Surname" field including the two surnames as before, this field being sent as "Surname1" when the integration with Apodera is in effect. So, although the field "Surnames" can continue to be sent instead of the new fields, it is recommended to migrate to two surnames for the sending of more precise information.

Extension of personal data with the field "Sent name" (optional field)

With the intention of addressing citizens with the name with which they feel identified, the field "Heard name" has been incorporated into the database, to be able to send notices with this name, in addition to the name that appears in the DNI/NIE or Passport.

The sent name field is an optional field.

Modification in relation to the consultation of representaactive actions

In order to improve the queries made on the platform, it has been incorporated into the query of the representaactive actions, those that are in the “Pending signature” status and additionally, the “Current” field will be incorporated into the response to inform about those representations that, in addition to being considered active, are in force at the time of consultation.

You can check the missatgeria for all the details and for any questions or comments you can contact him Support for Integrators.

Published in