Foreword

HRMTS offers multiple integration options. This page provides a basic guide to find out which integrations are suitable for your (Customer's) needs.

Vacancy List on Career Page

The foremost important integration you need is to list the vacancies on your career page. Which one of the following best describe your requirements?

Talent Recruiter as Career Page

This is the most simple option. Using this option, the System will serve as your career page. Whenever your clients would like to visit your career page, they will be redirected to the career page in the System, which will be designed according your needs and requirements. This way, your clients will continue to feel that they are still on your website.

Process

1. Inform HRMTS Support that you want to use this option.
2. HRMTS Technical Support coordinates with you to implement your company's design on the career page.
3. HRMTS Support provides you with a URL that you send to your technical staff.
4. Your technical staff connects this URL to appropriate places in your company's website.

Vacancy List in IFrame on Career Page

This option is also quite simple. Using this option, your career page will remain on your company's website. The vacancies from the System are then shown inside an IFrame on your career page. The contents of the IFrame will be designed according to your needs and requirements. This way, your clients will never leave your website while browsing for jobs.

Process

1. Inform HRMTS Support that you want to use this option.
2. HRMTS Technical Support coordinates with you to implement your company's design in the IFrame.
3. HRMTS Support provides you with a URL that you send to your technical staff.
4. Your technical staff connects this URL to the IFrame on your career page.

Vacancy List as API

This option gives you 100% control on how to retrieve the vacancies from the System, store them on your server, integrate with your internal system, and finally, display on the career page. This option does not only give 100% freedom of design, but also ability to combine information from other sources, as well as detailed logging for analytics purposes.

Important to Know

1. The option requires development by Customer.
2. See: Integration Support Package
3. Documentation: TR Job Portal API (public)

Process

1. Inform HRMTS Support that you want to use this option.
2. HRMTS Support enables the API in your account, and sends you a URL to the API.
   1. Send this information to your technical staff along with the documentation.
   2. Your technical staff must read the documentation thoroughly.
3. You technical staff implements a consumer to the API that reads the vacancies form the System and displays on the company's website.

Single Sign-On (SSO)

The System offers SSO that allows users to sign into the System without entering a username and password. The users are authenticated on company's own network, and granted access to the System. In practical terms, the users simply click on a link provided on Customer's Intranet which takes them directly into the System.

Important to Know

1. The option requires that Customer has the necessary infrastructure to support SSO.
2. The option also requires that your technical staff knows how to configure SSO on your end.
3. See: Integration Support Package
4. Documentation: Single Sign-On (SSO)

Process

1. Inform HRMTS Support that you want to use this option.
2. HRMTS Support enables SSO in your account, and provides you with a SAML metadata URL.
   1. Send this information to your technical department along with the documentation.
   2. Your technical staff must read the documentation thoroughly.
3. Your technical staff implements SSO on their side, sends necessary information back to HRMTS Support, and coordinates verification.

Good to Know

• It is not required to synchronize users or departments in order to use SSO.

Synchronizing Department Hierarchy

Department hierarchy is an important part of the System. Sometimes, Customers do not want to replicate their internal department hierarchy into the System. When they do, then arises the question of synchronizing the department in the System whenever changes occur in Customer's internal hierarchy. To facilitate this, the System offers a dedicated web service to automatically synchronize the departments. Using this option, any change in Customers' internal hierarchy can be replicated automatically in the System.

Important to Know

1. The option requires development by Customer.
2. See: Integration Support Package
3. Documentation: Department Synchronization API

Process

1. Inform HRMTS Support that you want to use this option.
2. HRMTS Support enables the API in your account, and issues an API Key.
   1. Send this information to your technical staff along with the documentation.
   2. Your technical staff must read the documentation thoroughly.
3. Your technical staff implements a consumer to the API that reads the internal department hierarchy and sends to HRMTS.

Good to Know

• HRMTS can provide a test account for the development. It must be clarified with HRMTS. Limitations may apply.
• As the development is done by the Customers, there is no dependency or wait time from HRMTS. The Customers set their own pace. However, during the testing phase, certain coordination with HRMTS will be required.
• You should carefully evaluate the need of department synchronization based on your company's needs and requirements. If you have few departments, or changes in your internal hierarchy occur quite seldom, then you can always replicate the changes in the System manually.
• It is also possible to have a mix of synchronized and manually managed departments in the System.

Synchronizing Users

For large organizations with many users, it can be difficult to manually manage their users in the System. To facilitate this, the System offers a dedicated web service to automatically synchronize the users with Customers' own directory services. Using this option, any change in Customers' user base can be replicated automatically in the System.

Important to Know

1. The option requires development by Customer.
2. See: Integration Support Package
3. Documentation: User Synchronization API

Process

1. Inform HRMTS Support that you want to use this option.
2. HRMTS Support enables the API in your account, and issues an API Key.
   1. Send this information to your technical staff along with the documentation.
   2. Your technical staff must read the documentation thoroughly.
3. Your technical staff implements a consumer to the API that reads the users from your Directory Service and sends to HRMTS.

Good to Know

• HRMTS can provide a test account for the development. It must be clarified with HRMTS. Limitations may apply.
• As the development is done by the Customers, there is no dependency or wait time from HRMTS. The Customers set their own pace. However, during the testing phase, certain coordination with HRMTS will be required.
• You should carefully evaluate the need of user synchronization based on your company's needs and requirements. If you have few users, or changes in your user base are not that often, then you can always manage the users in the System manually.
• It is also possible to have mix of synchronized and manually manage users in the System.
• Department and synchronizations are independent of each other.

Fetching Hired Candidates

Quite often, Customers would like to fetch the candidates hired in the System to import them into internal ERP systems. To facilitate this, the System offers a dedicated web service to do exactly that.

Important to Know

1. The option requires development by Customer.
2. See: Integration Support Package
3. Documentation: TR Candidate API V2

Process

1. Inform HRMTS Support that you want to use this option.
2. HRMTS Support enables the API in your account, and issues an API Key.
   1. Send this information to your technical staff along with the documentation.
   2. Your technical staff must read the documentation thoroughly.
3. Your technical staff implements a consumer to the API that fetches the hired candidates and imports into the ERP system.

Good to Know

• HRMTS can provide a test account for the development. It must be clarified with HRMTS. Limitations may apply.
• As the development is done by the Customers, there is no dependency or wait time from HRMTS. The Customers set their own pace.

Archive Recruitment (Case) Documents

In Norway, there is a requirement for all government organizations to archive documents and communication during recruitment processes. It includes protocols, advertisements, candidate applications, candidate lists (public and extended), rejections, and so forth. These documents must be archived in Customers' archiving system that supports NOARK version 4 (or 5). To facilitate this, the System offers a unique integration option that can automatically push out relevant documents from the System over the Customers' archive.

Important to Know

1. The option requires a special environment to be delivered by the Customer. See documentation for more information.
   
2. There is cost associated with this option, which will depend on whether your archive is already supported by the System or not.
   1. Following NOARK archives are currently supported:
      1. ESA
      2. Ephorte
      3. WebSak
      4. Public 360
3. The Customer must ensure that they have Geo-Integrasjon license from their vendor of archive.
4. For implementations that are currently not supported, the Customer must cover the following costs:
   1. Cost of development of integration from the System to their archive.
   2. Cost to their vendor of archive for integration support.
5. Documentation: Proxy Web Service

Process

1. Inform HRMTS Support that you want to use this option.
2. A process is started to calculate cost of the project.
3. Once agreement is reached, the HRMTS Technical Support coordinates the rest with you.
4. In the final stage, one or more online sessions are required with your Archive Expert to configure the integration values.

Exporting Hired Candidates

The System also supports an option to export hired candidates directly into Customers' internal ERP systems. As Customers' internal ERP systems are (mostly) located in the internal network without any interface open toward the Internet, this integration requires a quite unique setup to function, and, therefore, also a significant cost to it.

Important to Know

1. The option requires a special environment to be delivered by the Customer. See documentation for more information.
   
2. There is cost associated with this option, which will depend on whether your ERP system is already supported by the System or not.
   1. Following ERP systems are currently supported:
      1. Visma
      2. Silkeborg Data
      3. SAP
3. The Customer must ensure that they have necessary licenses from their vendor of ERP system.
4. For implementations that are currently not supported, the Customer must cover the following costs:
   1. Cost of development of integration from the System to their ERP system.
   2. Cost to their vendor of ERP system for integration support.
5. Documentation: Proxy Web Service

Process

1. Inform HRMTS Support that you want to use this option.
2. A process is started to calculate cost of the project.
3. Once agreement is reached, the HRMTS Technical Support coordinates the rest with you.
4. In the final stage, one or more online sessions will be required with your ERP Expert to configure the integration values.