This article provides an overview of the process taken when PageUp receives or exports data from the system. Other methods of transferring data in or out of the PageUp system are also available. Discussions with your PageUp representative are recommended for best practices on a streamlined approach to integrating between PageUp and your IT systems.
What does an integration provide?
Setting up the integration between PageUp and your existing IT systems, for example, a Human Resource Information System (HRIS) like SAP, Oracle, Peoplesoft, Workday and Banner, will allow you to capture information in your IT system and transfer it into PageUp or vice versa.
Who do we currently integrate with?
To view a full list of our current integration partners/connections, visit our Marketplace.
- Information only needs to be entered once and can be used in multiple systems including PageUp.
- Identifies a single source of truth so that it is clear in which system the information is housed.
- The ability to send and receive information from and to your existing IT systems based on a real time or custom schedule.
The following technologies are supported by PageUp:
- Standard flat file(s) - inbound and outbound
- Web services - SOAP
- REST API
Supported file formats
- .CSV or .TXT file formats are supported for flat file integrations.
Refer to the links above for more information.
What does an HRIS integration consist of?
Integrations can be a one-way transfer of information either into (import/feed) or out of (export) PageUp, or you may elect to set up a two-way integration between PageUp and your IT system(s).
If you include a user feed (import of people) into PageUp, using Single Sign On is also recommended.
How does the Import process work?
Your system creates one or more flat file(s) containing information that is to be imported into PageUp. These file(s) are pushed to the PageUp FTP server in a variety of formats. We do not support pulling the file(s) from your FTP server.
For more information refer to SFTP specifications.
The PageUp Generic Importer pulls the file(s) from the FTP server. It validates that the files are complete, and converts the file(s) to a standard XML format.
The PageUp PUP Importer then takes the standard XML and performs updates to the database.
The PUP Importer works on the following rules:
- If a new item is in the file, it is added to the database
- If an item is updated in the file, it is updated in the database
- If an item is in the database, but not in the file, it is archived in the database
Support model for Import
PageUp offers a number of monitoring and support services above the primary sFTP error handling that will occur during the transfer of files to PageUp.
Beyond the physical transfer of files via sFTP, errors can arise during the processing of the file content itself. This may be due to file corruption, or incomplete/incorrectly formatted files. PageUp provides ongoing monitoring of inbound sFTP files, specifically in the identification of:
- Failed inbound sFTP imports due to the corruption of file format/content
These monitoring alerts contain full stack traces of the subsequent errors. In all cases, a support ticket will be raised in accordance with the error and actioned in alignment with PageUp's SLA and KPI agreements. PageUp support is equipped with a number of tools to diagnose and reprocess files where possible. In addition to this, the PageUp application layer is equipped with a retry mechanism to mitigate the number of intermittent processing failures that require manual intervention. Currently, based on the nature of the import error the PageUp system may automatically attempt to reprocess the files up to 5 times.
How does the Export process work?
There are two key processes running at PageUp. These are known as the scheduler process, and the exporter process.
The scheduler process wakes up and runs once an hour, checks if there are any exports that are due to be run, adds them to a work queue, and then goes back to sleep.
The exporter process runs all the time. It picks up items off the queue, creates an export file, and then picks the next item on the queue. It can produce a simple "flat" file, an MS Access database, or a "File-per-Record" stream.
Once the file is created, it is transferred to your systems via FTP (File Transfer Protocol) or by e-mail. FTP is used much more widely than e-mail.
There are two ways that FTP can be used.
Firstly, PageUp can push the file to our own FTP server, from where you can download or pull the file to your own FTP server. The URL of our FTP server can be found here, a valid login will also be required.
Secondly, PageUp can push the file to your FTP server, from where you can process it directly. To set up this method, PageUp will require the IP address of your FTP server, a login account to use and a valid password.
Support model for Export
PageUp offers a number of monitoring and support services to handle any errors that arise during the process of producing and sending files via sFTP to clients' HRIS systems. PageUp provides ongoing monitoring of outbound sFTP files, specifically in the identification of:
- Failures to access the required export data from the PageUp system
- Failure to produce the physical files to transfer via sFTP
- Failures in the physical sending of files via sFTP.
These monitoring alerts contain full stack traces of the subsequent errors. In all cases, a support ticket will be raised in accordance with the error and actioned in alignment with PageUp's SLA and KPI agreements. PageUp support is equipped with a number of tools to diagnose and reprocess files where possible. Also, the PageUp application layer is equipped with a retry mechanism to mitigate the number of intermittent processing failures that require manual intervention. Currently, based on the nature of the outbound export error the PageUp system may automatically attempt to reprocess the files up to 5 times.
In addition to these processes, clients can be notified directly of outbound sFTP by providing an email address that will be alerted upon the failure of the outbound transfer.
What can you do to help?
Integrations usually involve technical conversations to ensure the correct information is transferred into and out of PageUp. Please ensure you have both a business and a technical representative available to attend the integration meetings as required. A technical review of the SFTP specifications prior to conversations with PageUp will accelerate the integration discussions.
Getting started with integrations
Other areas detailing integrations
Additional integration options
Downloadable PDF detailed specification documents.