Cloud Talent Solution release notes

Add a RelevanceThreshold field to the SearchJobsRequest to filter results by precision.

Improve address resolution for LocationFilter with region code.

Adds MAX_THREE_PER_COMPANY DiversificationLevel option.

Jobs with commutable city-level locations are returned when allowImpreciseAddresses is set in CommuteFilter.

Jobs with matching nation-level locations are boosted for telecommute searches.

Added support for more MOC codes.

Marking company_size histogram facet as deprecated.

Marking keyword_searchable_job_custom_attributes on the Company as deprecated. Moving forward please use the keyword searchable tag on the Job.CustomAttribute to specify keyword searchable.

Extend the functionality for the inferred remote location filter to respect the region code

Histogram query for city and admin1_country can handle multiple location jobs

Support special characters in companyDisplayNames fuzzy match

Derive annualized compensation info for more employment types

Deprecate option TELECOMMUTE_EXCLUDED under enum TelecommutePreference

Add a new operator on companyDisplayNames filter to further support fuzzy match by treating input value as a multi word token

Add a new option TELECOMMUTE_JOBS_EXCLUDED under enum TelecommutePreference to completely filter out the telecommute jobs in response

• Jobs within same state will rank higher in results when search jobs in a state level location with TELECOMMUTE_ALLOWED option

• keywordSearchable will be returned correctly in Job instance responses
• Fix compensation histogram query to return correct histogram result

The Cloud Talent Solutions dashboard management tool has added a Jobs and Companies page, which displays job statistics and metadata. You can use this page to troubleshoot data issues. The Jobs and Companies page has three tabs:

• On the Summary tab, see the latest job count snapshots and a visualization of job count statistics over time.
• On the Job Metadata tab, search for specific jobs and their available metadata.
• On the Exports tab, export your metadata to a BigQuery table for further analysis.

For more about this new feature, see the Jobs and Companies data documentation.

Added functionality in the companyDisplayNames filter to support fuzzy matching.

Fixed a bug with certain DIVERSIFICATION_LEVELS where results were dropped.

Improvements in spell correction.

Added a new KeywordMatchMode field to support more keyword matching options.

Added more DiversificationLevel configuration options.

Added WALKING and CYCLING as commute options in the CommuteFilter.

Removes companyName requirement for use of ListJobs API.

Increased the number of characters supported in custom ranking expressions.

Cloud Talent Solution has launched the v4 version of the API. Migrate to Cloud Talent Solution v4 by October 14, 2021 to continue using Cloud Talent Solution.

As of today Cloud Talent Solution versions v3, v3p1beta1, and v4beta1 are deprecated. Deprecated means that these versions will continue to work until October 13, 2021, at which time these versions will be shut down. Migrate to Cloud Talent Solution v4 by October 14, 2021 to continue using Cloud Talent Solution.

When using orderBy to order job search results by distance_from from the search location, equidistant jobs from the center of the search location will be tie-broken based on each job's relevance to the search keywords. Previously, jobs in this scenario weren't primarily tie-broken based on each job's relevance to the search keywords.

When using the EmploymentType as part of HistogramQuery, facet counts for CONTRACTOR no longer also include facet counts for CONTRACT_TO_HIRE.

HistogramQuery facet counts no longer differ from the number of jobs returned when filtering search results by a given facet.

CTS has made improvements to the handling of accented characters and gendered terms in job titles and search keywords.

Cloud Talent Solution's consumption pricing and quota limits will change effective January 4, 2021. The new pricing and quota limits are intended to better address the variety of use cases the talent industry has for managing and searching for jobs.

As of this date, Cloud Talent Solution Job Search v2 is no longer available. Calls to v2 will result in error. The deprecation of v2 was first communicated in August 2018.

CTS has launched a new dashboard management tool. This new improvement provides visual data to give you more insight into:

1. How your job seekers are engaging with Job Search, by showing see top queries and locations by domain.
2. Whether Job Search is properly configured for your application, by showing inconsistencies in your search API integration.
3. Whether your client events are properly configured, by showing client events that you can correct or improve to take full advantage of Job Search's machine learning capabilities.

JS has improved the algorithm for better street resolution coverage. This will give you more precise geolocation results when using commute search.

The following fields have been added to SummarizedProfile:

• group_id
• application
• assignment

Bug fix: Required fields are now marked correctly in the BatchUpdateJobs reference documentation.

Bug fix: CTS has fixed a bug that caused deleted companies to be counted toward the company limit in a job distributor.

JS has added new field query_language_code.

New enum CONTACT_AUTOMATED_SYSTEM has been added to ProfileEventTypes.

CTS has added validation to job.workHour.workHour now allows hour values between (0-23), otherwise a 400 error is returned.

Bug fix: Job Search has fixed an issue that caused only some jobs in a specific location to be returned, rather than all options matching the search query.

Bug fix: Job Search has fixed an issue that caused only some of the results to be returned when searching on the string "Chief accountant". All results to this query string are now returned.

All resource (Tenant, Job, Profile, and so on) Create/Update methods now return any duplicated resource names in a structured error response to ALREADY_EXIST errors.

Bug fix: CTS has fixed a bug that caused the job export tool to generate fewer results.

Job update time is now only tracked if the job was updated by a customer.

Bug fix: CTS has fixed a bug that caused information in the addresses field to be appended to structuredAddresses.

The maximum size of the customAttributes filter field of a job has been increased from 3KB to 6KB.

New documentation added: Create an expired job.

Cloud Talent Solution has launched a new Batch API.

Cloud Talent Solution has added an exception for an invalid profile name.

Bug fix: Cloud Talent Solution has fixed issues related to histogramming custom attribute facets. An empty histogram expression now throws an error message.

Bug fix: Cloud Talent Solution has fixed an issue where UpdateJob failed with a 500 error if the job's name didn't have a tenant_id.

Bug fix: Compensation filters are now able to account for jobs that have no compensation fields set.

Cloud Talent Solution has launched new Batch API calls. These calls enable you to perform multiple operations at the same time. Note that Batch API calls only apply to Job resources and CTS does not guarantee how quickly they will be reflected in search or recommendation responses.

Cloud Talent Solution fixed an issue that would not allow customers to upload expired jobs. You are now able to create an expired job and link it to any associated Application or Assignment records. When loading your historical data, input the following values:

• postingPublishTime=[timestamp when the job was created]
• postingExpireTime=[timestamp when the job was closed]
• requisitionState=[FILLED, LOST, CLOSED]

Customers can now set the group_id field with their values, rather than having to use the Cloud Talent Solution auto-generated values for this field.

Cloud Talent Solution has added validation checks on timestamp related fields on the job and profile entities.

Cloud Talent Solution has launched the v4beta1 version of the API. You can download these libraries from our Client Libraries page.

Cloud Talent Solution has updated it's documentation to include more code samples, and better structured examples on how to use the APIs.

Cloud Talent Solution now allows you to define your own group_id to identify the same candidate across multiple profiles.

Cloud Talent Solution has fixed issues causing 500 status messages to be returned due to discrepancies in the Profile object.

Cloud Talent Solution fixed issues causing the excludedJobs list in the search API to work incorrectly.

For invalid histogram expressions Cloud Talent Solution will now return a 400 response instead of a 500 response.

Fixed a bug in which jobs with multiple locations did not have any identifier between each location. Added in double quotes as a delimiter between each location.

Additional Commute Search modes: Cloud Talent Solution now supports walking and cycling modes of transit for Commute Search.

Rank by distance: Cloud Talent Solution now allows you to order search results by distance based on a specified location.

Simplified client events in v3: Simplified client events provides provides a set of APIs to implement client events in a clean, easy-to-use manner.

Increased the max characters for languageCode: Cloud Talent Solution now accepts locale strings from 10 to 16 characters.

Fixed a bug in which jobs with multiple street addresses were returning only the first address. Creating job will now return all job locations in STREET_ADDRESS type if job location is successfully resolved to street address, otherwise returning job addresses in extracted location type.

Fixed a bug which was slowing the performance of the CTS Self-Service Tools.

Diversification level available in v3: DiversificationLevel controls whether or not highly similar jobs are returned next to each other in the search results and is now available in v3 of the API.

Multiple languageCodes for auto-complete API: Cloud Talent Solution now allows you to specify multiple languageCode filters for the autocomplete API.

Cloud Talent Solution now available on APIs Explorer: Cloud Talent Solution is now available on APIs explorer. Learn more about using APIs Explorer.

Improved error messages: Cloud Talent Solution has added more context to error messages that are generated when updating the compensation information of a job.

Compensation information now modifiable: Cloud Talent Solution now allows you to modify the compensation information of a job using the updateJob API call.

Improved access control: Cloud Talent Solution has introduced stronger access control measures that give developers more flexibility to control data permissions through Google Cloud Console. See the access control documentation for more information.

New beta version: Cloud Talent Solution has launched a beta version of the API suite that now supports three additional features - custom ranking, new histogram expression and, a new Pub/Sub API set.

One-sided compensation ranges: Previously, Cloud Talent Solution required both the max and min ranges to be set while defining the compensation range. This requirement has now been alleviated.

v3 orderBy values: Previously, Cloud Talent Solution documentation suggested that orderBy values such as postingPublishTime would be accepted, but the API only accepted posting_publish_time. This has now been fixed. Cloud Talent Solution will accept both versions and also capitalized versions of the same values.

Military occupational speciality code: Cloud Talent Solution is proud to launch a new feature that enables veterans to search for jobs using their military occupational speciality code.

nextPageToken not yielding page results: In some cases, using the nextPageToken to get the next page of results yielded empty search results. This behavior is now fixed.

v3 schema: Cloud Talent Solution has launched v3 of the job search API. New customers should use the v3 schema to integrate with the API. Existing customers on V2 of the API are encouraged to migrate to the new schema as soon as possible. The v2 version of the Job Search API will continue to be supported until 8/23/2019. Most new features are only available on the v3.

Cloud Talent Solution is now generally available.

New method for tagging bot traffic: Added a BOT device type to indicate if the device used by the job seeker at the time of the call to the service is a bot.

Inability to parse keywords with non-alphanumberic characters: Previously, Cloud Talent Solution was unable to parse queries such as A.B.C.D and match them against literals in the job description field and custom attribute fields. This is now fixed.

Limit distributorCompanyId size: The distributorCompanyId field of a job now has a limit of 255 characters.

Autocomplete issues with different languageCodes: Previously, Cloud Talent Solution incorrectly parsed languageCode values in the complete API request. This is now fixed.

Cloud Talent Solution is now in an open beta.

Self-service tools launched: Cloud Talent Solution has released some self-service tools to assist with smoother integration and monitor usage of the API. Follow the directions in our documentation to learn more.

New data centers in Europe: Cloud Talent Solution has opened data centers in Belgium and the Netherlands to route traffic of European customers and reduce the overall latency of the service.

Limit autocomplete results to specific languageCode: Previously, for complete API requests, if languageCode included "en-US" Cloud Job Discovery incorrectly discarded the "US" bit and returned all jobs with languageCode starting with "en" even if the search language code had been set to "en-US". Now only jobs corresponding to the languageCode are returned.

Restriction on number of Location filters: This release restricts the number of Location filters to no more than 5.

Job expiration changes: This release extends the allowed retention period for expired jobs within the Google database from 60 days to 90 days (default) and, upon request, up to 360 days. This release also allows for updating expired jobs (including re-setting the expiration date of an expired job to a future date) and updating the expireTime field introduced in the last release. expireTime allows customers to set the format of an expiration date to a DateTime (ms timestamp) instead of a Date at 0:00 UTC. In cases where both the expireTime and expiryDate are added to a job, the expireTime takes precedence.

Quota lookup for Google Cloud Projects: Customers of Cloud Job Discovery can view the quotas allocated to their Google Cloud Projects by looking up the APIs & Services section of the Google Cloud Console. If you require more quota than has been allocated, file a ticket from our support page.

Use regionCode to specify preferred language: Cloud Job Discovery has introduced an optional search parameter regionCode to specify the preferred country in which jobs are to be found in. For example, by setting this field to UK, a location-based search for jobs in Reading would return jobs in Reading, UK as opposed to Reading, MA, USA.

Cloud Job Discovery has released new customAttribute fields on jobs. These fields work in a similar manner to the existing filterableCustomFields, with the following new features:
Define your own custom field name: The advanced custom fields allow you to define your own name for the custom fields, rather than use a specific index value (as is the case in regular custom fields)

• Case insensitive search: The search request is now able to specify if a case sensitive or case insensitive match is required.
• Support for numeric values: customAttributes can store either string or numeric values.
• Range based filtering: customAttribute search filters can filter jobs between a range of specified values. For example, if a given customAttribute field is used to store salary information, the customAttribute filter can be used to return jobs with a certain salary, jobs with a salary greater than a specified value, jobs between a range of specified values, etc.
• Cross-field filtering: Advanced custom fields also provide customers of Cloud Job Discovery with the ability to define expressions that filter a combination of advanced custom field values. For example, a customer has business logic that states they only want jobs that sponsor visas, or jobs paying more than $100K. A customer can use one advanced custom field to indicate if the job is sponsored, and another for the salary. The customer can then specify a search filter with an expression that defines the logic needed. Only 3 levels of nested expressions are supported.
• Keyword specific search: Specify a certain customAttribute in the keywordSearchableCustomAttribubte of the associated company to ensure search requests that contain a value in the specified custom field return the jobs that contain this value in that custom field.
• SQL based searches:strong> customAttributes allows you to define boolean-style expressions in the search request. Cloud Job Discovery automatically parses these expressions, applies the filters to the search request, and returns results accordingly.
• Define custom histogram buckets: customAttributesallow customers of Cloud Job Discovery to set custom buckets by which histograms can be calculated. For example, you can use a customAttribute to store salary information, and then create a histogram on the field. You can further create buckets from 10000 - 20000, 20000 - 30000, etc to group all the salaries within these buckets.

New API for Search for Alerts: There is a new Search API endpoint - searchJobsForAlerts that has been created exclusively to provide relevant job content targeted to passive job seekers (such as for email alert campaigns). This API is preferred over the current means of specifying the MODE of a searchJobs API call to EMAIL_ALERT_SEARCH. Customers can also see the quota associated with this type of search in the Google Cloud Console under the PeriodicTaskGroup.

nextPageToken throwing 500 error on broadened errors: Previously, Cloud Job Discovery was incorrectly throwing 500 errors on search requests that had the pageToken set such that the set of returned results were only broadened results ( by setting the flag enableBroadening to true). This has been fixed.

Compensation histogram change: A request to generate a histogram by compensation does not accept the same searchType to be repeated more than once on a single request.

API Schema changes: Cloud Job Discovery has added several new fields in the schema and corresponding deprecated fields in order to standardize the naming of fields. Deprecated fields have been marked "deprecated" in the schema.