Table of contents

• Introduction

• Version numbering

• What is versioned

• Obtaining the version number

  • Service Studio

  • Integration Studio

  • Platform Server

    • Platform Software

    • Metadata (database) & Service Center

    • LifeTime

    • System Components

Introduction

In the context of a support case, it is required that one provides information on the version and revision of the OutSystems Platform being used.

This post explains how to obtain such information from the system, in any of the components.

Version numbering

Versioning in OutSystems is identified by 4 sets of digits in the form of M.m.b.r. These represent:

• Major version number and minor version number together represent a version of the OutSystems Platform. Together are also intended to exactly match a Marketing version of the product, even if with a different name;
• A new release is issued whenever a complete package is distributed with significant improvements to current functionalities but without breaking the existent features. An update to a new Release forces keeps the compatibility with the previous release, as long as the Major and Minor don’t change, so it does not introduce breaking-changes with previous releases, and does not force an update to all components of the OutSystems Platform;
• A new revision patch indicates an update to the OutSystems Platform that introduces bug-fixes or minor improvement to features. A new revision patch does not introduce breaking-changes with previous revisions, and does not force an update to all components of the OutSystems Platform.

What is versioned

In the OutSystems Platform, versioning exists for:

• The development tools (Service Studio and Integration Studio);
• Platform Server, at three levels: the version of the Software (installer), the version of the metadata (database), System Components, Service Center and LifeTime;
• Components (eSpaces, Extensions, Solutions).

 This versioning implies that:

• The development tools (Service Studio / Integration Studio) can only connect to a Platform Server that runs the same Major.Minor (M.m are equal);
• All versioned components within the Platform Server must be running the same revision (M.m.R.r are equal);
• All components that are published in a Platform Server must have the same Major.Minor (M.m) as the Platform Server where they run;
  • When publishing the components they will be compiled with the current Platform Server revision, so if the components don’t show information that have been compiled with the current Platform Server revision, it means that they haven’t been published since the last revision update, causing possible inconsistent states.

• The development tools can open components which are in a Major.Minor (M.m) equal or lower to the one of the development tools:
  • E.g. Service Studio 9.0.0.23 can open an eSpace last saved in version 8.0.1.23;
  • Opening a component of an earlier Major.Minor will be upgraded. This operation is not reversible – components cannot be downgraded!
• A Platform Server running in a given revision cannot be downgraded to an earlier revision:
  • From the moment the Metadata is upgraded, the only way back is by restoring a database backup.

Obtaining the version number

Service Studio

You can obtain the version of Service Studio under Help -> About and check the numbers that appear on the popup that just opened.

Integration Studio

You can obtain the version of Integration Studio under Help -> About and check the numbers that appear on the popup that just opened.

Platform Server

Platform Software

You can obtain the version of the platform installed on a server by accessing the server, and then, execute the configuration tool and go to the menu option “Help” -> “About”. It will open a popup that states which version of the software is installed. Beware that after checking this, you must close this utility without applying and exiting.

If you are in the java platform, you have to open a file that is in the root folder of your installation called version.txt and. For example, if you are using the command line and installed the platform on the standard folders, you can execute “cat /opt/outsystems/platform/version.txt” and you will see the installed version. If you are using the .NET stack this is an alternate way of checking the version because this file also exists in that stack.

Metadata (database) & Service Center

You can obtain the metadata version and the service center version by logging in to service center and then, in the right sidebar, the version will be listed under the current working mode.

LifeTime

You can obtain the LifeTime version by logging in to LifeTime and then scroll down to the footer of the page and check what is written there.

System Components

You can obtain the system components version by going to Service Center and then, in the “Factory” menu, go to the “Applications” sub-menu and filter by “System Components”. You will see in the description of the filtered application the installed version.

  

And if you want to confirm the specific version number of one of the system components, just enter the details of the application - each component is listed and has its own version number in the description.