Placement Validation

Brand new alternative method for validating Placements.

What

We have designed an alternative method of Validating a Placement. The new method allows customers to configure the fields within the Validation, surface fields from other entities such as Client and Candidate, along with making certain fields mandatory. The difference between the two methods is the new way the modal pop-up window appears, which will show the fields, rather than the Mercury core method of hiding the completed ones.
 

Where > Configuration

There are new Configuration records which control the entities displayed, fields visible and mandatory fields within the Support area of Mercury:


How

There is a main Configuration file which allows you to configure the tabs available within the new process:

You are currently only able to add the following:

  • Client

  • Contact (Client Contact)

  • Candidate

  • Placement

Please click the following link to download the Field_Schema_names_for Placement_validation_v29.xlsx This lists all of the available fields that are supported by this config across the Client, Client Contact, Candidate and Placement entities.


The configuration files can be split into 2 groups > Fields Visible and Mandatory:

Fields VisibleMandatory
     PLACEMENT_VALIDATION_CLIENT.ACCOUNT       PLACEMENT_VALIDATION_MANDATORY.ACCOUNT
     PLACEMENT_VALIDATION_CLIENTCONTACT.CONTACT     PLACEMENT_VALIDATION_MANDATORY_CLIENTCONTACT.CONTACT
     PLACEMENT_VALIDATION_CANDIDATE.CONTACT     PLACEMENT_VALIDATION_MANDATORY.CONTACT
     PLACEMENT_VALIDATION_PLACEMENT.CRIMSON_PLACEMENT     PLACEMENT_VALIDATION_MANDATORY.CRIMSON_PLACEMENT

 

NOTE: This is different to some existing config records within Mercury, where you have to choose the fields to hide. Within these configs, you select the fields you wish to display. If a field is not visible within the config, you will be unable to make this mandatory and you will receive an error. In order to make fields show or mandatory within Placement Validation, you will need to add the schema name of the field(s) within the Value - string field of the configuration file.

 

Security Role

For the time being, this feature is hidden behind a security role to allow for the gradual rollout within your business. We propose this process will replace the original Placement Validation, but we want to give our Customers the opportunity to view this Coming Soon feature and provide the ability to give feedback.

In order to provide users access to the new Placement Validation, please assign the following role to them via: Home > Settings > Advanced Settings > Security > Users > Manage Roles


Placement Validation

The majority of our clients opt-in to having an approval process set up, where one, or multiple check points, are run after validation. Approvals help insure correct information across financials, compliance, onboarding, etc. 

The new Validate Placement ribbon button will show on all Placement Statuses.

This will open the Placement Validation record. See Why run Validation on a Placement? to further understand the value of Placement validation and for step-by-step instructions


Users can update the fields as they go. They will also have the ability to save part way through the validation. Once the user has populated or amended the relevant field, they can finalise by changing the toggle of the Finalised field within Placement Validation or via the ribbon menu.

 

Excluding Fields when Cloning a Vacancy

NOTE: The instructions in this section can only be carried out by your organisation's System Administrator.

Alongside cloning a Vacancy, users are now able to set which fields are copied to the new Vacancy. This is done via a new Configuration setting entitled EXCLUDE_FIELDS_CLONE_VACANCY found in the Configuration folder.

Within the Configuration setting, the value – string field will need to have the field the user wishes to be excluded inputted into it.

Once the Vacancy is cloned, the Tags on the original version will continue to be transferred across. However, please note there are certain fields that are unable to be excluded, which are as follows:
 

  • Clone

  • Standard Rate Type

  • Frequency

  • Pay

  • Charge

  • Salary

  • Currency

  • Package Value

  • Auto-calculated Values (recalculated automatically)

  • User Fields

 

Making the Address picker visible 

Please note, if you are looking to include either Client Site Address, Client Invoice Address or Client Correspondence Address, you will need to include the following to show the Address picker:
 
Address Details Client = WebResource_AddressLookup_ClientSite
 
Address Details Invoice = WebResource_AddressLookup_InvoiceAddress
 
Address Details Client Correspondence Address = WebResource_AddressLookup_CorrespondenceAddress



Authored by Matt McNamara - Product Owner @ Mercury

Have any feedback on this article? Let us know or ask the Community if you need more help.