The Salesforce Winter '20 release is quickly approaching, and a key update will require our customers to take a few minutes and update their permissions. Salesforce follows a “secure by default” approach, which includes platform updates. Like many other Salesforce AppExchange apps, the upcoming release will impact our Composer and CQG customers, requiring additional user-based permissions for third-party applications.
What does that mean? It’s time to update the default access to Customize Application user permissions!
But don’t worry, we’re here to guide you through these necessary updates to ensure your success. Our global customers can stay ahead of this update with the resources available, and by following our recommendations.
Brian Farr, our Director of Product Management, is here to answer some of the most pressing questions related to this critical update.
Give me the rundown. What should I be looking for in the Salesforce Winter ‘20 release?
Salesforce is enforcing the user permissions for customize metadata access. In fact, some orgs are having this update auto activated as early as January 2nd.
Why are Conga customers impacted?
This change impacts the way that Composer and Conga Quote Generation completes the OAuth process. Meaning, orgs that haven’t given their Composer users read access to the customize metadata for Composer will receive an internal server error when those users attempt to generate a document.
Important note: Customers using using versions of Composer preceding Composer 8.149 do not require the custom metadata referenced, and no further action is required.
Not sure which version you're using? You can find your version by following the steps outlined in this article.
When should customers make these updates?
We recommend making the update as soon as possible. Waiting until January 2nd will likely cause issues that can be avoided by updating now.
How do I update my Conga user permissions?
If you prefer to manage your user permissions by creating your own custom permissions, you can follow our steps outlined here to create the correct permission set to assign to Composer users.
If you’d prefer to assign permission sets that are included as part of the Composer managed package, you should upgrade to our newest package (available 12/18) and be sure to grant each Composer user the pre-packaged permission set.
You can also follow our step-by-step guide here.
Are there any resources I can use to help guide the process?
Yes! We’ve put together several different resources that can help take you through updating your permissions, from technical support articles to a step-by-step instructional video (found below). You can access them here: