These two processes are client-specific in the sense that the data provided in the source file must match the standards of PSI as this data is manipulated or used to derive column values that can be imported correctly into an ePersonality system. Specifically, candidate codes less than seven digits are left-padded with zeroes to ensure that candidate codes to be loaded are exactly seven digits. This feature will be made more general in the near future so that other clients may use this.
For more information on loading the file from PSI please review the LRCAPSI - Load Candidate Information.
Before the XRAPPSI can be run there are site preferences that must be defined. Within the IMST screen, the administrator must define where the Extract and Load files are located and where the load functions are to write the exception files to. These locations are used by the functions to create and retrieve information. The customer can modify these values to represent any directory on their system.
The extract directory is defined using the EXTRCT DATA FLDR preference. The load directory is defined using the LOAD DATA FLDR preference. The ATTACHMENTS FLDR must be specified so the load functions know where to write the report exceptions log to.
Once the XRAPPSI function has been run, it will have created an .xml and .data file, it is suggested that the user reviews the .xml file to ensure the correct data was extracted.
Report Parameters | |
---|---|
User Comment | The user may opt to provide a comment on the output report generated. |
Report Filters | |
---|---|
Candidate Status | The user may filter the data to specific candidate statuses. |
Application Status | The list of candidates may be filtered down to specific application statuses. |
Entity | The user may filter the data to a specific entity. |
Location | The user may filter the data to candidates within a specific location. |
Department | The list of candidates may be filtered down to those within a specific department. |
Screen captures are meant to be indicative of the concept being presented and may not reflect the current screen design.
If you have any comments or questions please email the Wiki Editor
All content © High Line Corporation