We have a number of areas of enhancements in this release including Timesheets and Spec Sends, and a range of other UI and UX improvements designed to make it easier than ever for you to use Mercury.
Jump to:
UI/UX Enhancements
| Timesheets | |||
| 93438 | Editing Timesheet Line on a Timesheet | ||
| What: | You are now able to ‘edit’ a Timesheet on behalf of a Candidate, saving them having to go back through the process of updating, re-submitting and getting approval for the updated Timesheet. This is managed with a specific Security role – (Mercury-Can-Edit-Timesheet-Line) and can be applied to any Timesheet with the associated status of Draft, Submitted, Recalled or Rejected. | ||
| Where: | Timesheet – Timesheet Lines tab | ||
| Why: | Enhanced user experience as Candidates do not need to go back through the various stages of submission if the Timesheet has been edited.
| ||
| 92740 | Control display of additional fields on Timesheet Lines via Timesheet Template | ||
| What: | We have given Timesheet Admins the ability to decide if specific items are shown within the Candidate Portal when a Candidate is completing their Timesheet, giving them control over the data collected and Candidate experience. Added new fields on the Timesheet Template form | ||
| Where: | On the Timesheet Template form | ||
| Why: | So that the Candidate can provide additional information where appropriate. These fields are Comments, Project & Purchase Order.
| ||
| 92635 | Additional fields on Timesheet Lines | ||
| What: | To allow Candidates to have more flexibility over the information that they can populate via the Candidate Portal we have added some more fields to Timesheets Lines in Core. When a Candidate is filling out their time, they now have the ability to add any Comments per Rate worked. They can also specify which Project & Purchase Order the time worked should be applied to. Please note – this work has been completed in Core in preparation for showing it in the Candidate Portal but is not currently available in the Portal. That work will be undertaken as part of the Release Train, not as part of the v35 Release. Added additional fields on Timesheet Lines | ||
| Where: | On the Timesheet Lines form | ||
| Why: | So that the Candidate Portal can display the new fields for population by the Candidate. These fields are Comments, Project & Purchase Order.
| ||
| 92636 | Timesheet 'type' on timesheet template | ||
| What: |
A new field called "Type" has been added to the Timesheet Template entity. | ||
| Where: | On the Timesheet Template main form and Timesheet Template Quick View form. | ||
| Why: | So users can decide what is displayed within the Candidate Portal either in the current 'Unit' UI or the new 'Time' UI.
| ||
| 92732 | Provide a mechanism for future timesheet post-processing | ||
| What: | In order to better support non-UK Timesheet processes, we have added configuration to give you more flexibility over what happens to the Timesheets once they have been Processed. Created a config to allow customers to stop updating a timesheet to "Submitted" in order to implement their own logic when the timesheet moves to "Pending Processing" | ||
| Where: | Mercury Admin app > Support > Configuration > TIMESHEET_UPDATE_TO_SUBMITTED config | ||
| Why: | So customers can handle timesheets their own way.
| ||
| 94542 | Number of Working Day Calculation on Timesheet | ||
| What: | As part of the work done to allow for forecasting on Timesheets Mercury will now automatically calculate the number of working days associated with the Timesheet.
| ||
| Where: | Placement → Timesheets Tab → Create Timesheets → Populates Number of Working Days (Note - hidden in FORECAST & ACTUALS section) | ||
| Why: | I would like the number of working days to be calculated between Start Date and End Date of a Timesheet to assist with forecasting.
| ||
| 94541 | Pay Forecast Amounts on Timesheet | ||
| What: | We have added the ability to see a forecast of the Pay on a Timesheet to make it easier to see when Candidates are due to work and the associated costs.
| ||
| Where: | Placement → Timesheets Tab → Create Timesheets → Populates Forecast Pay(Note - read only on FORECAST & ACTUALS section) | ||
| Why: | So I can see what the Candidate is scheduled to work for that period and how much they are to be paid
| ||
| 94602 | Charge Forecast Amounts on Timesheet | ||
| What: | We have added the ability to see a forecast of the Charge on a Timesheet to make it easier to see what the Client is charged for that period of time.
| ||
| Where: | Placement → Timesheets Tab → Create Timesheets → Populates Forecast Charge (Note - read-only in the FORECAST & ACTUALS section) | ||
| Why: | So I can see what the Client is due to be charged for that period
| ||
| 94606 | Actual Pay Amount on Timesheet | ||
| What: | Users are now able to see the actual amount of Pay on a Timesheet so that they can easily see what the Candidate worked for that period and associated pay for that period of time. Added new field Actual Pay on Timesheet, which shows a sum of all Financial Transactions from the Pay Net field | ||
| Where: | Forecast & Actuals tab of a Timesheet form | ||
| Why: | So I can see what the Candidate worked for that period and the associated Pay
| ||
| 94607 | Actual Charge Amount on Timesheet | ||
| What: | Users are now able to see the actual amount of Charge on a Timesheet so that they can easily see what the Client is to be Charged for a particular time period. Added new field Actual Charge on Timesheet, which shows a sum of all Financial Transactions from the Charge Net field | ||
| Where: | Forecast & Actuals tab of a Timesheet form | ||
| Why: | So I can see what we are to charge the Client for that period
| ||
| 94603 | Forecast Margin, Margin % & Markup % on Timesheet | ||
| What: | You are now able to see a forecast for Margin, Margin % and Markup % for a Timesheet to help you understand future margin information. Forecast Margin, Margin %, and Markup % fields added to Timesheet | ||
| Where: | Forecast & Actuals tab of a Timesheet form | ||
| Why: | So we can easily see the Margin without manually calculating, using the correct currencies from the Placement
| ||
| 94608 | Actual Margin, Margin % & Markup % on Timesheet | ||
| What: | You are now able to see the actual Margin, Margin % and Markup % for a Timesheet so that you can view those values per Timesheet, taking into account multiple currencies where appropriate. Actual Pay, Charge, Margin, Margin % and Markup % are now derived from a Financial Transactions upon completion of the Timesheet. Multi-currency is taken into account when calculating the Margin value. | ||
| Where: | Forecasts & Actuals tab of a Timesheet form | ||
| Why: | Allowing me to gain valuable insight into the Timesheet and the actual amounts payable / chargeable
| ||
| 97053 | Multi Currency Forecast & Actuals on Timesheet | ||
| What: | We’ve made it easy to view which currency Forecast and Actual value is in, this will help you to get true forecast and actuals based on the different currencies taken from the Placement. Added currency fields to accompany Forecast and Actuals on Timesheets | ||
| Where: | Timesheet form | ||
| Why: | So I can be sure that the values are a true forecast and actuals based on the different currencies taken from the Placement
| ||
| 98893 | View Timesheet Lines from Timesheets View | ||
| What: | When you are looking at Timesheets in Mercury via ‘Timesheets’ on a Placement there is now a dropdown so that you can see all associated Timesheet Lines, making it quick and easy to view which different days/rates were worked for that particular Timesheet without having to open the record. Enabled the Timesheet entity to display a dropdown of all Timesheet Line records associated with it | ||
| Where: | Both in the main grid view and on the subgrid on the Mercury Placement form | ||
| Why: | To allow recruiters to quickly view the breakdown of days and rates worked without needing to open the full Timesheet record
| ||
| 98173 | New Chart for Timesheet | ||
| What: | To support the work done on Timesheets we have created a new chart which shows Forecast Margin vs Actual Margin on a month-by-month basis, giving you invaluable information around expectations vs actual for Timesheets at a glance. New chart added for Timesheets | ||
| Where: | 'Show Chart' when looking at Timesheets | ||
| Why: | Following the addition of new fields on Timesheets to show Forecast and Actuals, we've now added a handy chart for a more visual representation of forecast vs actual
| ||
| Spec Sends | |||
| 85694 | Convert a Spec Send into an Info | ||
| What: | We have given users the ability to choose what to do with a record that they create as part of a Spec Send. As a result you are now able to choose to convert it to an Info record. Converts a Spec Send record into an Info record and links the two together via lookup columns. | ||
| Where: | Spec Send Grid & Spec Send Item → Convert To Info Ribbon Button | ||
| Why: | So I can easily create an Info record directly from a Spec Send without manually adding
| ||
| 97901 | Convert a Spec Send into a Vacancy | ||
| What: | We have given users the ability to choose what to do with a record that they create as part of a Spec Send. As a result you are now able to choose to convert it to a Vacancy record. A user can now convert a spec send to a vacancy, and if a candidate is available on the spec send then a shortlist will also be created | ||
| Where: | Convert To Vacancy button is available on the Spec Send home grid and form | ||
| Why: | So that I can quickly open a new vacancy form with as much information populated from the Spec Send Please note, we have relabelled 'Converted From' to 'Info' to avoid any confusion. We have also made this read-only. | ||
Both of the above provide visibility of how many Spec Sends have been converted to Vacancies & Placements.
| |||
| 97902 | Create a Shortlist when a new Vacancy is created from a Spec Send | ||
| What: | When a new Vacancy has been created from a Spec Send (see ID 97901) a Shortlist record will now automatically be created which means you will not need to add to do so manually. When converting a Spec Send to a Vacancy, a Shortlist will also be created for the Candidate | ||
| Where: | Convert To Vacancy button is available on the Spec Send home grid and form | ||
| Why: | So that I can quickly open a new vacancy form with as much information populated from the Spec Send
| ||
| Compliance and Placements | |||
| 100370 | Change Compliance Status grid on Placement Forms | ||
| What: | In order to make the Compliance and Onboarding sub grids clearer on the Mercury and UCI Placement forms we have removed the ‘Go to Record’ icon. Go to Record icon is now removed from the compliance status view | ||
| Where: | Compliance/Onboarding sub grids on Mercury Placement / UCI. | ||
| Why: | To reduce confusion
| ||
| 98861 | Compliance Status Colours | ||
| What: | We have brought the colours in the Compliance Status in line with other areas of Mercury to improve consistency across the product. Updated the colours for the different Statuses of Compliance | ||
| Where: | 'Compliance Status' via the Related menu of a Placement | ||
| Why: | Users now have visual indicators for Confirmation Status and Validity fields, which matches other areas of Mercury. In the next release, these visuals will also be added to the subgrid on the Mercury Placement form.
| ||
| 98862 | Compliance Evidence Colours | ||
We have brought the colours in the Compliance Evidence in line with other areas of Mercury to improve consistency across the product.
| |||
| 71922 | Hierarchy on Contact lookups in Placement Validation | ||
| What: | When you select a Contact in the Placement tab of Placement Validation you will only be able to select from Contacts in the relevant Hierarchy. This makes the behaviour consistent with other areas of Mercury. When selecting a Contact in 'Placement' tab, users would like to only see Contacts within the Relevant Hierarchy. | ||
| Where: | 'Placement' tab of Placement Validation form | ||
| Why: | This ensures that the user can be confident they are selecting the correct Contact
| ||
| 96224 | Placement Form UI Tweaks | ||
| What: | We’ve made some small tweaks to the Placement Form to ensure consistency with the legacy UCI form. Small tweaks, and changes such as Agreement filtering by Type, Yes / NO fields set to be toggles to Mercury Placement form | ||
| Where: | On Mercury Placement Form | ||
| Why: | So both forms have the same functionality
| ||
| Vacancy Updates | |||
| 86180 | RTF Fields on Vacancy - IDEA-01616 | ||
| What: | We have now made more of the fields in the Vacancy form rich text fields so that it is easier for you to create job adverts, emails etc with additional formatting to make them more visually appealing to Candidates. Updated Email Description, Job Summary (Job Board) & Job Description on Vacancy forms to include rich text field | ||
| Where: | On the Mercury Vacancy and UCI forms. | ||
| Why: | To allow for greater content formatting, highlight key information, and make the advert visually appealing to attract the right candidates. This will also be passed through to the Job Posting provider. | ||
Please note – Broadbean and LogicMelon and Idibu all handle the formatting in different ways for example;
| |||
| 86884 | Vacancy Form UI Tweaks | ||
| What: | We’ve made some slight UI changes to bring additional parity across the Mercury Vacancy and UCI forms to improve product consistency. Updated the Mercury Vacancy form to remove discrepancies between V1 and V2, including: Moving 'Agreement' to underneath Client | ||
| Where: | On the Mercury Vacancy form | ||
| Why: | To make the experience more consistent.
| ||
| 87249 | Choice Colours on Vacancy | ||
| What: |
| ||
| Where: | Vacancy Home Grid view | ||
| Why: | So it can be easily readable
| ||
| Client Updates | |||
| 62976 | Client > Related Menu Tidy Up | ||
| What: | We’ve made some changes to the ‘Related’ menu of the Client area of Mercury to make it easier for you to get to the information you need. For the Client entity, the Mercury Account form's "Related" menu has been tidied up. We have removed everything from the Related – Common menu. Anything that appears here is not part of our core solution. Some menu items have also been renamed to provide clarity of their relationship, moved, and sorted into Related – Mercury. | ||
| Where: | Mercury Account form → Related | ||
| Why: | Makes things clearer, cleaner and easier to navigate around.
| ||
| 83377 | Contact View on Client | ||
| What: | We have removed the ‘Current Client’ as a column when you are already in the Client area of the Mercury Account form. Removed 'Current Client' as a column when looking at Contacts on a Client | ||
| Where: | 'Contacts' tab of a Client (Mercury Account form) | ||
| Why: | Column was not useful as User was already on the Client record
| ||
| 98670 | Remove Social Profiles from Client Related | ||
| What: | To improve the Related menu on the account/client forms we have removed Social Profiles. Removed social profiles from the account/client forms | ||
| Where: | On the client forms | ||
| Why: | Social Profiles removed from the Related menu following #6297
| ||
Flag Entity Please note - whilst you may see the Flags entity at the moment Flags are still managed via Search, so please do not create any flags using this new entity until all of the associated work has been completed. Search Flags will also not yet be populated. We will let you know when this new feature is fully available. | |||
| 96579 | Flag Entity | ||
To make it easier to view which Candidate / Vacancies have been flagged during Search you are now able to record and Manage Flags via the new Flags entity.
| |||
| 96583 | Search Flags Entity | ||
| What: | You are now able to see if a Candidate or Vacancy has been flagged by someone in Mercury Search. This will give you valuable information to see what someone has flagged as noteworthy. New entity to record if a Candidate or Vacancy has been flagged within Search | ||
| Where: | Related Menu on a Candidate and/or Vacancy~ | ||
| Why: | Ability to see if a Candidate or Vacancy has been flagged by someone within Search from within Mercury. This gives valuable information to a recruiter if a record has been flagged by someone.
| ||
| Other UI Enhancements | |||
| 87208 | Data Protection Dashboard > Add Dashboard to Apps | ||
| What: | Based on an idea from a customer, we have re-ordered the default views on the Data Protection Dashboard to make it easier to view what needs to be actioned. Updated the Mercury Data Protection dashboard to show the most appropriate and relevant views | ||
| Where: | On Mercury / Mercury Admin app. Please note, this is only visible for users with the 'Mercury - Data Protection Officer' security role | ||
| Why: | So I can easily see and distinguish between Data Requests and Removals for a Candidate and Client Contact
| ||
| 95419 | 'Novate' label change to 'Change Client' | ||
| What: | We have renamed the Novate button to Change Client so that it is easier to understand what it does. Novate Placement has been re-labelled to Change Client. This will be apparent on the ribbon and on the page that flies out from the right of the screen | ||
| Where: | Both UCI & Mercury Placement Form → Change Client (Ribbon Button) | ||
| Why: | So, it is more intuitive and clearer to the End User.
| ||
| 98895 | Invoice Instructions for a Candidate Company | ||
| What: | You are now able to associate Invoice Instructions to a Candidate Company, bringing the functionality in line with what currently happens for a Client. This makes it easier to record invoicing instructions. Now able to select an invoice instruction on the Candidate Company | ||
| Where: | Candidate Company record | ||
| Why: | Enables recruiters to record invoicing instructions similarly to how it's done for Clients, improving consistency and usability
| ||
| 72109 | Make Work Contact Fields Visible via Config | ||
| What: | Following on from customer feedback you now have the ability to decide whether work contacts fields (work email, work phone, work mobile) are included on the Candidate record via configuration. This will make it easier for you to communicate with your candidates in the way that works best for you, your business and your candidates. Dictates whether work contact details are forced to be visible or not. By default they’re hidden on the form. This will conflict with the same field names in HIDDEN_FIELDS.CONTACT or HIDDEN_FIELDS.CRIMSON_CANDIDATE, so users will need to remove them from the hidden fields configs. | ||
| Where: | Mercury Contact -- Contact Details Section Configuration record 'ALWAYS_SHOW_WORK_CONTACT_DETAILS' by adding emailaddress1, telephone1,mobilephone | ||
| Why: | So I can ensure I have all the relevant contact details and can email them about work related communications.
| ||
| 79242 | Remove Skills from Info | ||
| What: | Previously, Skills were used as part of Legacy Search, however they are no longer used in New Mercury Search and so we have removed them from an Info Record. Removed 'Skills' from an Info Record | ||
| Where: | Info Record | ||
| Why: | Skills are not used within Search, therefore removed from an Info record
| ||
| Integration Updates | |||
| 83327 | LogicMelon - Remove 'Post Vacancy' page for already posted vacancies | ||
| . | |||
| What: | This enhancement reduces the need to open different pages to see Vacancies that have already been posted for users of LogicMelon. Remove 'Post Vacancy' page for already posted vacancies | ||
| Where: | On Vacancy form, Manage Advert tab (Logic Melon) | ||
| Why: | So users no longer need to click on the 'Post Vacancy' button for vacancies that have already been posted
| ||
| 90789 | Daxtra Date Formatting | ||
| What: | To ensure that all data for Work History and Education is parsed correctly we have changed the data formatting in Daxtra. This accommodates where only a year (rather than day – month – year) has been entered. The Start and End dates were not being formatted correctly in certain scenarios. For example, if the End date was specified as 12-2020, it was previously displayed as 01-12-2020. This behaviour has now been corrected, and the End date is displayed as 31-12-2020. | ||
| Where: | Work History or Education sub grid on Contact forms | ||
| Why: | This issue was causing incorrect or missing data to appear in the Work History and Education records
| ||
| Other updates | |||
| 87167 | Removal of Saved Queries from Mercury | ||
| What: | We have removed 'Saved Queries' from Mercury as these are no longer needed since the release of New Mercury Search. With the adoption of Mercury Search, we have removed Saved Queries from Mercury apps | ||
| Where: | Mercury and Mercury Admin Sitemaps | ||
| Why: | Saved Queries are not used within Mercury Search, therefore they are now redundant
| ||
Software Fixes
| 61779 | Contacts with no SharePoint Location |
| Some customers reported that a SharePoint Document location was not being created when a Contact was switched from a Client Contact to a Candidate. This has now been resolved. | |
| Tags - SharePoint | |
| 80713 | Unable to add Client to Project |
| A bug was identified when the Client field was locked on a Project when creating ‘New’. This has now been rectified. | |
| Tags - Projects | |
| 92594 | Candidates subgrid in Projects shows an error when empty |
| When viewing a Project, the Candidates subgrid was displaying an error when it was empty. This was on the Candidates tab on a Project. This has been resolved. | |
| Tags - Projects | |
| 90278 | Unable to add 'Update' on Shortlist Timeline |
| The ability to ‘Update’ on a Shortlist Timeline was not showing. This has now been rectified. | |
| Tags - Shortlist | |
| 89160 | Placement not incrementing the revision number |
| On both the UCI and Mercury Placement Forms when a material change was made (i.e. Start Date) and saved, the Placement was not incrementing as expected. This has now been resolved | |
| Tags - Placement | |
| 93873 | PlacementAgreement banner timeout issue overwriting messages |
| When adding an Agreement to a new Placement (Placement – New – Add Agreement via look up) the financial banner notifications were not displaying correctly. The banner now displays as expected. | |
| Tags – Placement | |
| 84782 | Placement Validation Missing Fields - Candidate |
| If a user added new fields (Latest Source, EU Resident, ..) in the PLACEMENT_VALIDATION_CANDIDATE.CONTACT config, it was not appearing in Placement Validation 'Candidate' tab. This is now showing. | |
| Tags – PlacementValidation | |
| 84783 | Placement Validation Missing Fields - Client Contact |
| If a user added new fields (Job Title, ..) in the PLACEMENT_VALIDATION_CLIENTCONTACT.CONTACT config, it was not appearing in Placement Validation Client Contact tab. This is now showing. | |
| Tags – PlacementValidation | |
| 36881 | Cloning Placement does not inherit from Agreement / Worker Type |
| When cloning a Placement, Compliance, Expenses and Benefits information were not carrying over into the cloned version. This has now been resolved. | |
| Tags – Clone, Placement | |
| 92564 | Mercury Placement Form - Missing 'This Placement Has Been Extended' Banner |
| The Mercury Placement form was not displaying the "This placement has been extended" banner when applicable. The banner is now showing as expected. | |
| Tags – Placement, Forms | |
| 94936 | Fee Based On and Fee % are not populated on Permanent Placement using an Agreement |
| When using an Agreement that has the fields 'Mark-up / Fee %' and 'Fee Based On' populated, and the Agreement is associated to a new Placement, ‘Markup % and Margin %’ were being populated instead. This has now been rectified. | |
| Tags – Placement, Agreement | |
| 97401 | Can't extend placement: Entity Key Compliance Status |
| Some users reported that they were unable to extend Placements and were receiving an error - Entity Key Compliance Status Key violated. This has now been resolved. This was a result of duplicate Compliance Status existing on the Placement. Duplicate Compliances Statuses should now appear, and we believe this to be a legacy issue | |
| Tags, Placement, Worker Type, Compliance | |
| 74712 | Fields not hiding as expected within Placement Validation |
| The Client Site Address and Client Invoice Address were showing on the Placement Validation page despite being marked as hidden in config. This has now been resolved. | |
| Tags – PlacementValidation | |
| 99916 | BFF Plugin Exceptions - Token not saving as end user |
| Some parses were failing when using Daxtra and TK for On Demand Parsing as the BFF Plugin was throwing an exception. This has now been resolved | |
| 73699 | Start Date Blank during Placement Validation despite populated |
| Start Date was showing as not populated during Placement Validation despite being populated. This is now working as expected. | |
| Tags – PlacementValidation | |
| 81775 | Unable to hide Daxtra buttons from the Vacancy entity |
| There was an issue which meant that the Daxtra buttons on the Vacancy entity were showing even where they had been set to hide. This is now resolved. | |
| Tags - Daxtra | |
| 96349 | Accept Offer - Throwing "FormHelpers" is not defined error |
| Following the sandbox and standard release of v34 a number of customers raised an issue when Accepting Offer using the older Progress Candidate(s) option where an error message was displayed to the end user and the placement creation notification will not fire although the placement was still created. This is now all working as expected. | |
| Tags – Vacancy | |
| 96496 | Candidate Pay missing on Placement UCI form |
| The fields for Candidate Pay on Temporary Placements were not showing on the Placement UCI form. This is now working as expected. | |
| 97404 | No Address on Vacancy when selecting Hiring Manager |
| There was an issue on the Mercury Vacancy form where users were unable to select Client Address if the Hiring Manager was added before the Client. This has now been resolved. | |
| Tags - Vacancy | |
| 94650 | Applicant Timeline sorting by CreatedOn |
| On the Applicant records the timeline sort order was set to “Modified On” rather than “Created On”. This has now been changed. | |
| Tags – Applicant | |
| 99986 | Shortlist Timeline sorting by CreatedOn |
| On the Shortlist records the timeline sort order was set to “Modified On” rather than “Created On”. This has now been changed. | |
| Tags - Applicant | |
| 99987 | Contact Timeline on Applicant & Shortlist sorting by CreatedOn |
| The Contact Timeline on Applicant & Shortlist timeline sort order was set to “Modified On” rather than “Created On”. This has now been changed. | |
| Tags – Applicant, Shortlist | |