Skip to content
On this page

Objects and Database Tables

Data Tables

While you have to manually map the data between the Data sources and the staging tables, the process to copy the data from the staging tables to the repository is carried out automatically. Although you will mainly be working with the staging tables at first, it might be useful to know where the data goes 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 desctibed above are:

  • Identification (Identity_Import)
  • Structural (Structural_Import)
  • Application_Account (Application_Account_Import)
  • Profile (Profile_Hierachy_Import)

The following is a description of the main tables that correspond to the staging tables.

The Identification table

The Identification table is the table into which all of the data from the Identity_Import table is loaded.

Data is imported into this table using the IdentificationCopy module (see Configuring a Module).

Note

RAC/M Identity enables you to normalize and enhance data to increase matching performance by 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 Normalize_Identification table, where any special character will be removed and up to 4 permutations of the full name will be created. Thus, a person whose full name is “André Gagné-Lajoie” would also be saved as “Andre Gagne”, “Andre Lajoie”, and “Andre Lajoie-Gagne”. This means that if any of the identities created in an identity source uses one of the alternate spellings, RAC/M will still be able to match the identity to the person.

The main attributes are listed in the table below. The most important ones are in bold. In most cases, the attributes in the Identification table correspond exactly to the attributes in the Identity_Import table.

AttributesIdentity_Import Table CorrespondenceDescription
Identification_IDThis is an incremental number automatically generated by RAC/M to identify the identities.
First_NameFirst_NameThe first name of the identity.
Last_NameLast_NameThe last name of the identity.
EmailEmailThe email of the identity.
Employee_IDEmployee_IDThe employee id of the identity.
Jobs_IDHR_Jobs_IDThis is a key that links to the Jobs table, which contains all of the organization’s jobs (for example, administrator, secretary, doctor, student, etc.).
Employment_Status_IDHR_Empl_Status_IDThis is a key that links to the Employment_Status table, which contains all of the organization’s employment statuses (for example, active, retired, sick leave, etc.).
Employment_Type_IDHR_Empl_Type_IDThis is a key that links to the Employment_Type table, which contains all of the organization’s employment types (for example, permanent, contractor, intern, etc.).
Termination_DateTermination_Date_StrThe termination date when this identity will be flagged as inactive.
HR_Supervisor_Employee_IDHR_Supervisor_Employee_IDThe supervisor id of this identity.
Reviewer_IDThis links to another identity and is used in review campaigns to determine who will review this identity.
Department_IDHR_Department_IDThis is a key that links to the Structural table. It retrieves the primary key number lined to the HR_Department_ID attribute.
HR_Department_IDHR_Department_IDThis is a key that links to the Structural table. It retrieves the value located in the HR_Department_ID attribute.
Organization_IDHR_Organisation_IDThis is a key that links to the Structural table. It retrieves the primary key number lined to the HR_ Organisation_ID attribute.
HR_Organization_IDHR_Organisation_IDThis is a key that links to the Structural table. It retrieves the value located in the HR_ Organisation_ID attribute.
Work_Location_IDHR_Work_Location_IDThis is a key that links to the Structural table. It indicates all of your organization’s work locations.
File_Source_IDHR_File_Source_IDThis is a key that links to the File_Source table. It enables you to identify all of the different identity sources used to create identities.
Birth_DateBirth_Date_StrThe birth date of the identity’s associated person.

The Structural table

The Structural table is the table into which all of the data from the Structural_Import table is loaded.

Data is imported into this table using the StructuralCopy module (see Configuring a Module).

The main attributes are listed in the table below. The most important ones are in bold. In most cases, the attributes in the Structural table correspond exactly to the attributes in the Structural_Import table.

AttributesStructural_Import Table CorrespondenceDescription
Structural_IDThis is an incremental number automatically generated by RAC/M to identify the structural elements.
HR_Structural_IDStructural_Import_IDThe ID of the structural element.
NameNameThe name of the structural element.
Organisation_Type_IDOrg_TypeThe type of structural element, an organization or department.
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_IDThe ID of the work location.

The Application_Account table

The Application_Account table is the table into which all of the data from the Application_Account_Import table is imported.

Data is imported into this table using the ApplicationAccount module (see Configuring a Module).

The main attributes are listed in the table below. The most important ones are in bold. In most cases, the attributes in the Application_Account table correspond exactly to the attributes in the Application_Account_Import table.

AttributesApplication_Account_Import Table CorrespondenDescription
Application_Account_IDThis is an incremental number automatically generated by RAC/M to identify the accounts.
Application_IDApplication_NameThe ID of the application which is derived from the name of the application in the import data.
Account_NameAccount_NameThe name of the application account
Status_IDStatusThe status ID of the application account derived from the status of the import data.
Identifier 1 & 2Identifier 1 & 2Custom identifiers that may be used to complement the standard fields.
HR_File_Source_IDHR_File_Source_IDThe ID of the file source which was the origin of this import data.
Expiration_DateExpiration_Date_StrThe expiration date of the application account
PasswordPasswordThe password associated to this application account.
Password_Exp_DatePassword_Exp_DateThe expiration date of this password

The Profile table

The Profile table is the table into which all of the data from the Profile_Import table is loaded.

Data is loaded into this table using the Profile module (see Configuring a Module).

The main attributes are listed in the table below. The most important ones are in bold. In most cases, the attributes in the Profile table correspond exactly to the attributes in the Profile_Import table.

AttributesStructural_Import Table CorrespondenceDescription
Profile_IDThis is an incremental number automatically generated by RAC/M to identify the structural elements.
Profile_NameProfile_NameThe profile name refers to group names in the imported data.
Profil_DescriptionDescriptionThe profile description
Application_IDExt_Application_Import_IDThe application import ID is mapped to the application ID.
Ext_Profile_IDExt_Profile_IDProfile ID

Indicating Items to Be Removed

If you are using a PDF or an XLS document to review accesses, you will receive it by email from the person who launched the campaign. You can then print the document and indicate, by hand, the items that need to be removed. You can add any comment on an accompanying sheet. You can then return the printed report to the person who launched the campaign.

Configuration Tables

The SELF_SERVICE_QUESTION table

The SELF_SERVICE_QUESTION table is where the questions that can be used in the 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 questions are displayed (smallest first).
RequiredWhether the question is mandatory.
Add_Question_In_Written_RequestIf the question is used as part of a written request, this column indicates whether the question or only the answer is added to the written request. Here is an example with a question: 'My question: My answer' and an example with only the answer: 'My answer'.
TypeThe question type. Supported types are: SELECT, INPUT and TEXTAREA. See the section below.
PageThe page in which the question is used. Supported pages are: TERMINATION_IDENTITY and TERMINATION_EXTERNAL_IDENTITY.
Title_ENThe title of the question in English.
Title_FRThe title of the question in French.
Placeholder_ENPlaceholder to be used in English. Leave empty if you don't need any.
Placeholder_FRPlaceholder to be used in French. Leave empty if you don't need any.
Tooltip_ENThe tooltip to use in English. Leave empty if you don't need any.
Tooltip_FRThe tooltip to use in French. Leave empty if you don't need any.

Types of questions

Two question modes are supported: free text and multiple choice questions.

Free form mode

The two types that can be used for this mode are:

  • TEXTAREA
  • INPUT

The difference between the two is only in the way they are displayed. The first one allows the use of line breaks, while the other is more often used for short-answer questions without line breaks.

Choice mode

The only type supported is SELECT. With this type, the user must choose an option among the provided choices. The available choices for the 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 answer choices for the 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 question identifier for this choice.
Label_ENThe choice text in English
Label_FRThe choice text in French