Frontier chris21 Connector
A Frontier chris21 connector is a reading, writing, deleting and polling connector provided by UNIFYBroker/Frontier chris21.
This connector encapsulates the information of a single form in chris21 and is typically implemented multiple times to represent each form in a single chris21 instance.
The Frontier chris21 connector has no additional requirements following the listed connector prerequisites and setting up a Frontier chris21 agent.
A Frontier chris21 connector encapsulates the human resource data available at one form in a chris21 instance.
The connector utilizes the EAI mechanism in chris21 for detecting changes, which works essentially like a delta table in a database. As a result, the EAI entries for the form are cleared following each polling operation.
In order to delete an employee from chris21, the employee must have an active termination record.
Fields in a chris21 connector refer to individual fields in the target form of the same name.
The schema provider for this connector will retrieve all known form fields, mapping their types and read-only settings as present in chris21. Additionally, if the Show Translations setting is enabled on the connector, translation fields will also be available. A translation field is a lookup of a field that only has a code value, for example, the full name of a position as opposed to just its code.
A Frontier chris21 connector maintains the following configuration:
|Form||Data in chris21 is broken up into many 'forms'; these forms can manage different subsections of data like Person Details (DET), Terminations (TER), Address details (ADR) and so on.|
|File||Each form has a corresponding GTR file. This GTR file is a five letter code which is located on the system screen for the specified GTR form in the Frontier chris21 client application. e.g. Form - DET, File - EMDET. See Common GTR forms and their file tables.|
|Show Translations||Whether to include a series of additional 'translation' fields which are suffixed by a '.trn'. This is useful when a GTR form contains multiple code fields and descriptions are required. Using the True setting can decrease system performance due to the additional translations provided, especially when used with the gtrListRequest='All' setting. It is recommended that this setting is only changed if the retrieved information is not worthwhile for the solution, and if performance is significantly impacted in larger environments.|
|Request Type||The type of list request to perform on requests to the chris21 instance.|
|EAI Type||The method for handling EAI records once they have been processed. Delete: Issues a delete command for seen items. Flag: Flags a custom field to specify that the field has been processed - these records are later filtered out when requesting items from EAI.|
|Chunk Size||The chunk size to get when request data from chris21. A chunk is the number of records returned in a single GTR request. If the number of records for a connector exceed the number records requested then multiple GTR requests are made. This setting needs to be configured for each connector in each environment to achieve optimal performance.|
|Key Type||The key type to use for change polling. Full retrieves the full connector key and is suitable in most cases.|
|Data Threshold||The number of entities that will be read in an 'Import Changes' before a 'Import All' will be run instead.|
|Debug Mode||Whether or not debug mode is active for the connector. Debug mode results in all chris21 information being written to the log.|
|Attachment Extension||The file extension of default attachments to retrieve.|
|Filters||Defines a comma-separated collection of GTR filters for the connector. These filters enable the limiting of scope of particular entries, and are formatted as attribute:operator:value. For example, to filter the address form to only import home address data, the filter adrtype:EQ:H: can be added.|
Common GTR forms and files
|Relational information records||REL||PSLDW|
Customer support service by UserEcho