Linda received an email from Frisbii informing her that a new version is available. She also attended a webinar where exciting new features were presented. Linda is looking forward to this new version which will save CloudKicks employees a lot of time!
The update process is as follows: Frisbii customers who previously created a request (evolution or correction) processed in the new release are contacted as a priority to perform the update. Linda is not in this case, but as one of the new features would be very useful, she is writing to the Frisbii support team to have her organisation updated as soon as possible.
The Support team then explains the different steps to carry out the update in the best conditions.
1. Creating a sandbox
Updating the Frisbii application may sometimes require numerous adjustments, especially if the version you currently use is old. Examples of adjustments:
page layout
automations
rights
reports & dashboards
picklist values
This update must therefore first be carried out in a sandbox, to test the correct operation and avoid any blocking of the production during the process. You need to generate a sandbox whose configuration is identical to your production.
Important: please generate a "full" or "partial" sandbox which will save you a lot of time and give you real data on which to perform your tests. They will be more reliable.
Salesforce documentation for generating a sandbox
Note:
Even if you are not using Frisbii in production it is important to go through a sandbox first. Frisbii has automations on Salesforce Accounts and Users. We have normally taken all possible measures to prevent Frisbii from interfering with normal Salesforce usage, however as the problem has already occurred we recommend, as Salesforce says, that you always install an application or its update in a sandbox for testing.
2. Grant access to support and inform the Frisbii team
Please give us support access (1 week or more) and inform us by replying to the support email as soon as the sandbox is generated by providing its org ID.
Procedure to give us access and find the org ID Frisbii Support - Grant access to your org for the support team.
3. Update of the sandbox by Frisbii
Once the sandbox is created, we install the latest release. This step is subdivided into four operations on the Frisbii side:
Pre-update checks
Update by deployment from our package organisation
Addition of new features and post-update controls
Informing the customer of the completed update and the changes made
Depending on the number of releases between the currently installed release and the target release, these steps can be significantly longer and take up to several days. Frisbii is working to ensure that these release gaps are kept to a minimum in the future.
4. Testing of the sandbox by your team
You test the correct functioning of the application in the sandbox, and inform us of any malfunctions on Frisbii Community so that we can correct them.
These tests should be as complete as possible to avoid discovering anomalies when in production. It is therefore necessary to test your entire business cycle with the different user profiles, from the creation of an account/contact to the renewal of a subscription, via an opportunity. Please follow this article: Testing your environment following the Frisbii release upgrade.
5. Validation of tests
Once you have carried out all your end-to-end tests with different profiles, from the creation of an account to the dunning of an invoice, and once these are conclusive, please indicate to support that you are validating the sandbox update.
Warning: if a problem is detected in production when it should have been detected in the sandbox, support will be charged to unblock you.
6. Updating your production org
Once the sandbox has been validated on your side, we will update your production org.
For the best adoption of your collaborators and to take advantage of this update, it is recommended to prepare documentation on the use of the new features with screenshots made on your environment.
We recommend this excellent trailhead module on user adoption: Salesforce adoption strategies.
7. Patches automatically deployed
We test our new releases as much as possible before deploying them, but the very wide diversity of our customers and configurations does not allow us to anticipate everything. Thus, it happens that releases are corrected by patches following reports of problems in sandbox or production. As soon as a patch is made and tested by us, there are two cases:
The patch is important (necessary change in operation): we therefore wait for the feedback from the customer who reported the problem before pushing the patch to all customers with the same release and informing them of the changes.
The patch is not important (correction of a problem that does not change the behaviour of Frisbii): we will push the patch to all organisations that have received the latest release of the application.