October 2021 Impact Release Guide

A guide for administrative users on any changes that may impact their team

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 intended to provide 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. This release is tentatively scheduled for March 8th.

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.

This release will contain two improvements and changes. Select the link below to jump to a change.

Form Requests - Improved


Form Requests



Applies To

All Users that have previously used Crelate's Form Request feature

Action Required

Discuss impact to team. Form Requests with attachments will now save as a separate attachment outside of the Form Request.


Business and higher

Previous Behavior

When a form request is sent and asks the contact to upload documents as part of the request, the current behavior outlines that only the Form Request will be added to the contact record via the Document Trays.

Then, to review any documentation included within the Form Request, customers may open the request to review any attachments that may have been included. The attachments will not separately be added as unique documents within the contact record.

New Behavior

With our October release, you'll notice any document uploaded by a contact in a form request will display in the activity feed and within the Document Trays. You'll see below, the Form Request (#1) and two attachments all display within the Document Trays.

Indeed Job Location Posting - Changed


Published Jobs to Indeed



Applies To

All users that have posted jobs to Indeed containing a blank city & state

Action Required

Review published positions to ensure those shared to Indeed contain a city & state.



Previously, Indeed allowed jobs that did not require city & state information. Meaning customers may have had jobs with blank city & state fields that Indeed will no longer accept. This change was learned of and implemented via Indeed in early September 2021. Crelate recommends as a best practice, to always add city & state information and to leverage Indeed's Remote Posting Experience for any job without a unique city & state (or with multiple). Administrative users may wish to review posted positions to Indeed to ensure jobs contain both city and state data.

What's Next?

Looking for more on our October release? Look no further than our full October Release Guide!

Did this answer your question?