FAQ for Upgrades
The following sections list the FAQs for Push Upgrades and Manual Upgrades:
Push Upgrades
1. The Release Schedule page shows a GA date. What does it mean for the push upgrades for the Asset 360 package?
The GA date represents when the new Asset 360 package is available. However, no push upgrade happens for any org before the Sandbox push upgrades. Push upgrades for Sandbox orgs begin on the date mentioned in the Release Schedule page under the column Sandbox, and then for the Production orgs.. If you want to upgrade to the new package before the mentioned push upgrade schedules, you must create an Upgrade case in the Support portal after the GA date. Log in to ServiceMax Community, and then navigate to Support > Case Management > Asset 360 > Upgrade Case to create an upgrade case.
2. Can I opt out of the push upgrades?
No, there is no opt-out option from the push upgrades.
3. Can I exclude any of my Sandbox orgs from the push upgrade cycle?
Although we expect to include all of your Sandbox orgs in the push upgrade program, you can log a case with the Support team to exclude up to two Sandbox orgs initially. These excluded Sandbox orgs remain with the same version as that of the Production orgs for testing purposes.
 |
The excluded Sandbox orgs will be upgraded to to the new release in the final push upgrade cycle when the Production push upgrade is scheduled.
|
4. I see there is a window of time of a few days for the Sandbox orgs to be push-upgraded. On which date my Sandbox org is going to be upgraded?
The push upgrade for the Sandbox orgs is planned for three days to spread out the high volume of Sandbox orgs across multiple days. The schedule is based on the Sandbox SFDC instances on which the org is running. The schedule is as follows:
◦ Day 1: CS1-CS99
◦ Day 2: CS100-CS199
◦ Day 3: >= CS200
5. At what time will the upgrades happen?
The push upgrades will be scheduled for 11:00 UTC time on the scheduled date.
6. Will I be notified about the push upgrades throughout the process?
Our Status Page is used to provide updates to our customers throughout the push upgrade process. Therefore, it is recommended to subscribe to the page to receive regular updates. Notifications are scheduled as follows:
◦ Notification will be provided on the page a couple of weeks in advance on any major release upgrades.
◦ Additional follow-up notifications will be provided through the system automatically
▪ 60 minutes before the upgrade
▪ when the upgrade begins
▪ when the upgrade is complete
7. Can I get early access to the release?
Yes, you can get your Sandbox orgs upgraded between the GA date and the first push upgrade date by creating an Upgrade case with the Support team. If you like to upgrade your production orgs early before the scheduled release date, you can also create a case for it. We prefer that this is scheduled in advance, not after the planned upgrades.
8. How much downtime can I expect during the push upgrade?
We do not expect that there will be any downtime, and customers should be able to continue to use Asset 360 during the upgrade period. The upgrade process for all orgs is expected to take between 60 – 90 minutes, but each org upgrade will typically take about 20–30 minutes. As per Salesforce general guidelines, it is recommended that customers do not carry out any other migrations or deployments during this time.
9. Will push upgrades be done for both major releases as well as patch releases?
Push upgrades for patch releases will not be completed before the A360 11.0 release. If you have an issue, raise a Support case. If it is a defect that requires a patch, you can receive the installation link for the monthly patch either through the Support case. Else, you can raise an Upgrade case to receive it.
10. How do I get added to the email distribution for notifications sent out to customers about the push upgrades?
The advance notification on the push upgrade is sent to those customers who are currently set up as Support Portal users for the Account. For receiving the notification during the upgrade process, see the above questions for the related answers.
Manual Upgrades
1. Is running the Auto Configurator a must after an upgrade?
Yes, running the Auto Configurator is a must after an upgrade. You can do it manually by navigating to the Asset 360 Admin screen after the package upgrade is complete. For more information, refer to Auto Configurator.
2. In which scenarios should we run the Post Install manually with the Override flag?
In case of a fresh install, you do not need to run the Post Install manually. In case of an upgrade, only the new configurations are installed by default. If you need the changes that we provide with any existing configurations, you should run the Post Install manually with the Override flag as True. This operation overrides any changes to any standard configurations you might have made.
3. Is there any challenge upgrading from Winter '21 to Summer '21 or Winter '22?
No, there is no limitation with regards to upgrading an Org with an A360 package to a higher A360 package version.
4. How to get the latest picklist values after an upgrade?
You should run the Auto Configurator to get the new picklist values that are added to the package. But, you need to manually update the picklist values whose labels are modified.