First of all, the version naming has changed. Stages release 26.1 is the successor version of Stages 7.12.

Please note, that Stages 26.1 is not yet a Long Term Support (LTS) release, but will become LTS later this year. Until then, Stages 7.11 will continue to be the LTS version.

The main feature of Stages 26.1 is that it uses a completely new backend platform. End users should not notice any differences, but modelers will benefit from faster data transfers, e.g. during process version creation or process module updates. Also, the new technology platform allows us to release future product innovations quicker than before.

Release 26.1 is currently only available for Stages Managed Service instances. On-premise usage will be made available later this year.

When process modules are integrated into other workspaces or whole processes are copied into new workspaces, the creation of process interfaces is now solely controlled through workspace collections. Only processes in any workspace collection of the current workspace are being searched for potential process interface target elements. If a target is found in multiple workspaces, multiple associations are being created.

The handling of process interfaces via workspace groups and common element workspaces has been removed.

As a result, process interface creation should be much more consistent and transparent.

Multiple SAML IdPs can now be configured. Upon first login, the users have to select the respective authentication provider.

Custom attributes that were never set and have no default value in the meta model will now return null in the facade API. Previously, an empty String was returned.

Dates are now shown consistently with four digit years throughout the whole application.

Config property “operation.list.filter.types” has been renamed to “operation.list.exclude.types”.

TBD: are there other changes in config.xml, etc.? Multiple SAML IdPs?

TBD: Multilanguage support via export/import.

This will be supported in a future release.

Scripting changes (e.g. for reports, visualization scripts, etc.):

• Variables asCurrentUser, currentMetric, currentFolder, currentCollector were removed and should be replaced by TBD
• Type org.apache.commons.collections.map.MultiKeyMap is not supported anymore and should be replaced by TBD

User authentication:

• LDAP synchronization: user authentication should be performed through Single Sign On via SAML
• SPNEGO/Kerberos and PKI SSO: was already deprecated in version 7.11, code has now been removed. Should be replaced by SAML SSO.

ZIP import support:

• ZIP exports that were created with versions prior to 7.6.1.0 cannot be imported anymore.

Database support:

• The minimum supported MySQL version is 8.0.1.

Stages V6 features:

• V6 style deep links are not supported anymore.
• V6 legacy element types (Article, Category, Ypuser, Orgunit, Resource) and associations of these elements will be deleted from the database during upgrade.
• The “mandatory flag” for core process elements, which was only available through explicit configuration, has been removed.

tbd

tbd

In addition to new product features, we also made new reference models available to manage compliance.

Please reach out, if you are interested to use one or more of the following standards in Stages.

TBD

See here for the full list of available reference models.

Please let us know if you have additional compliance requirements. Our teams are ready to implement them for you.

Version 26.1 is currently only available on Stages Managed Service instances. On-premise usage will be made available later this year.

Please contact our customer care team to request an upgrade of your Stages Managed Service instance.

For topics marked with *: please contact your product consultant for more info on how to integrate those enhancements into your configuration.