Aurion Person Connector

Overview

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.

Technical Requirements

The Aurion person connector has no additional requirements following the listed connector prerequisites.

Usage

Reading Yes
Updating Yes
Adding Yes
Deleting No
Polling No

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_PHONE
  • CONTACT_TYPE_CODE (add only)
  • COUNTRY_CODE
  • CUSTOMER_OR_SITE_ID (add only)
  • DATE_OF_BIRTH
  • DOB_DOCUMENT_CODE
  • EMAIL_ADDRESS
  • EMPLOYEE_NO (update only)
  • EXTERNAL_EMPLOYEE_NO
  • EXTRA_FIELD_1
  • EXTRA_FIELD_2
  • EXTRA_FIELD_3
  • EXTRA_FIELD_4
  • EXTRA_FIELD_5
  • EXTRA_FIELD_6
  • EXTRA_FIELD_7
  • EXTRA_FIELD_8
  • FAX_PHONE
  • GENDER
  • GIVEN_NAMES
  • HIDE_MOBILE_PHONE
  • HOME_PHONE
  • HR_PROFILE_COMMENTS
  • MOBILE_PHONE
  • POSTAL_COUNTRY_CODE
  • POSTAL_POST_CODE
  • POSTAL_STATE
  • POSTAL_STREET_ADDRESS_1
  • POSTAL_STREET_ADDRESS_2
  • POSTAL_STREET_ADDRESS_3
  • POSTAL_SUBURB
  • POST_CODE
  • PREFERRED_NAME
  • PRIOR_SURNAME
  • SALUTATION
  • STATE
  • STREET_ADDRESS_1
  • STREET_ADDRESS_2
  • STREET_ADDRESS_3
  • SUBURB
  • SURNAME
  • SURNAME_CHANGE_CODE
  • VALIDATE_ONLY

Schema

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.

Configuration

An Aurion person connector has the same configuration as its base generic reading connector.

Mappings

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.

Is this article helpful for you?

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?

Thanks

+1

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.