Job board provider

From Onlinehelp
(Redirected from Job platform providers)
Jump to navigation Jump to search

In contrast to job boards like Jobs.ch or Monster, which refer to individual dedicated job boards, a job board provider represents a collection of many job boards, thus allowing for jobs to be published to multiple job boards simultaneously. By default, Umantis Applicant Management offers the following job board providers.

Note:

  • Once a job board provider is set up, the corresponding publication channel can be used in the publication area for a job (see Publish job).
  • As with job boards, the interfaces to job board providers Solique (Unio) and Broadbean can be controlled using XML. Unlike job boards, however, the data to be published are not extracted using SQL, but are controlled with Umantis variables.
  • For the job board providers Solique (Unio) Broadbean, the publication texts are created in Umantis, sent to the provider through the interface, and then prepared from there for publication to the various job boards. For Prospective Media (PMS), on the other hand, publication texts and options for a job are not managed within Umantis, but on the third-party platform itself. The way the publication process works is that HR experts use the links associated with the job to navigate to the corresponding third-party platform, where they can then manage the publication text and all other publication options. They then select the desired media, and put the job posting online for each of those channels.
  • All publication platforms allow the Umantis job board to be used as a publication medium too, so that the publication texts are fed into the corresponding job in Umantis, and the Publication on home page is initiated through the publication platform. The link to the application form for the job in Umantis is always sent along too.

Umantis applicant management

Umantis Applicant Management offers an interface of its own through which other instances of Umantis Applicant Management can actively publish their jobs. In this case, administration of the job posting texts is the responsibility of the sender system, and job postings are published 1:1 in the selected language and specified area (home page or intranet).

Settings in Umantis

The following fields must be filled out in the “sending” Umantis Applicant Management solution in order to use the “receiving” Umantis Applicant Management solution as a job board provider:

  • URL: The URL to which publication requests are directed (e.g. https://recruitingapp-1067.umantis.com). As such, this URL is the actual job board on which you will find the published jobs after successfully linking the two Umantis Applicant Management solutions.
  • Branch office ID in third-party system: Umantis ID of the branch office for which the job should be created in the third-party system, and which should be used for the branch office-specific job positing.
  • User system ID in third-party system: The user’s Umantis ID in the third-party system, i.e. in the Umantis Applicant Management solution that is being used as a job board (see under URL). Publication will go through this ID. The ID in question can be found in the URL of the user’s profile (e.g. https://recruitingapp-1067.umantis.com/Administration/Users/ID/Profile).
  • Authentication key for third-party system: To verify the interface, the two Umantis Applicant Management solution instances exchange keys with each other. Enter the same key here that was entered in the "Authentication key for publication from third-party system" field of the Settings for company / organizational profile in the target solution (see under URL).
  • Job posting layout code for publication on third-party system: In the target system, you can automatically activate a particular job posting layout for publication. This setting is optional — and if you have previously selected other job posting layouts for individual jobs, it is superfluous. In that case, the code for that layout will be sent, overriding this setting.

Once you have correctly filled out the fields, you can publish the job via Internal job posting > umantis Applicant Management home page (third-party system).

Note:

  • You must ensure that the link for the application form points directly to the source Applicant Management instance for each job posting.
  • The application link is sent to the target solution each time the interface is triggered, and can be pulled from the "Text block 6" field of the corresponding publication by using the template variable [Inserat.Text6].

Prospective Media (PMS)

In contrast to job postings on job boards, job posting texts and publication options for a given job on Prospective Media are not managed within Umantis, but on the third-party platform itself. The way the publication process works is that HR experts use the links associated with the job to navigate to the corresponding third-party platform, where they can then manage the publication text and all other publication options. They then select the desired media, and put the job posting online for each of those channels. In addition, the Umantis job board can also be set up as a publication medium, so that the publication texts are fed into the corresponding jobs in Umantis, and the Publication on home page process is initiated through the publication platform. The link to the application form for the job in Umantis is always included here too.

Static vs. generic interface

You can choose to use either the Static or the Generic interface. The difference is that the Generic Interface allows you to send any job publication texts you like, whereas the Static Interface only allows you to send the fields for Job ID, Job Title, Applicant Link and Job Layouts Link.

  • Static Interface: In the static version of the PMS interface, the range of data that can be sent is fixed, i.e. only the following data are permitted: Job ID, Job Title, Applicant Link and Job Layouts Link. The advantage of this version is that there is no need to configure the interface, so it can be used immediately.
    Note:
    These data are sent using URL parameters, and the data that can be sent are therefore subject to a length restriction of 255 characters.
  • Generic Interface: With the generic approach, any job data you like can be sent to PMS. The data to be sent are extracted using Umantis variables, then placed in an XML structure.
    Note:
    The interface sends the data as HTTP POST arguments, so there are no length restrictions.


Settings in Umantis

General settings

The following settings must be configured in the general settings in Umantis.

  • URL: The URL to which publication requests are directed. (The following URL is used by default: https://jobcenter.prospective.ch/NJCWeb/services/fastinterface). The customer-specific URL is: [Customer].jobbooster.prospective.ch
  • Customer ID in Prospective Media: Similar to the Customer ID in Umantis, each customer has a unique ID with Prospective Media. This ID must be stored in Umantis, and is part of the authentication process when communicating data.
    Note: Please check with Prospective Media as to what Customer ID you should use here.
  • Prospective Media XML: With the Generic Interface, you can use an XML-structured document to specify the data that should be sent from Umantis to PMS for publication purposes. Its structure and content can be defined in accordance with the publication requirements. The job data for this XML are extracted using Umantis variables.
    Note: Work with Prospective Media to develop a new XML that fulfills your requirements more effectively than the default XML for the interface.
User-defined settings

Certain settings must be set up for the individual users who are to be allowed to publish content from Umantis to PMS.

  • User security key: The security key is needed to authenticate the associated user.
    Note: You will receive the login information directly from Prospective Media. The IDs of the Umantis users who are allowed to publish to PMS must also be entered in the Prospective Media system.

Settings in Prospective Media

The following Umantis-specific settings must be entered in the Prospective Media system in order to use the interface:

  • User system ID: The Umantis ID of the users who are allowed to use the Prospective Media interface (i.e. to publish through Prospective Media).
  • Customer ID in Umantis: Just as the Customer ID in Prospective Media must be entered in the Umantis settings, the Umantis Customer ID must also be entered in PMS. This is the same ID that you can find in the Umantis URL: https://recruitingapp-[CustomerID].umantis.com


Additional information about Prospective Media (PMS)


Solique (Unio)

In contrast to job postings on job boards, job posting texts and publication options for a given job on Solique (http://www.solique.ch) are not managed within Umantis, but on the third-party platform itself. The way the publication process works is that HR experts use the links associated with the job to navigate to the corresponding third-party platform, where they can then manage the publication text and all other publication options. They then select the desired media, and put the job posting online for each of those channels. In addition, the Umantis job board can be used as a publication medium too, so that the publication texts are fed into the corresponding job in Umantis, and the Publication on home page process is initiated through the publication platform. The link to the application form for the job in Umantis is always sent along too.

You can withdraw a job published on Solique directly through Umantis, with no need to go to the Solique site. Job postings should be published and withdrawn separately for each language.

Note:

  • Until recently, Solique was known as Unio

Settings in Umantis

The following settings must be configured in order to use Solique:

  • Solique login: Login and password information are needed for authenticated publication through Solique. You will receive the login information directly from Solique.
  • Solique password: Password and login information are needed for authenticated publication through Solique. You will receive the login information directly from Solique.
    Click on the "Change Solique password" link and enter the password provided by Solique. The interface is then activated and ready for publications.
  • URL: The URL to which publication requests are directed (default ishttp://www2.unio.ch/cgi-bin/WebObjects/UNUserInterface.woa/wa). Check with Solique about which target URLs your publication requests should point to when the system is in operation.
  • Solique XML: The XML document defines the structural requirements for the publication of jobs through Solique. Its structure and content can be defined in accordance with the publication requirements. The job data are extracted using Umantis variables.
    Click on the “Customize Solique XML” link. Work with Solique to develop a new XML that fulfills your requirements more effectively than the default XML for the interface.

Note:

  • You must make sure that the link for the application form points directly to the source AM instance for each publication.
  • To learn more about operations with Solique (Unio), please consult directly with our partner company.
  • The login name and password for Solique are stored at the user level. The same password should be used for Umantis and Solique.

Publicitas

Publicitas bankruptcy declaration (website announcement)
Click on “Expand” to show the contents.

With the decision of the District Court of Bülach of May 11, 2018, Publicitas AG was declared bankrupt. On May 14, 2018, the Administrative Commission of the Supreme Court of the Canton of Zurich appointed the Aussersihl-Zurich Bankruptcy Office as the Extraordinary Acting Office for the Wallisellen Bankruptcy Office in the bankruptcy proceedings of Publicitas AG. Inquiries may be sent exclusively by e-mail directly to the Aussersihl-Zurich Bankruptcy Office at aussersihl-zuerich@notariate.zh.ch. Additional general information on bankruptcies can be found on this website under the heading “Bankruptcy”
(Source: https://www.publicitas.ch/de/ and link to: https://www.notariate.zh.ch/deu/index.php?not=aussersihl-zuerich, viewed on June 1, 2018, 4:35 p.m. CEST)

In contrast to job postings on job boards, the job posting texts and publication options for a given job on Publicitas were not maintained in Umantis, but on the third-party platform (= Publicitas) itself.
Note that we have never had any influence on the availability or functionality of the Publicitas platform, but merely offer an interface. If you were using Publicitas, we recommend that you check the functionality of your current configuration. Due to the bankruptcy filing, we recommend that you use an alternative platform described on this page.

(Internal documentation: https://wiki.abacus.ch/x/zQ9bD)

Broadbean

In contrast to job board providers Unio and Prospective Media, publication texts for Broadbean are created in Umantis and sent to Broadbean through the interface, where they are then prepared for publication to various media.

An overview of the job boards to which Broadbean can publish is available here: http://www.broadbean.com/job-boards/

Settings in Umantis

The following settings must be configured in order to use Broadbean:

  • Broadbean login: You will receive the login information directly from Broadbean.
  • Broadbean password: Click on the "Change Broadbean password" link and enter the password provided by Broadbean. This will activate the interface immediately.
  • URL: The URL to which publication requests are directed (default is https://api.adcourier.com/hybrid/hybrid.cgi). Check with Broadbean about which target URLs your publication requests should point to when the system is in operation.
  • Broadbean publication XML: The XML document defines the structural requirements for the publication of jobs through Broadbean. Its structure and content can be defined in accordance with the publication requirements. The job data are extracted using Umantis variables.
    Click on the “Customize Broadbean XML” link. Work with Broadbean to develop a new XML that fulfills your requirements more effectively than the default XML for the interface.
  • Broadbean offline XML: Similar to the Broadbean publication XML, you can specify an XML-structured document that can be used to explicitly withdraw a job from the Broadbean job board.
  • Broadbean CSS: The CSS document contains the style guidelines for the Broadbean interface. This document can be used to specify the appearance of the Broadbean forms embedded in the dialog window. If a CSS document is uploaded for use, the Broadbean publication XML must be modified accordingly. The stylesheet attribute must contain the path to the document. To ensure that the new design will be used, the following structure must be used for the CSS path in the Broadbean publication XML:https://<URL der Lösung>/[Broadbean.CSSFile]. The [Broadbean.CSSFile] variable contains the path to the CSS file.
  • One-to-one implementation: In order for Broadbean to re-use the job postings published in Umantis one-to-one, the job description created in Umantis should be sent to Broadbean as HTML. To do this, the following must be added to the unparsed publication XML after </JobDescription>: <VacExtension name='special_formatted_advert'>[Ausschreibung.HTML]</VacExtension>. You must make sure that the path in the job posting layout is not a relative path, but an absolute path. This means that all links and URLs in the templates must specify the full path.

Note:

  • You must make sure that the link for the application form points directly to the source AM instance for each publication.
  • To learn more about operations with Broadbean please consult directly with our partner company.
  • The login name and password for Broadbean are stored at the user level, and can be set up separately for each user.
  • A user will only see the option to publish a job through Broadbeanafter appropriate login data have been specified.


Technical details:

Under Technical details regarding Broadbean, you will find our default XML which lists the fields that we send to Broadbean.

Google4Jobs

Abacus Umantis provides the technical requirements for setting up this interface. Please note that no support is offered for the setup (and thereafter).

▶ We recommend using Umantis Multiposting for publishing job ads!


Details on setting up Google4Jobs (archived)

Google for Jobs is a new Google feature that displays job postings directly on the first page of Google’s search results. To do this, Google aggregates information about job postings from all websites in the search index. What this means for job hunters is that, instead of having to search for relevant job openings on individual companies’ Careers pages or on job boards, they now simply have to enter the appropriate search terms in the Google search field. The most relevant hits are then shown in the results box, along with their source. Searches can be narrowed down further using various filter options, including work hours, industry, and publication date. Clicking on the selected job posting takes the user to the source page, where they can get more information about the job.

Settings in Google

Before you publish a job for Google via Umantis Applicant Management, some settings must be made in Google and within your Umantis solution.

Create OAuth Client-ID

  • Log in with your Google Account at: https://console.developers.google.com/apis.
  • Create a new project.
  • Select “Credentials” on the left and click on Create Credentials > OAuth Client ID. Then follow the steps below:
1. Specify the Application type (Web application).

2. Enter the Name of your OAuth client ID.
3. In the “Authorized redirect URIs” field, please enter in the following format, replacing the [YourSolutionNumber] section with the ID of your Umantis Applicant Management solution: https://recruitingapp-[YourSolutionNumber].umantis.com/callback/google4jobs
4. Click on “Create”. A window with the Client ID and the Client Key will appear.

5. Transfer the client ID into your Umantis solution in the field “API key” (under: /Administration/JobPlattforms/Google4Jobs)

6. Transfer the client key into your Umantis solution into the field “Secret Key” (also under: /Administration/JobPlattforms/Google4Jobs)

Verification

You have successfully created the client ID and client key for your application (HTM) and stored it in your Umantis solution. Now you must carry out a verification to confirm ownership of the solution.

  • Open the following page https://www.google.com/webmasters/verification/home?hl=de
    and click on “Add property”.
  • Customize the following URL according to your Umantis solution number and enter it as a property that you verify: https://recruitingapp-[YourSolutionNumber].umantis.com/VacanciesGoogle4Jobs/
  • After clicking “Next”, select the “HTML Tag” method, which you may find in the “Alternative Methods” tab
  • Copy the code from the meta tag (marked yellow in the screenshot) and paste it into the field Verifikationsschlüssel für Ihre Domain (Verification key for your domain) in your Umantis solution. Save these settings of your Umantis solution before you click “Verify” in Google.

You can also use https://www.google.com/webmasters/tools/home for verification.

Indexing API

In order to verify the owner of the URL to be indexed (when publishing jobs), the Google Indexing API is required.

  • Using Google's API library (https://console.developers.google.com/apis/library), find “Indexing API”.
  • Add it and select your solution under "Credentials".
  • Add the following custom redirect URL under “Authorized redirect URls”: https://recruitingapp-[YourSolutionNumber].umantis.com/callback/google4jobs.
  • Click on “Save”.

Next, add the enabled “Indexing API” in the OAuth approval screen by:

Afterwards, you can publish the respective job within your Umantis applicant management solution via the tab External posting (via “Google4Jobs”). Please note that you have to agree to the indexing by Google the first time you publish a job.

Please note that it may take up to 24 hours before vacancies can be “captured” by Google (assuming the interface is successfully set up and the vacancy is advertised via Google4Jobs).

Job not listed?

You can check whether you have filled in all the necessary fields to ensure that they can be found successfully by Google.

  • Click on the following link: https://www.google.com/webmasters/tools/home
  • Under “URL prefix”, enter the following link, customized according to your solution number: https://recruitingapp-[YourSolutionNumber].umantis.com/VacanciesGoogle4Jobs
  • Check the following URL, customized according to your solution number and the job published via Google4Jobs: https://recruitingapp-[YourSolutionNumber].umantis.com/VacanciesGoogle4Jobs/[ID]/Description/[ID]
  • Then check the notes/information and configure your Umantis applicant management solution, where applicable.

For more information, see: https://support.google.com/webmasters/answer/9012289#url_cannot_be_on_google

Settings in Umantis Applicant Management

  • API key
Enter the API key or the client ID here (provided via your Google Account, see above).
  • Secret key
Enter the secret key or the client key here (provided via your Google Account, see above).
  • Verification key for your domain
To verify that this is indeed your domain, Google needs access to an open page under your domain and will search there for an HTML MetaTag containing a certain (your) code. Please enter here only the key without MetaTag (as described above).
The whole MetaTag will look like this: <meta name="google-site-verification" content="Verifikationsschlüssel für Ihre Domain">
and can be found here: https://recruitingapp-[YourSolutionNumber].umantis.com/VacanciesGoogle4Jobs/.
Please customize the URL according to your solution ID and use the complete URL to this page in the Google settings to verify your domain.
  • JSON document
The use of an individual JSON structure is optional. This allows you to use specific features of the Google4Jobs interface that may not be supported in the standard version. However, we recommend to stay in the standard and not to save a JSON document or only for a transitional period, so that you can benefit from improvements or adjustments of the interface in the future.
  • JSON document - example
Use the sample file as basis for your individual JSON file, which you can upload in the upper field after completion.

Callback URL
You can configure a callback URL to your server. To ensure a secure authentication process and prevent abusive data transfers, Google only accepts URLs that you have defined as trustworthy. The callback URL must have this format: https://recruitingapp-[YourSolutionNumber].umantis.com/callback/google4jobs

RAV job boards

More information and guidelines can be found on the following page: Information on the job reporting requirement (Switzerland)

Related topics

Retrieved from "https://en.onlinehelp.umantis.com/index.php?title=Job_board_provider&oldid=8888"