July 2023 Impact Guide

A guide for Administrative users to learn of upcoming subscription changes

Ian Remington avatar
Written by Ian Remington
Updated over a week ago

About this Guide

This guide is designed to help Crelate System Administrators understand the potential user impact of an upcoming release of Crelate. The guide is a shortened version of our “What’s New” documentation and provides additional insights that Crelate System Administrators should be aware of. Crelate provides this guide ahead of scheduled releases to allow Crelate System Administrators time to prepare for and take advantage of new or changing system capabilities.

Each improvement includes a description of the impact and when available, administrative options available to minimize the impact on your users.

About Crelate Upgrades

All upgrades to Crelate are automatic, benefit all users and typically require no user action. However, not all system upgrades are on by default. System Administrators may need to opt-in or opt-out of some new functionality. We know change can be disruptive and we work hard to ensure System Administrators have the flexibility to control when new features are available to their users. To minimize potential business impact, new features of Crelate are often off by default for existing customers and other features may be turned off if a customer chooses to do so. Occasionally, we make changes the behavior or look and feel of a feature. System administrators should review this guide to understand their options, any potential impacts to their users and any actions they may have to take to either take advantage of new functionality; or hide new functionality depending on their organization’s needs.

NEW – This is a new feature or functionality. It may need to be enabled and configured.

IMPROVED – This is a change to an existing feature.

CHANGED – This is an existing feature or behavior that has changed, and users need to be aware.

Features

Attachment Properties in API v1 and v2 – CHANGED

Impact

The Attachment property on Contact, Account, and Job records retrieved via bulk queries has been deprecated. It will also return an empty array now.

Severity

Low

Applies To

All API users

Action Required

For best performance and data consistency, Attachments should be retrieved using their respective core record/attachment endpoints.

SKU

All

Starting July 1st, all bulk retrieve endpoints will be limited to 100 records per page. Requests for more than 100 rows will return an error response if more than 100 rows are requested. All bulk result sets that do not specify a sort order will now sort by ModifiedOn descending.

It is advised to only retrieve attachment data for records that are actively being worked (recent within a certain threshold) and to limit the sync times.

Deprecate “What's New” in Hamburger Menu – CHANGED

Impact

The “What’s New” button available in the organization menu has been removed

Severity

Low

Applies To

All user

Action Required

Utilize the secondary “What’s New” button on the left pane going forward

SKU

All

In our last release, we introduced a new “What’s New” button on the left pane in each org. The old button that used to live in the organization menu has been removed and will no longer be available. Users are directed to use the new “What’s New” button above the Settings button.

Indeed- Email Address Required – CHANGED

Impact

Setting a publisher on all existing published jobs in Indeed, which will be the publishing user’s email address getting passed to Indeed as the job publisher.

Severity

Low

Applies To

All users that utilize the job portal

Action Required

No Required Action (read note below)

SKU

All

Starting July 1st Indeed has a new rule for job listings. They now want the email address of the publisher included in all published jobs. If you don't include it, your job will just be marked as 'Hidden' and won't show up on Indeed. To update the publisher, you can either republish the job or hit 'Reset' in the job publishing section on Opportunity Records.

For the jobs you already have listed, they'll automatically assign the publisher as the Primary Owner. And if there's no Primary Owner, they'll just go with the person who last updated the opportunity.

Mentions Setting Options – CHANGED

Impact

To mention core records and users, the user will always need to type @

Severity

Medium

Applies To

All users

Action Required

Ensure you are using the @ symbol before mentioning Core Records in activities

SKU

All

Previously, Admins had a setting option for Crelate to automatically suggest mentions for you when you type in the notes for an activity. This setting option has been deprecated and users will need to type @ when wanting to mention other users.

Old UI:

New UI:

Did this answer your question?