Apply critical updates
Apply critical updates
This is for:System Administrator
A critical update is an important change in the features of Coveo that may require extra validation steps or manual configuration in your organization. Most importantly, a critical update gives you the ability to decide, for a given time frame, the most favorable time to apply the update to your organization.
Conversely, non-critical updates are automatically applied to Coveo since they don’t require any action on your part.
With the Critical Updates (platform-ca | platform-eu | platform-au) page, you have the opportunity to proactively apply a critical update in order to test it and take the required actions to adapt your organization before this update officially becomes part of Coveo.
Testing updates in a sandbox organization or during off-peak hours is recommended.
When a new update is available on the Critical Updates page, Coveo informs organization administrators by email (see built-in groups). It’s then the administrators’ responsibility to activate the update in a sandbox organization to test it (see About non-production Coveo organizations). Once they have checked that the update doesn’t affect their organization customization, they can activate it in their production organization. Regardless of whether administrators test it, a critical update will eventually become an official feature of Coveo and be automatically activated for all organizations. At this point, it will then no longer be possible to deactivate it manually from the Critical Updates page. For more information on this process, see Critical update test process.
Activate or deactivate a critical update
Updates apply to your Coveo organization shortly after their manual activation. You can activate an update temporarily for testing purposes or, when you find the update satisfactory, you can activate it to start benefiting from it without waiting for its official release.
Deactivated updates don’t apply until Coveo officially releases them. Once it does, they can no longer be deactivated, and their status becomes
Click Activate or Deactivate to confirm.
Critical update test process
The following is an example of a workflow taking place at your company when a new critical update is available.
As a Coveo organization administrator, you receive an email informing you of the availability of a new critical update.
You read the message and the documentation relative to the critical update.
You define a testing plan for the update and inform your coworkers of the upcoming changes.
You activate the critical update in your sandbox organization, which is your test environment.
Should an issue be identified, you take steps to fix it. You can seek help from the Coveo Support team. While working on a solution, you can deactivate the update in your sandbox organization (see Activate or deactivate a critical update).
Once you fixed your sandbox organization, you can test it with the critical update activated again.
When satisfied with the test results, you apply your fix to your production organization. You can then activate the update in this organization as well.
Coveo officially releases the update. If the critical update isn’t already activated in your production organization, it’s automatically activated, and you can no longer deactivate it. If you manually activated the update, the permanent activation has no effect on your organization other than preventing you to deactivate this update.
|Action||Service - Privilege||Required access level|
|View the list of updates||
Organization - Critical Updates
Organization - Organization
|Activate/deactivate updates||Organization - Organization||View|
|Organization - Critical Updates||Edit|