Exporting Information

This topic describes the steps to enable an Anthology Reach user to export records to an external system (such as, PeopleSoft, Banner).

Prerequisites

• In the integration mapping record of an entity field, verify that the column number is set in the Field Order Number field.

  In the export framework, the administrator can set the order of occurrence of data of a source field in columns of the exported file. For example, the order of occurrence of the Mobile Phone and Email Address fields can be 5 and 6, respectively. This means that in the exported file, data of all Mobile Phone numbers will occur in the 5th column, and Email Addresses will occur in column 6.

  If the column number of a field is not set in the Field Order Number field of the integration mapping record, it will be placed after all columns for which a value is set.
  

• Set a Data Transformation Type for the Integration Mapping records.

  You can specify one of the following values in the Data Transformation Type field:

  • CONCATENATE
  • DATE
  • NUMBER
  • PREFIX
  • SUFFIX
  • SPLIT
  • REPLACE
  • STRING
  • OPTIONSET
  • MULTISELECTOPTIONSET
  • TWOOPTIONS

  For more information, see Data Transformation Types For Export.

Performing An Export Operation

1. Exporting will start on the next run of the flow Sample - FileExport – <External system name>, which is supported by the secondary flow Export - Entity Data.

   For example, Sample - FileExport – PeopleSoft.

2. By default, records of the following entities are exported at 12 hours UTC. An administrator can change this setting.
   • Application
   • Application Requirement
   • Previous Education
   • Test Score

   The administrator can change these settings and also run the flow manually.

   In addition, records of entities related to the above entities on the one side will also be exported. For example, multiple applications that are all related to a specific contact have a many-to-one relationship. In such scenarios, the contact records will also be exported.

3. On the next run of the flows:
   • The source files will be automatically placed in the path common\outbound\<External system name>-export in Microsoft Azure.
   • Four files, each with records of the following entities (and their related records) will be exported:

     Entity	Name of Exported File
     Application	<External system name>-ApplicantData.<xlsx or csv> (e.g. PeopleSoft-ApplicantData.<xlsx or csv>)
     Application Requirement	<External system name>-ApplicationRequirement. <xlsx or csv> (e.g. PeopleSoft-ApplicationRequirement. <xlsx or csv>)
     Previous Education	<External system name>-PreviousEducationData. <xlsx or csv> (e.g. PeopleSoft-PreviousEducationData. <xlsx or csv>)
     Test Score	<External system name>-TestScoreData. <xlsx or csv> (e.g. PeopleSoft-TestScoreData. <xlsx or csv>)