Public

This article explains the methods of how to transfer data from HR Information Systems (such as SAP, Oracle, Workday, Unit4, Banner, and PeopleSoft) to the PageUp system.

The following are the ways data can be sent into PageUp:

• Using PageUp's API
• Using flat files

Using PageUp's API

PageUp APIs offer an effective and secure means of transmitting data. These APIs are designed with security in mind, ensuring that sensitive information can be shared without compromising its integrity or confidentiality. This makes them an excellent choice for organizations that prioritize data security.

With the API, you can manage data efficiently. You can create new entries to keep information current, update existing data to reflect the latest changes, and archive outdated information, ensuring effective data management.

Data is sent to PageUp in a JSON format using the attributes listed on the Developer Portal. Also, refer to API integration for further details.

Contact PageUp to discuss this option further.

Using flat files

Flat files cater to batches of export operations and process the contents of the files on a scheduled basis, and batch inserts or updates the information.

Data is formatted in delimited files and securely sent to a PageUp sFTP server for retrieval by a data importer. For more information, refer to Inbound file data formats.

The importer parses the contents of the files and adds new information to the system or updates existing information. Data that does not appear in the files but which exists in the PageUp is archived.

Recommendations

For a full list of files and their relevant fields that the PageUp system can process, refer to the Inbound data formats. To get the most value out of the system while keeping the integration streamlined, the following files are recommended:

• User file
• Position file
• Business unit files (1 to 4)
• Cost centre
• Site.

This list is intended as a guide only. Refer to the Inbound data formats or contact your PageUp representative to discuss further.

Importer configuration

It is possible to create and edit importer schedules and import files from within PageUp. This functionality can be accessed in System settings via the Integration menu, then clicking on Import Configuration.

Contact PageUp for clarification if you're uncertain about any information in this article. These processes carry a high risk to your data, and incorrect configuration may lead to issues, such as an incorrect User file blocking all users from accessing PageUp properly.

These sample files illustrate the required format for data in the flat file to be sent to PageUp for processing. Right-click and select "Save link as":

The information must be structured into a flat file using one of the following supported file formats:

• *.CSV (pipe/comma delimited)
• *.TXT (pipe/comma delimited)

Interface details

The following section details the requirements for the data files passed to the PageUp system.

Rules and requirements for flat files

• Data files are to be created as flat files.
• Data within the text files is to be either pipe (|) or comma (,) delimited.
• Data files will be archived and retained for a maximum of 45 days post-processing.
• PageUp will report on any processing exceptions.
• Importer issues will be prioritized from a support perspective.
• Data files should maintain a consistent naming convention and include the file date as part of the file name, e.g., User-20130920.txt
• The user and position need to have a 1:1 relationship.
• Information in each data file will be matched to the appropriate item in the PageUp system based on the "Number" column.
• Each data file should contain a listing of all records that should be active within the PageUp system.
  • Delta files are not supported.
• Items included in the data file that do not exist in the PageUp system will be created.
• Items existing in both the data file and in the PageUp system will be updated from the data file.
• Items existing in the PageUp system that are not included in the data file will be archived. The data remains archived and is retained for historical and reporting purposes.