Skip to content

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.

AttributesIdentity_Import Table MappingDescription
Identification_IDAn incrementally generated number automatically created by RAC/M.
First_NameFirst_NameThe first name of the identity.
Last_NameLast_NameThe last name of the identity.
Middle_NameMiddle_NameThe additional name.
EmailEmailThe email address of the identity.
Employee_IDEmployee_IDThe human resources identifier of the employee.
Cost_CenterCost_CenterThe cost center of the employee.
Jobs_IDHR_Jobs_IDA key referencing the Jobs table, which contains all jobs in the organization (e.g., administrator, secretary, doctor, student, etc.).
Employment_Status_IDHR_Empl_Status_IDA key linked to the Employment_Status table, which contains all employment statuses of the organization (e.g., active, retired, sick leave, etc.).
Employment_Type_IDHR_Empl_Type_IDA key linked to the Employment_Type table, which contains all employment types in the organization (e.g., permanent, contractual, intern, etc.).
Identifier 1 to 6Identifier 1 to 6A key used to identify an entity using a unique key or name. (Note: Identifiers 1 and 2 are indexed to speed up the search.)
AddressAddressThe civic address of the identity's workplace.
Phone_NumberPhone_NumberThe professional phone number.
Hire_DateHire_DateThe hire date of the identity.
Termination_DateTermination_Date_StrThe employment end date when this identity will be marked as inactive.
HR_Supervisor_Employee_IDHR_Supervisor_Employee_IDThe human resources identifier of this identity's supervisor.
Supervisor_IDHR_Supervisor_Employee_IDA key linked to the Identification table to resolve the reference.
HR_Reviewer_IDHR_Reviewer_IDThe human resources identifier of this identity's reviewer (e.g., supervisor).
Reviewer_IDHR_Reviewer_IDA key linked to another identity and used in review campaigns to determine who will review this identity.
HR_Department_IDHR_Department_IDThe human resources identifier of the department.
Department_IDHR_Department_IDA key referencing the Structural table to resolve the reference.
HR_Organisation_IDHR_Organisation_IDThe human resources identifier of the organization.
Organisation_IDHR_Organisation_IDA key referencing the Structural table to resolve the reference.
Work_Location_IDHR_Work_Location_IDA key linked to the Work_Location table to resolve the reference.
HR_File_Source_IDHR_File_Source_IDThe identifier of the ICF or file used in the collector. (A default value is used if unspecified.)
File_Source_IDHR_File_Source_IDA key linked to the File_Source table to resolve the reference. It allows identifying all the different sources used to create identities.
Birth_DateBirth_Date_StrThe birth date of the person associated with the identity.
CountryCountryThe country of the identity's workplace.
OccupationOccupationSpecialization associated with the identity.
Extra 1 to 50Extra 1 to 50Additional relevant information. (Note: Not all have the same available capacity.)
Primary_AccountPrimary_AccountIdentifies the primary account naming convention. (Note: Often the AD account, used for correlation and provisioning.)
Secondary_AccountSecondary_AccountIdentifies the secondary account naming convention. (Note: Often the high-privilege AD account, used for correlation and provisioning
Tertiary_AccountTertiary_AccountIdentifies the tertiary account naming convention.
Quaternary_AccountQuaternary_AccountIdentifies the quaternary account naming convention.
Quinary_AccountQuinary_AccountIdentifies 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.

AttributesStructural_Import Table MappingDescription
Structural_IDHR_Structural_IDAn incrementally generated number automatically created by RAC/M.
HR_Structural_IDStructural_Import_IDThis key identifies the human resources structure.
NameNameThe name of the structural element.
Organisation_Type_IDOrg_TypeThe type of structural element (Enterprise, Department, or Organization).
Manager_IdHR_Manager_IdThis key is linked to the Identification table to resolve the reference.
HR_Manager_IdHR_Manager_IdThe ID of the manager responsible for this structural element.
HR_Manager_NameHR_Manager_NameThe full name of the manager.
Work_Location_IDHR_Work_Location_IDThis key is linked to the Work_Location table to resolve the reference. The ID of the work location.
Cost_CenterCost_CenterThe 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.

AttributesStructural_Import Table MappingDescription
Structural_IdHR_Structural_IdThis key, which identifies the human resources structure, references the Structural table to resolve the reference.
Superior_Structure_IdHR_Structural_Superior_IdThis 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.

AttributesApplication_Account_Import Table MappingDescription
Application_IDAn incrementally generated number automatically created by RAC/M.
Application_IDEXT_Application_IdThis key is linked to the Application table to resolve the reference.
Application_NameApplication_NameThe name of the asset.
Application_Group_IdEXT_Appl_Group_IdThis key references the ApplicationGroup table to resolve the reference.
System_TypeSystem_TypeInformation about the system type of this asset.
OSOSInformation about the OS type of this asset.
Application_Status_IdApplication_StatusThis key is linked to the ApplicationStatus table to resolve the reference.
EXT_Application_ID_TextNot 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.

AttributesApplication_Import Table MappingDescription
Application_IDAn incrementally generated number automatically created by RAC/M.
Application_IDEXT_Application_IdThis key is linked to the Application table to resolve the reference.
Application_NameApplication_NameThe name of the asset.
Application_DescriptionApplication_DescThe description of the asset.
Application_Group_IdEXT_Appl_Group_IdThis key references the ApplicationGroup table to resolve the reference.
System_TypeSystem_TypeInformation about the system type of this asset. (Notes: Informational only.)
OSOSInformation about the OS type of this asset. (Notes: Informational only.)
CountryCountryThe country where the asset is hosted. (Notes: Informational only.)
DNDNDN (Notes: Informational only.)
Application_Status_IdApplication_StatusThis key is linked to the ApplicationStatus table to resolve the reference.
Identifier 1 to 2Identifier 1 & 2Custom identifiers that can be used to complete external key fields.
Extra 1Extra 1Additional relevant information.
EXT_Application_ID_TextNot 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.

AttributesApplication_Account_Import Table MappingDescription
Status_IDAn incrementally generated number automatically created by RAC/M.
NameStatusThis 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.

AttributesApplication_Account_Import Table MappingDescription
Application_Account_IDAn incrementally generated number automatically created by RAC/M.
Application_IDEXT_Application_IdThis key is linked to the Application table to resolve the reference.
Account_NameAccount_NameThe name of the account.
DescriptionDescriptionThe description of the account.
First_NameFirst_NameThe first name associated with the account.
Last_NameLast_NameThe last name associated with the account.
Middle_NameMiddle_NameThe additional name associated with the account.
Full_NameFull_NameThe full name associated with the account.
EmailEmailThe email address associated with the account.
EINEINExternal key (Note: Not indexed, not recommended for use).
GUIDGUIDExternal key (Note: Used by Active Directory, LDAP).
DNDNInformation about the DN (Note: Used by Active Directory, LDAP).
Application_Group_IdEXT_Appl_Group_IdThis key references the ApplicationGroup table to resolve the reference.
HR_File_Source_IDHR_File_Source_IDThe identifier of the ICF or file used in the collector. (A default value is used if not specified.)
Expiration_DateExpiration_Date_StrThe expiration date of the account.
Last_Login_DateLast_Login_Date_StrThe last login date for the account.
Status_IDStatusThis key is linked to the Status table to resolve the reference.
Identifier 1 to 5Identifier 1 & 5Custom identifiers that can be used to complete external key fields. (Note: Identifiers 1 and 2 are indexed to speed up search.)
PasswordPasswordThe password associated with this account.
Password_Exp_DatePassword_Exp_DateThe expiration date of this password.
Sync_StatusNot use (Note: Used for provisioning; by default, it is undefined.)
Extra 1 to 40Extra 1 to 40Additional 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.

AttributesProfile_Import Table MappingDescription
Profil_IDAn incrementally generated number automatically created by RAC/M.
Profil_NameProfil_NameThe name of the profile refers to group names in the imported data.
Profil_DescriptionDescriptionThe description of the profile.
Application_IDEXT_Application_IdThis key is linked to the Application table to resolve the reference.
EXT_Profile_IDEXT_Profile_IDUnique identifier of the profile for an asset (e.g., GUID, ID).
Identifier 1 to 5Identifier 1 & 5Custom identifiers that can be used to complete external key fields. (Note: Identifiers 1 and 2 are indexed to speed up search.)
Sync_StatusNot use (Note: Used for provisioning; by default, it is undefined.)
Extra 1 to 20Extra 1 to 20Additional relevant information. (Note: They do not all have the same available capacity.)
EXT_Application_ID_TextNot use This was for IDs that were too long (Note: This is a relic of the past).
EXT_Profile_Application_IDNot use This was to import logical profiles (Note: This is a relic of the past).
EXT_Profile_ID_TextNot use This was for IDs that were too long (Note: This is a relic of the past).
EXT_Profile_Application_ID_TextNot 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_StrNot use (Note: Not yet implemented.)
Start_Date_App_Profile_StrNot 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.

AttributesProfile_Import Table MappingDescription
Profile_IDAn incrementally generated number automatically created by RAC/M.
Application_IdEXT_Application_IdThis key is linked to the Application table to resolve the reference.
Profile_IdEXT_Profile_IDThis key is linked to the Profile table to resolve the reference.
Application_Account_IdAccount_NameThis 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.

AttributesDescription
OrderThe order in which the questions are displayed (smallest first).
RequiredIndicates if the question is mandatory.
Add_Question_In_Written_RequestSpecifies 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".
TypeThe type of question. Supported types are: SELECT, INPUT, TEXTAREA. See the section below.
PageThe page where the question is used. Supported pages are: TERMINATION_IDENTITY, TERMINATION_EXTERNAL_IDENTITY.
Title_ENThe title of the question in English.
Title_FRThe title of the question in French.
Placeholder_ENThe placeholder to be used in English. Leave empty if none is required.
Placeholder_FRThe placeholder to be used in French. Leave empty if none is required.
Tooltip_ENThe tooltip to use in English. Leave empty if none is required.
Tooltip_FRThe 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.

AttributesDescription
Self_Service_Question_IdThe identifier of the question for this choice.
Label_ENThe text of the choice in English.
Label_FRThe text of the choice in French.