Overview

When new versions of our PaaS platform are released, it is crucial for our customers to understand the upgrade process to ensure a smooth transition. We strive to provide a seamless experience, minimizing testing efforts and potential side effects.

This article outlines the key steps and considerations for upgrading your Cloud environments when a new version is launched. It is intended for customers managing all their environments on the Bizagi PaaS platform.

Release Cycle and End of Service Policy

Our company generally releases two versions per year—one in Spring and one in Fall—though this schedule can vary. To maintain optimal performance and security, customers must upgrade within 18 months of a version's release, in accordance with our End of Service (EOS) policy. After this period, the PaaS will no longer receive technical support, updates, or patches for that specific release.

The Upgrade Process Overview

The upgrade process is designed to be straightforward and manageable.

Below is a step-by-step guide to help you navigate it:

1. Coordination with Your Customer Success Director (CSD)

Before requesting any upgrades, coordinate with your assigned Customer Success Director (CSD) to determine the desired upgrade dates. This ensures proper planning and resource allocation.

2. Upgrade Downtime Considerations

Upgrades cause a small amount of downtime in the target environment. We strongly recommend scheduling these procedures during non-working hours and planning effectively.

Downtime Estimates

•Development upgrade from 11.2.5 or Fall 2022: 8 hours

•Development upgrade from Spring 2023 onwards: 1.5 hours

•Test and Production environment upgrades: 1.5 hours

3. Sandbox Testing (Optional)

We offer a 30-day optional Sandbox environment where your Development environment is restored to allow for thorough testing of the upgrade, as well as the new features and enhancements in the version. During this period, the Sandbox is free of charge. After 30 days, continued use incurs a monthly fee.

The Sandbox environment is provisioned in a different subscription, separate from your actual Development, Test, and Production environments, enabling effective regression testing without impacting live systems.

You can request deletion of the Sandbox at any time after the 30-day period.

4. Requesting the Upgrade

Customers are autonomous and responsible for requesting upgrades for each Cloud environment. Bizagi manages the upgrade process once requested.

For each environment upgrade, create a separate Support ticket specifying the environment, along with the preferred date and time for execution. Make sure you have previously agreed on dates and times with your CSD.

The first mandatory step is to upgrade your Development environment (or environments if you have multiple projects). Once the Development environment is tested and confirmed, request an upgrade for your Test environment via a separate Support ticket. After the Test environment is approved, submit a request to upgrade the Production environment, which completes the upgrade process.

5. Testing and Validation

The testing period is flexible and depends on the depth of testing or validation required by your organization. If any issues are discovered during testing, a separate Support ticket should be submitted for each problem, allowing our team to address them promptly.

Changes in Upgrade Process for Fall 2024 and Beyond

For versions released before Fall 2024 (including Spring 2023 and earlier), all Development environments across all projects are upgraded simultaneously.

Starting from the Fall 2024 version, customers with multiple projects can upgrade environments independently, including the Development environment. This provides greater flexibility in managing upgrades based on project-specific needs and timelines.

Frequently Asked Questions (FAQ)

•How do I know the version that I need to upgrade to?

You can upgrade to the latest version released by Bizagi. Check our Release Notes portal for all new features and enhancements.

•Are there any costs associated with the upgrade?

While the upgrade itself may not incur additional charges, changes in our pricing model could impact the renewal process. We recommend reviewing your renewal terms for any adjustments in pricing. For further questions, please contact your Account Executive.

•What happens if I have a VPN and require a Sandbox?

Since the Sandbox is created in a new subscription, we will need to create a subnet in the existing VNET (VPN). We will share the necessary information so you can add it to your encryption domain (whitelist). Once the Sandbox is created, we will notify you to authorize the subnet.

•Does the Sandbox have any cost?

Bizagi provides a Sandbox free of charge for one month. After 30 days, the Sandbox will be charged per monthly usage.

•When should the upgrade be done?

The timing of the upgrade depends on customer availability and scheduling with the Bizagi team. Contact your CSD to obtain detailed information.

•Is there any risk of data loss during the process?

No, Bizagi takes all necessary measures to avoid data loss. Our team keeps a backup in case a rollback is required.

•Which environment do I need to upgrade first?

You must update the Development environment(s) first, followed by the Test environment(s), and lastly the Production environment(s).

•Is there any downtime during the process?

Yes, during the actual Development, Test, and Production upgrades, there is downtime. Expect approximately 1.5 hours per environment.

•Will there be any changes in the URL for the Work Portal?

No, the URL remains the same.

Conclusion

Upgrading to the latest PaaS version ensures your systems stay secure, high-performing, and up to date with the newest features. By following the outlined steps and coordinating closely with your CSD, you can streamline the upgrade process and minimize potential disruptions. Should you have any questions or need assistance during the upgrade, our Support team is ready to help.

Last Updated 8/27/2024 4:57:35 PM