Objects and Database Tables
Data Tables
While you must manually map data between data sources and staging tables, the process of copying data from staging tables to the repository is performed automatically. Although you primarily work with staging tables initially, it can be helpful to know where the data is stored in case you want to view the internal tables.
The main tables in the RAC/M identity and access repository that correspond to the "_Import" tables described above are as follows:
- Identification (Identity_Import)
- Structural (Structural_Import)
- Hierarchy (Structural_Import)
- Status (Application_Account_Import)
- Application_Account (Application_Account_Import)
- Application (Application_Account_Import)
- Application (Application_Import)
- Profile (Profile_Import)
- ApplicationProfile (Profile_Import)
Below is a description of the main tables that correspond to the import tables.
The Identification Table
The Identification table is where all data from the Identity_Import table is loaded.
Data is imported into this table using the IdentificationCopy module (see Module Configuration).
Note
RAC/M Identity allows you to normalize and enhance data to improve matching performance using primitives such as the ModulePermutation primitive used in the NormalizerIdentification module.
When importing identities into the Identification table, the first and last names will be copied into the Normalization_Identification table. In this table, all special characters will be removed, and all permutations of the full name will be generated. For example, a person with the full name "André Gagné-Lajoie" will also be registered under the following variations: AndreGagne, AndreGagneLajoie, AndreLajoie, AndreLajoieGagne, GagneAndre, GagneAndreLajoie, GagneLajoie, GagneLajoieAndre, LajoieAndre, LajoieAndreGagne, LajoieGagne, or LajoieGagneAndre. A soundex will also be associated with each name entered in the normalization table.
This ensures that if any of the identities created in an identity source use one of these spelling variants, the RAC/M module will still be able to match that identity to the person. This process is particularly useful in name correlation modules and on the manual account-to-identity association page.
The main attributes are listed in the table below. The most important ones are in bold. In most cases, the attributes of the Identification table correspond exactly to the attributes of the Identity_Import table.
Attributes | Identity_Import Table Mapping | Description |
---|---|---|
Identification_ID | An incrementally generated number automatically created by RAC/M. | |
First_Name | First_Name | The first name of the identity. |
Last_Name | Last_Name | The last name of the identity. |
Middle_Name | Middle_Name | The additional name. |
The email address of the identity. | ||
Employee_ID | Employee_ID | The human resources identifier of the employee. |
Cost_Center | Cost_Center | The cost center of the employee. |
Jobs_ID | HR_Jobs_ID | A key referencing the Jobs table, which contains all jobs in the organization (e.g., administrator, secretary, doctor, student, etc.). |
Employment_Status_ID | HR_Empl_Status_ID | A key linked to the Employment_Status table, which contains all employment statuses of the organization (e.g., active, retired, sick leave, etc.). |
Employment_Type_ID | HR_Empl_Type_ID | A key linked to the Employment_Type table, which contains all employment types in the organization (e.g., permanent, contractual, intern, etc.). |
Identifier 1 to 6 | Identifier 1 to 6 | A key used to identify an entity using a unique key or name. (Note: Identifiers 1 and 2 are indexed to speed up the search.) |
Address | Address | The civic address of the identity's workplace. |
Phone_Number | Phone_Number | The professional phone number. |
Hire_Date | Hire_Date | The hire date of the identity. |
Termination_Date | Termination_Date_Str | The employment end date when this identity will be marked as inactive. |
HR_Supervisor_Employee_ID | HR_Supervisor_Employee_ID | The human resources identifier of this identity's supervisor. |
Supervisor_ID | HR_Supervisor_Employee_ID | A key linked to the Identification table to resolve the reference. |
HR_Reviewer_ID | HR_Reviewer_ID | The human resources identifier of this identity's reviewer (e.g., supervisor). |
Reviewer_ID | HR_Reviewer_ID | A key linked to another identity and used in review campaigns to determine who will review this identity. |
HR_Department_ID | HR_Department_ID | The human resources identifier of the department. |
Department_ID | HR_Department_ID | A key referencing the Structural table to resolve the reference. |
HR_Organisation_ID | HR_Organisation_ID | The human resources identifier of the organization. |
Organisation_ID | HR_Organisation_ID | A key referencing the Structural table to resolve the reference. |
Work_Location_ID | HR_Work_Location_ID | A key linked to the Work_Location table to resolve the reference. |
HR_File_Source_ID | HR_File_Source_ID | The identifier of the ICF or file used in the collector. (A default value is used if unspecified.) |
File_Source_ID | HR_File_Source_ID | A key linked to the File_Source table to resolve the reference. It allows identifying all the different sources used to create identities. |
Birth_Date | Birth_Date_Str | The birth date of the person associated with the identity. |
Country | Country | The country of the identity's workplace. |
Occupation | Occupation | Specialization associated with the identity. |
Extra 1 to 50 | Extra 1 to 50 | Additional relevant information. (Note: Not all have the same available capacity.) |
Primary_Account | Primary_Account | Identifies the primary account naming convention. (Note: Often the AD account, used for correlation and provisioning.) |
Secondary_Account | Secondary_Account | Identifies the secondary account naming convention. (Note: Often the high-privilege AD account, used for correlation and provisioning |
Tertiary_Account | Tertiary_Account | Identifies the tertiary account naming convention. |
Quaternary_Account | Quaternary_Account | Identifies the quaternary account naming convention. |
Quinary_Account | Quinary_Account | Identifies the quinary account naming convention. |
The Structural Table
The Structural table is where all data from the Structural_Import table is loaded.
Data is imported into this table using the StructuralCopy module (see Module Configuration).
The main attributes are listed in the table below. The most important ones are in bold. In most cases, the attributes of the Structural table correspond exactly to the attributes of the Structural_Import table.
Attributes | Structural_Import Table Mapping | Description |
---|---|---|
Structural_ID | HR_Structural_ID | An incrementally generated number automatically created by RAC/M. |
HR_Structural_ID | Structural_Import_ID | This key identifies the human resources structure. |
Name | Name | The name of the structural element. |
Organisation_Type_ID | Org_Type | The type of structural element (Enterprise, Department, or Organization). |
Manager_Id | HR_Manager_Id | This key is linked to the Identification table to resolve the reference. |
HR_Manager_Id | HR_Manager_Id | The ID of the manager responsible for this structural element. |
HR_Manager_Name | HR_Manager_Name | The full name of the manager. |
Work_Location_ID | HR_Work_Location_ID | This key is linked to the Work_Location table to resolve the reference. The ID of the work location. |
Cost_Center | Cost_Center | The cost center of this structural element. |
The Hierarchy Table
The Hierarchy table is where data from the Structural_Import table is loaded.
Data is imported into this table using the Hierarchy module (see Module Configuration).
The main attributes are listed in the table below. The most important ones are in bold. In most cases, the attributes of the Hierarchy table correspond exactly to the attributes of the Structural_Import table.
Attributes | Structural_Import Table Mapping | Description |
---|---|---|
Structural_Id | HR_Structural_Id | This key, which identifies the human resources structure, references the Structural table to resolve the reference. |
Superior_Structure_Id | HR_Structural_Superior_Id | This key, which identifies the superior human resources structure, references the Structural table to resolve the reference. |
The Application Table
The Application table is where some data from the Application_Account_Import table is imported.
Data is imported into this table using the Application module (see Module Configuration).
The main attributes are listed in the table below. The most important ones are in bold. In most cases, the attributes of the Application table correspond to certain attributes of the Application_Account_Import table.
Attributes | Application_Account_Import Table Mapping | Description |
---|---|---|
Application_ID | An incrementally generated number automatically created by RAC/M. | |
Application_ID | EXT_Application_Id | This key is linked to the Application table to resolve the reference. |
Application_Name | Application_Name | The name of the asset. |
Application_Group_Id | EXT_Appl_Group_Id | This key references the ApplicationGroup table to resolve the reference. |
System_Type | System_Type | Information about the system type of this asset. |
OS | OS | Information about the OS type of this asset. |
Application_Status_Id | Application_Status | This key is linked to the ApplicationStatus table to resolve the reference. |
EXT_Application_ID_Text | Not use This was for IDs that were too long (Note: This is a relic of the past). |
The Application table is also where some data from the Application_Import table is imported.
Note
This table association represents essentially the same as the table above, but the information comes from another source. This manipulation is rare unless different information is to be loaded. It gives an example of the flexibility of these modules.
Attributes | Application_Import Table Mapping | Description |
---|---|---|
Application_ID | An incrementally generated number automatically created by RAC/M. | |
Application_ID | EXT_Application_Id | This key is linked to the Application table to resolve the reference. |
Application_Name | Application_Name | The name of the asset. |
Application_Description | Application_Desc | The description of the asset. |
Application_Group_Id | EXT_Appl_Group_Id | This key references the ApplicationGroup table to resolve the reference. |
System_Type | System_Type | Information about the system type of this asset. (Notes: Informational only.) |
OS | OS | Information about the OS type of this asset. (Notes: Informational only.) |
Country | Country | The country where the asset is hosted. (Notes: Informational only.) |
DN | DN | DN (Notes: Informational only.) |
Application_Status_Id | Application_Status | This key is linked to the ApplicationStatus table to resolve the reference. |
Identifier 1 to 2 | Identifier 1 & 2 | Custom identifiers that can be used to complete external key fields. |
Extra 1 | Extra 1 | Additional relevant information. |
EXT_Application_ID_Text | Not use This was for IDs that were too long (Note: This is a relic of the past). |
The Status Table
The Status table is where data from the Application_Account_Import table is imported.
Data is imported into this table using the Status module (see Module Configuration).
The main attributes are listed in the table below. The most important ones are in bold. In most cases, the attributes of the Status table correspond exactly to the attributes of the Application_Account_Import table.
Note
When new statuses are added, their actual state (Active, Terminated, Inactive) must be defined.
Attributes | Application_Account_Import Table Mapping | Description |
---|---|---|
Status_ID | An incrementally generated number automatically created by RAC/M. | |
Name | Status | This key is linked to the Status table to resolve the reference. |
The Application_Account Table
The Application_Account table is where all data from the Application_Account_Import table is imported.
Data is imported into this table using the ApplicationAccount module (see Module Configuration).
Note
RAC/M Identity allows you to normalize and improve data to enhance matching performance using primitives such as the ModulePermutation primitive used in the NormalizerApplicationAccount module.
When importing accounts into the ApplicationAccount table, the first and last names will be copied into the Normalization_ApplicationAccount table.
The main attributes are listed in the table below. The most important ones are in bold. In most cases, the attributes of the Application_Account table correspond exactly to the attributes of the Application_Account_Import table.
Attributes | Application_Account_Import Table Mapping | Description |
---|---|---|
Application_Account_ID | An incrementally generated number automatically created by RAC/M. | |
Application_ID | EXT_Application_Id | This key is linked to the Application table to resolve the reference. |
Account_Name | Account_Name | The name of the account. |
Description | Description | The description of the account. |
First_Name | First_Name | The first name associated with the account. |
Last_Name | Last_Name | The last name associated with the account. |
Middle_Name | Middle_Name | The additional name associated with the account. |
Full_Name | Full_Name | The full name associated with the account. |
The email address associated with the account. | ||
EIN | EIN | External key (Note: Not indexed, not recommended for use). |
GUID | GUID | External key (Note: Used by Active Directory, LDAP). |
DN | DN | Information about the DN (Note: Used by Active Directory, LDAP). |
Application_Group_Id | EXT_Appl_Group_Id | This key references the ApplicationGroup table to resolve the reference. |
HR_File_Source_ID | HR_File_Source_ID | The identifier of the ICF or file used in the collector. (A default value is used if not specified.) |
Expiration_Date | Expiration_Date_Str | The expiration date of the account. |
Last_Login_Date | Last_Login_Date_Str | The last login date for the account. |
Status_ID | Status | This key is linked to the Status table to resolve the reference. |
Identifier 1 to 5 | Identifier 1 & 5 | Custom identifiers that can be used to complete external key fields. (Note: Identifiers 1 and 2 are indexed to speed up search.) |
Password | Password | The password associated with this account. |
Password_Exp_Date | Password_Exp_Date | The expiration date of this password. |
Sync_Status | Not use (Note: Used for provisioning; by default, it is undefined.) | |
Extra 1 to 40 | Extra 1 to 40 | Additional relevant information. (Note: They do not all have the same available capacity.) |
The Profile Table
The Profile table is where all data from the Profile_Import table is loaded.
Data is loaded into this table using the Profile module (see Module Configuration).
The main attributes are listed in the table below. The most important ones are in bold. In most cases, the attributes of the Profile table correspond exactly to the attributes of the Profile_Import table.
Attributes | Profile_Import Table Mapping | Description |
---|---|---|
Profil_ID | An incrementally generated number automatically created by RAC/M. | |
Profil_Name | Profil_Name | The name of the profile refers to group names in the imported data. |
Profil_Description | Description | The description of the profile. |
Application_ID | EXT_Application_Id | This key is linked to the Application table to resolve the reference. |
EXT_Profile_ID | EXT_Profile_ID | Unique identifier of the profile for an asset (e.g., GUID, ID). |
Identifier 1 to 5 | Identifier 1 & 5 | Custom identifiers that can be used to complete external key fields. (Note: Identifiers 1 and 2 are indexed to speed up search.) |
Sync_Status | Not use (Note: Used for provisioning; by default, it is undefined.) | |
Extra 1 to 20 | Extra 1 to 20 | Additional relevant information. (Note: They do not all have the same available capacity.) |
EXT_Application_ID_Text | Not use This was for IDs that were too long (Note: This is a relic of the past). | |
EXT_Profile_Application_ID | Not use This was to import logical profiles (Note: This is a relic of the past). | |
EXT_Profile_ID_Text | Not use This was for IDs that were too long (Note: This is a relic of the past). | |
EXT_Profile_Application_ID_Text | Not use This was for IDs that were too long to import logical profiles (Note: This is a relic of the past). | |
End_Date_App_Profile_Str | Not use (Note: Not yet implemented.) | |
Start_Date_App_Profile_Str | Not use (Note: Not yet implemented.) |
The ApplicationProfile Table
The ApplicationProfile table is where members from the Profile_Import table are loaded.
Data is loaded into this table using the ApplicationProfile module (see Module Configuration).
The main attributes are listed in the table below, but only the information defining a member of an account for an asset listed in the Profile_Import table is required.
Attributes | Profile_Import Table Mapping | Description |
---|---|---|
Profile_ID | An incrementally generated number automatically created by RAC/M. | |
Application_Id | EXT_Application_Id | This key is linked to the Application table to resolve the reference. |
Profile_Id | EXT_Profile_ID | This key is linked to the Profile table to resolve the reference. |
Application_Account_Id | Account_Name | This key is linked to the ApplicationAccount table to resolve the reference. |
Configuration Tables
The SELF_SERVICE_QUESTION Table
The SELF_SERVICE_QUESTION table is where questions to be used in various self-service pages are configured.
The main attributes are listed in the table below. The most important ones are in bold.
Attributes | Description |
---|---|
Order | The order in which the questions are displayed (smallest first). |
Required | Indicates if the question is mandatory. |
Add_Question_In_Written_Request | Specifies if the question is included in the written request or just the answer when the question is used as part of a written request. Example with the question: "My question: My answer" and without the question: "My answer". |
Type | The type of question. Supported types are: SELECT, INPUT, TEXTAREA. See the section below. |
Page | The page where the question is used. Supported pages are: TERMINATION_IDENTITY, TERMINATION_EXTERNAL_IDENTITY. |
Title_EN | The title of the question in English. |
Title_FR | The title of the question in French. |
Placeholder_EN | The placeholder to be used in English. Leave empty if none is required. |
Placeholder_FR | The placeholder to be used in French. Leave empty if none is required. |
Tooltip_EN | The tooltip to use in English. Leave empty if none is required. |
Tooltip_FR | The tooltip to use in French. Leave empty if none is required. |
Types of Questions
There are two supported modes for questions: free-text and multiple-choice.
Free Form Mode
The two types that can be used for this mode are:
- TEXTAREA: Allows the use of line breaks and is suitable for longer responses.
- INPUT: Does not allow line breaks and is generally used for short answers.
Multiple-Choice Mode
The only supported type for this mode is SELECT. This option forces the user to choose one response from the available choices. The possible choices for a question are configured via The SELF_SERVICE_QUESTION_CHOICE Table.
The SELF_SERVICE_QUESTION_CHOICE Table
The SELF_SERVICE_QUESTION_CHOICE table is where the response choices for multiple-choice questions are configured.
The main attributes are listed in the table below. The most important ones are in bold.
Attributes | Description |
---|---|
Self_Service_Question_Id | The identifier of the question for this choice. |
Label_EN | The text of the choice in English. |
Label_FR | The text of the choice in French. |