← Back to Help Centre

It will now be possible to parse the job specification document to create a new Requirement.

What this means for you:

• If you have a documented job spec, you will be able to either drag and drop the file on to the 'Parse Requirement' option on the left navigation menu or from the Quick Create 'plus sign' (top right), select 'Parse Requirement'.
• When the parsing process has completed, similar to Candidate and Contact parsing, you will be taken to a Summary page which lists the values that have been parsed and shows you the relevant fields.
• The parsing process will attempt to assign the Company automatically, but you will also be able to lookup the Company and Contact yourself.
• This includes auto skilling based on the Job Specification (including skill alias matching).
• If you are happy to create the Requirement, press 'Save'.

How do I enable this:

• This feature will be enabled by default
• For Administrators who wish to disable this feature, there is a User Group Permission > View Requirement Parsing > 'Allows a User to view "Parse Requirement" on the Navigation Menu'

This release will enable the option to convert a Candidate Search Result into a Placement Search Result, which lists all of the associated Placements linked with the selected Candidates. Likewise, a Company or Contact Search Result will also be able to create a Placement Search, consisting of the Placements linked to those records.

What this means for you:

• When in the main Search area of Colleague and reviewing a Candidate, Company or Contact Search Result, it will now be possible to select a number of records (or select all), then from the 'Selected Records' toolbar menu option (or right click menu), choose to 'Create Placement Search'
• This will take the User to a Placement Search Result, listing all Placements associated to those records.
• A User can then edit the criteria of the Placement Search Result to filter the Placements using additional criteria.
• There will also be a 'Go Back To Search' option in the toolbar to return to the original search result.

How do I enable this:

• This will be a standard feature enabled for all Users

Our standard reports have now all been updated with an 'All Licenced Users' tickbox under the Users dropdown parameter.

What this means for you:

• If you wish to report on all the licenced users on the system, you will now only need to tick this box.

How do I enable this:

• This will be enabled for all standard reports

In response to recent Developer enhancement requests, our API has been updated with several new calls.

Social Media Links - in addition to the ability to create Social Media Links (LinkedIn URL), you can now also Find Existing, Update Existing, and Delete Social Media Links.

Requirements - when searching Requirements, it will now be possible to search over custom fields. The search will now also support a Job Title split function in the API call ("splitJobTitle": true). This will look for all references of the searched job title, for example searching on 'IT Manager' would find 'IT Support Manager' or 'Manager of IT Department' or 'Company IT Manager' (rather than the previous 'Exact Match' technique).

Placements - the API will now support the search and retrieval of Placement data. This uses the same advanced search technique as available for Candidates, Companies, Contacts and Requirements.

All API updates will be deployed alongside this latest Colleague release.

Following this release, it will be possible to enable Offers on a User Group Permission basis rather than being a system wide setting.

Offers are an optional stage to the booking process. This creates an Offer record that a User can then Reject or Accept to create a Placement. This is often relevant for Permanent teams, but less relevant in Temp/Contract teams.

What this means for you:

• Previously when you enabled or disabled Offers it was a system wide setting for all Users.
• If your Users are divided into Perm and Contract teams, it will now be possible to configure their User Groups so that one set of Users will use Offers when making Placements, and the other will be able to bypass Offers and go straight to making Placements.

How do I enable this:

• There is still a Global Setting under the 'Offer' section called 'Enable Offers'. This is a 'catch all' setting to turn on and off Offers for all.
• There is then a UGP specific setting, within User Group Permissions > Enable Offers > 'Grants the ability to Use Offers in the System' - set to Full Access to enable Offers for that User Group (or 'No Access' to bypass Offers)

Following the release, Users will now be able to edit a Social Media Link URL. When on a record, from the 'View More' menu > select 'Social Media Links', you will notice there is now an 'Edit' column added to the table. Click on the pencil icon to edit the Social Media Link:

In line with UK legislation, there is now an 'IR35 Status' field added to the Requirement. This is a lookup field and can be updated via the Lookups area in Admin. By default, the lookup will include:

• Inside
• Outside
• N/A

The field will only appear on Contract and Rolling Contract Requirements, Offers and Placements.

There is now a Global Setting to set whether the 'Potential Value' field on the Requirement auto calculates based on Revenue or Margin.

If based on Revenue (i.e. Charge Rate * Duration): Charge Rate £200 daily, 12 week contract (5 days/week) = 200 * 5 * 12 = 12,000.

If based on Margin (Charge Rate - Pay Rate): Charge Rate £200 daily, Pay Rate £100 daily, 12 week contract = (200-100) * 5 * 12 = 6,000.

The Global Setting which sets this feature will be under the 'Requirement' section: 'Calculate Potential Value As Revenue' Yes/No. All existing data will remain as entered (unless requested otherwise).

There is now an additional 'Click to Dial' prefix Global Setting for the Mobile UI of Colleague. This is to support the setup of ensuring calls made via the Colleague Mobile UI go via Teams or an installed application on the mobile device, rather than via the mobile operator. This will support the upcoming Teams integration, which Colleague are working on.

With MS Teams being the example, to ensure all calls made from the Colleague Mobile UI go via Teams, within this Global Setting you would enter: https://teams.microsoft.com/l/call/0/0?users=4:

Further to the introduction of the 'Attach Spec CV' option on the email form (when emailing a Contact record), after you have selected to 'Attach Spec CV' and looked up a Candidate record, it will now automatically attach the Candidate's Default CV:

An issue was raised when creating new addresses via the Placement record, resulting in the Address ID not being assigned to the Address Table. This has now been resolved.

Further to updates made to the Users table, the Portal user creation process was generating an error. This has now been resolved.

When creating a new List via a Search Result, returning to the Search Criteria and then going back to the Search Results, the new List was not available on the 'Add to List' dropdown. This has now been resolved and has been updated throughout the system to ensure new Lists are added dynamically to the lists dropdown.

Issue with the 'Scan Document' feature failing to find skill aliases has been resolved.

An issue which would cause GDPR notifications to be delayed or fail to appear has now been resolved.

When creating an interview and editing the participants, the history that is added afterwards was not including the additional participants. This has now been resolved.

When creating a new Company, if you copied a valid website address into the Company website field, it would bring back an invalid web address alert due to an automatic 'on change event' edit that the field undertakes when the address is not empty. This has now been resolved.

If a Candidate has two addresses and the User deletes the Primary address without setting the other as the new 'Primary', an error will occur when loading the Candidate record. This has now been resolved.

Following performance enhancement work undertaken on the Contact record for optimal loading time, an unintended side effect was that we broke the 'Apollo' integration when on an individual Contact record. This has now been resolved.

The Company Selection screen search has been updated to accommodate 'accented' characters (such as á, é, í, ó, ú). These were previously being reverted to QWERTY alphanumeric characters (i.e. a, e, i, o, u) and so failing to find the Company record, if it contained an accented character. The same fix is in place on the other selection screens and the Quick Search.

It was raised that when running an Offer or Placement Selection Screen search and choosing to edit the criteria, the 'Placed By' or 'Offered By' User field would get pre-populated with the Current User in error. This has been resolved.