Skip to main content

Release 5.369 // 25 January 2025

Placements | My Assistant | Candidate Reviews | CV Extraction | Tables

Updated over 8 months ago

📈 Placements in My Assistant!

From now on, you can also create an overview of your placements in My Assistant. Instantly see the number of placements per status and adjust where needed. Get a quick and easy visual reminder when a placement is nearing its end. One month before the end date, it will turn red as a reminder that an extension might be necessary. You can also easily edit basic information, such as start and end dates, directly from the preview.

With the introduction of placements, we are also adding a new recommended action to the matches in My Assistant: easily create a placement for successfully completed matches in your match funnel.

🤖 Minor Improvements and Bug Fixes

Every release includes minor improvements and bug fixes that enhance performance and user experience. Not all changes are visible to the end user. If the release contains updates that directly impact the software’s behavior and user experience, they will be briefly explained below.

  • Adjustments for the sort order of the candidate rating in My Assistant. Previously the non-rated records prevailed above the highest rated when sorted in descending order. This was revised.

  • When using pagination in the preview of My Assistant, you now have the option to save any changes you make when clicking the arrow to go to the next file. Previously, you only had the choice to discard your changes and proceed to the next file, or to return to the preview and save the changes using the Save button. After saving, the preview would close, and you would return to the overview instead of being directed to the next file.

  • The renewed CV-parsing flow now also is applied when starting the extract procedure from the attachment tabs.

  • A fix is applied preventing some document templates / legacy reports from not functioning.

  • Modifying any field of a datanode now should result in updating the modification date of that datanode. Previously changes to the name (in different languages) for example did not trigger an update of the modification date.

  • For a future change with regard to the displaying of the total amount of matches on jobs or candidates a new database column is introduced on the job and candidate entities.

⚠️ Please note: this will affect the Carerix Datasource product as follows:

  • Table CRVacancy and CREmployee get the following new column:

    • MATCH_COUNT

Did this answer your question?