With an outbound mode Code-Free Flat File Connector, EmpowerID can export data as file dumps. External systems can then process the exported files with any custom logic. This connector can identify and export Person & Account attribute changes in the EmpowerID system. You can additionally configure flags to determine if a record was modified, deleted, or added in EmpowerID. External systems can then import these file dumps with their processing logic. Follow the steps below to configure an account store for outbound flat file connectors,.
Steps to Configure an Outbound Flat File Connector
| Note |
|---|
It would be best to Create Data Model Mapping File for the connector before following this doc. The Data Model mapping file maps the EmpowerID object attributes to the columns of the delimited file. Simply, it specifies what data to export from EmpowerID to which column of the flat file. This document focuses specifically on creating an outbound flat file connector. For a more generic document that describes both inbound and outbound connectors, refer to the document linked here. |
| Info | ||||||
|---|---|---|---|---|---|---|
Creating a Code-Free Flat File Connector account store will create a corresponding SetGroup or Query Based Collection. The naming convention for the set group is adding _SetGroup to the end of the identifier of Account Store. e.g., If you create an account store named HROutboundFileConnector, the corresponding setgroup will be called HROutboundFileConnector_SetGroup. Click on Query Based Collections to learn more about it. The following things will be done in the SetGroup to configure the connector.
|
...