UNIFYBroker/Frontier chris21 Data Modelling

Overview

The following sections include the concepts required to understand UNIFYBroker’s connectivity to chris²¹ systems.

chris21 forms

A form in chris²¹ is comparable to a screen on the chris²¹ user interface.  Each form is customisable, although there are certain attributes that are common to all instances of chris²¹. 

Each form is accessible by UNIFYBroker by its three letter code designation.

UNIFYBroker and relationship between chris21 forms and a single connector

In order to allow the greatest flexibility of UNIFYBroker/Frontier chris²¹, each single connector in UNIFYBroker must correspond to a single form in chris²¹.  For example, a connector can be set up to correspond to the Staff Details (DET) form, enabling access to information about staff member’s details.

The fields within the described target form are denoted by individual schema fields on the connector of the same name. 

To provide information in the Identity Management de-normalised form, UNIFYBroker’s transformations can be utilized.  

Sample implementations of a chris²¹ solution can be found here

chris21 BRE

The Business Rules Engine (BRE) defines the rules and data which a chris²¹ instance uses to operate.  For a more detailed explanation of the BRE, refer to the Frontier technical documentation.

chris21 GTR

The General Transaction Record (GTR) is the language used to communicate with chris²¹’s Business Rules Engine.

UNIFYBroker uses this GTR to communicate with chris²¹. The GTR requests are constructed based on the schema and communicator configuration within the connector configuration.

chris21 scalability and Internet option

In order to gain the greatest isolation from chris²¹, which in some instances may actually be accessed over the internet, UNIFYBroker sends GTR requests to chris²¹ via a Frontier component called the “Internet Option”.  See the Frontier document Internet Option for an explanation of how to configure this.

Change Detection and EAI

Identity Broker uses the EAI mechanism within chris²¹ to import changes within the system. Once appropriately enabled for a form and its underlying file table, changes made in chris²¹ to each form will be logged to EAI. These changes are imported and cleared (or flagged for removal) during polling operations by the connector.

In order to prevent continual importing of the data in the target forms, the EAI table will be cleared of the entries relevant to the particular form following a successful import. Keep this in mind if any other systems depend on the EAI interface to function.

Export Considerations

The primary consideration for exports is to ensure all related information exists in the chris²¹ instance prior to the addition of new items. Most information in chris21 is reliant on the existence of a record in the Employee Details (DET) form. Without the employee record, information such as address, position, termination, or relational information will not correctly resolve in chris²¹.

Another note is that employees cannot be deleted unless they have an active termination record. In order to successfully delete a user from chris²¹, ensure a current termination record is present prior to the export.