Aurion Person Connector
An Aurion person connector is a reading and updating Connector provided by UNIFYBroker/Aurion.
This connector is an extension of the Aurion generic reading connector, and therefore supports all the same functionality, in addition to being able to update person information.
The Aurion person connector has no additional requirements following the listed connector prerequisites.
In addition to querying data, this connector is capable of updating person information with the EMP_UPDATE_PERS function of Aurion's ev397_aurion_ws web service:
- CONTACT_TYPE_CODE (add only)
- CUSTOMER_OR_SITE_ID (add only)
- EMPLOYEE_NO (update only)
In addition to the standard Query fields schema provider, there is an additional provider called Default Person schema.
This creates a schema based on the fields supported by the
EMP_UPDATE_PERS function. The fields
from this schema provider must be used over those that are returned by the query to allow for exports to occur to those fields. To map between differences in field names
from Aurion query names to schema fields, update the mapping settings.
An Aurion person connector has the same configuration as its base generic reading connector.
From version 22.214.171.124, "Update Key Field" is available for configuration on the Person connector. This allows configuration of which key the connector uses to update entities.
By default, the connector will pick EMPLOYEE_NO as this is the existing behaviour of the connector. This choice requires the connector schema to have the EmployeeNumber field populated. The WAMI_NO option will require the PersonNumber schema field to be set, and will populate the wami_no entry on the API call with that value. Only one field will be sent, so if WAMI_NO is selected then the EMPLOYEE_NO field is not populated on the API call, and vice versa.
Mappings allow fields in the schema to be mapped to the attribute names returned by the Aurion query during read operations. These are required when using the default schema provider, as the schema fields names are not the same as the query field names.
Customer support service by UserEcho
We have a customer with this connector deployed already, and there is a new requirement to write back an attitional attribute value. The above doco suggests that apart from setting up the new MIM attribute flows back to the Aurion MA that there is nothing else to do on the Aurion side to support making a change to meet this requirement - but can you please confirm?
That is the case as long as the field appears in the list of fields listed above that are part of the EMP_UPDATE_PERS function and that field has been mapped to the UNIFYBroker field that you are exporting to.