Versioning: are imports backward compatible?
Comments
-
Quick question for anyone who knows,
During the upgrade process, we will have our dev environment upgraded to the newest version of decisions and our sandbox environment in a previous until we complete our upgrade of all environments.
Is it possible that workflows or decisions entities developed in the most recent version can be exported back into the previous version without any problem?[font=Roboto, Arial, Helvetica, sans-serif] [/font]
[i]edited by CryptoKat1776 on 10/21/2019[/i] -
Hi,
Exporting from an earlier environment to a later environment should not be a problem, but exporting from a later or more recent version to a legacy version may cause issues. Due to the nature of our development process, each version is built off of the prior one, so there are some changes that are not backwards compatible. There is a lot of value in staying up to date with our upgrades, to experience all of our bug fixes and new features. If you have any questions, please reach out and let us know.
Howdy, Stranger!
Categories
- 4.1K All Categories
- 61 General
- 11 Training
- 201 Installation / Setup
- 1.1K Flows
- 106 Rules
- 260 Administration
- 212 Portal
- 489 General Q & A
- 693 Forms
- 333 Reports
- 3 Designer Extensions
- 47 Example Flows
- 51 CSS Examples
- 1 Diagram Tile
- 7 Javascript Controls
- 178 Pages
- 5 Process Mining
- New Features
- 178 Datastructures
- 69 Repository
- 219 Integrations
- 28 Multi-Tenant
- 27 SDK
- 76 Modules
- 56 Settings
- 25 Active Directory
- 12 Version 7
- 35 Version 8
- 66 Lunch And Learn Questions