Summary Overview
Utilize and configure third party iframe integrations in Mercury using the Third Party Integration Framework.
Integrations can be accessed either via the sitemap or against a Contact/Vacancy record.
Prerequisites
The instructions in this article can only be carried out by users with Admin security access, or via your CRM.
Step-by-Step Instructions: Config
Navigate to Advanced Find within Mercury. E.g. https://mercury-example.crm123.dynamics.com/main.aspx?pagetype=advancedfind
Select the third party record from the drop-down list, then click Results to search.
Third Parties
Select from the results page:
NOTE: Any user with Admin security access can edit and/or create new Third Party records. However, we strongly recommend to go through your CSM to make any changes required (during, or following, the certification process) as we cannot offer support for customisations of this kind.
Third Party UI Integrations
These records specify the location(s) of each iframe for each third party within Mercury.
NOTE: We recommend that users create this record type after creating the Third Party record. Alternatively, users can select a Third Party record and then access the Third Party UI Integration record from the Related tab; this will auto-populate the Third Party.
NOTE: Any user with Admin security access can edit and/or create new Third Party UI Integrations records. However, we strongly recommend to go through your CSM to make any changes required (during, or following, the certification process) as we cannot offer support for customisations of this kind.
Name: Tab name that is visible from either the site map or the select entity type, depending on the configuration. This name can replace the tab name for ‘Integrations’ within an Entity record (Contact or Vacancy) if only one Third Party is configured. This does not apply to the Sitemap.
UI Location: Select one option from a drop-down menu for either ‘Sitemap’ or ‘Entity’.
Entity Name: Select one option from a drop-down menu for either ‘Contact’ or ‘Vacancy’.
Sort Order: The iframe tab number within the entity record.
URL: URL displayed within the iframe.
URL Parameters: The iframe functionality only needs to include the minimum number of details required (e.g. candidateId, userId, etc.) – everything else is then handled by the Public API.
Third Party: Link to the Third Party record.
Owner: Owner of the record
Third Party User Identifiers
Mappings of Mercury users to external users on the Third Party. This exists to allow for specific Mercury user to external user mappings which can allow the Mercury user to gain access to certain privileges when accessing the third-party application via Mercury. It is one Third Party User Identifier per individual user.
Specifying user mappings within Mercury config is optional. I.e. if the userId is included within the URL Parameters field of Third Party UI Integrations record, access level per user can be determined from that point.
NOTE: Users with Admin security access can edit and/or create new Third Party User Identifiers records. However, we strongly recommend to go through your CSM to make any changed required (during, or following, the certification process) as we cannot offer support for customisations of this kind.
Name: Name of the user identifier type (the Mercury User).
System User: User record within Mercury.
Third Party: Link to the Third Party record.
External User Id: Reference for the external user that the Third Party uses to link to their application.
Owner: Owner of the record.
END