Release Notes

Change history by version, from the most recent to the oldest.

1.0.49

Version 1.0.49 — June 2026

Data Fabrik

UTD Production — More precise sorting of runs

The default sort order applied to runs on the Data Fabrik → UTD Productions screen has been fixed to take the full timestamp into account, now including seconds. Previously, sorting only took hours and minutes into account, which could result in a disorganized display when several UTDs were run within the same minute. This fix ensures a consistent and chronologically accurate display of runs, including after a refresh or a filter change.

Production Calendar: filtering out inactive schedules in the scheduling grid

The scheduling grid on the Data Fabrik → Production Calendar screen has been updated to include new data filtering capabilities.

• A « case à cocher » (checkbox) filter has been added above the grid, allowing inactive schedules to be shown or hidden. By default, only active schedules are displayed. When the checkbox is checked, inactive schedules are added to the data source. If a UTD only has inactive schedules, it will not appear until the checkbox is checked.
• The « Effacer les filtres » (Clear filters) button clears all filters applied to the grid and resets it to its default state in a single click.
• A quick search bar has also been added.

Dashboards - Power BI Integration

Orkestra can now display Power BI reports directly within its interface. Reports are hosted and governed in the customer's Microsoft tenant, and Power BI licenses likewise remain the customer's responsibility.

A new Data Fabrik → Dashboards page has been added. This page is not visible by default, but an administrator can enable it. On this page, the user must first sign in to their Microsoft account. They can then select their workspace and report to display it.

Data Shop

Marketplace — New screen for viewing datasets grouped by tags

As part of the ongoing improvement of the Data Shop user experience, a new Marketplace screen has been introduced in the Data Shop module. It provides an overview of tag labels, letting users browse datasets grouped by functional label.

Each tag card displays the number of associated datasets, the last update date, and the data owners. A free-text search bar dynamically filters the displayed cards. Datasets without a tag are grouped into a dedicated section titled « Jeux de données sans libellé » (Untagged datasets). Clicking a card opens a secondary page listing all linked datasets, showing for each dataset its label, creation date, owner, description, a button to download the dataset, and a button to view the dataset in Data Product.

Administration

User management — Overhaul and security

Several improvements have been made to user management in the Administration / Users module:

• For users whose password is managed by Orkestra (internal authentication), a Password field has been added to the user creation popup; the system no longer automatically copies the login as the password.
• When creating a user, the Operation type field is now preselected to Standard and the Status field to Active by default.
• Separation of Users / User templates: a new User templates submenu has been created under the Users menu. The Users grid no longer lists templates, and the template popup has been simplified (label + status forced to Inactive).
• Automatic welcome email: when a user is created, an email is automatically sent to the user's address containing their login credentials.
• Added the Custom role (specific to REF Manager), and permanently removed the AdminExploit and AdminRefs roles from the interface. Authorization policies have been updated accordingly.
• User 360° view: a side panel accessible from the users grid displays the user's full identity, their permissions (application, roles, status), and the rights matrix (rights per application). It also allows quick actions such as copying rights from a template.

REF Manager

Permissions on business reference data

Orkestra now includes a functional permissions system for the business reference data managed by REF Manager. A new role called Custom is available for REF Manager. It allows permissions to be defined per reference dataset. A new "REF Manager" tab has been added to the Administration → Permissions page to assign these permissions.

For each reference dataset, three permission levels are available:

• Reader: read-only access, viewing of records.
• Contributor: creating and editing records (includes Reader).
• Administrator: full access including deletion (includes Contributor).

Users with a role other than "Custom" (Viewer, Creator, Super Admin) retain their usual behavior. A user with no entry in the permissions table sees no reference datasets.

CRUD actions on reference datasets are also logged in the Orkestra Logs (filter [RFM]).

Supervision

Logging of connection events

To strengthen the traceability and auditability of user access, Orkestra now includes automatic logging of authentication-related events. Successful logins, failed login attempts, and logouts are now systematically logged, whether authentication is performed through Orkestra's native mechanism or via an SSO mode.

UTD Manager

UTD Manager — Renaming the "Déclaration" menu to "Gestion"

Following user feedback, the label of the UTD Manager → Déclaration menu was found to be insufficiently representative of the features it provides. It has been renamed to UTD Manager → Gestion (Management).

Platform

GDPR compliance

A set of GDPR compliance measures has been incorporated into version 1.0.49:

• Secure password hashing (BCrypt or Argon2) — GDPR Art. 32.
• Filtering of personal data in platform logs — GDPR Art. 5.

Bug fixes

• Fixed an error that could occur when sending the end-of-production email.
• The production quality chart did not display correctly with SQL Server.
• DTM References: the « Statut » (Status) and « En maintenance » (Under maintenance) columns in the FARMS and PARALLELU CLIENT FARMS tabs displayed raw values instead of the labels translated into the user's language.
• STATUSES tab: two columns shared the same « Statut » (Status) heading with no FR/EN distinction. The headers have been differentiated.
• DTM References: the generic title « Ajouter un nouvel enregistrement » (Add new record) has been replaced with titles specific to each tab's context.
• Configuration / UTD Manager - Text and translation fixes.
• FARMS: the Status column displayed the raw value "A" instead of the label « Actif » (Active). The mapping of status codes to readable labels has been fixed.
• Fixed the images displayed at the top of the page: the « Orkestra » icon appeared instead of the « Configuration » icon on some screens.
• Configuration / UTD Manager - Workers: the required-field asterisk was missing on the Server field in the worker creation popup.
• Various fixes to OIDC/SAML authentication.
• Data Fabrik: the « Lancer la production » (Start production) button remained greyed out when creating a production.
• UTD Manager: adding a server with a name that already existed blocked the interface with no error message. An explicit message is now displayed.
• Fixed a crash on the Configuration → Ref Manager page.
• Administration: it was possible to save a permission entry without an associated role. The role field is now mandatory.
• UTD Manager: missing translations in the blank-environment loading dialog when switching to English.
• Ref Manager: the "bit" column type (SQL Server boolean) was not handled and caused an error. The mapping has been fixed.

1.0.48.3

Data Fabrik

UTD Production - Visual highlighting of the comment icon

An ergonomic improvement has been made to the Data Fabrik → UTD Productions screen to make it easier to identify productions that have comments.

Previously, the icon associated with comments looked identical whether or not a comment was present. This lack of differentiation required opening each production to check for any existing exchange or annotation.

Now, when at least one comment has been entered for a UTD production, the corresponding icon appears in color (per the current visual guidelines). When there is no comment, the icon keeps its current neutral/greyed-out appearance.

This change makes it possible to immediately spot commented productions, without changing the screen's layout or adding clutter to the interface. It improves readability and helps with more efficient follow-up of discussions around jobs.

The associated tooltips remain available in French and English:

• Afficher les commentaires / Show comments
• Where applicable: Aucun commentaire / No comments

No functional change has been made to the comment management mechanism; this is purely a visual improvement aimed at enhancing the user experience.

Data Shop

Dataset view - Marketplace

As part of the ongoing improvement of the DataShop user experience, a new screen has been introduced in the Data Product module to provide a more business-oriented view of datasets.

Previously, datasets were grouped according to their technical tag value (for example: 20250219_CLT_TXC_02). While consistent from a technical standpoint, this approach sometimes made navigation less intuitive for business users.

Datasets are now grouped by explicit tag label, such as « Taux de change BCE » (ECB exchange rate). This change makes it possible to immediately understand the functional use of a dataset and to more easily identify the different versions associated with the same business scope.

The new screen presents a consolidated card-based view, showing for each group the number of available datasets, the last update date, and the associated data owners. This organization provides a clearer view centered on the value and use of the data rather than on its technical coding.

Supervision

Logging of connection events

To strengthen the traceability and auditability of user access, Orkestra now includes automatic logging of authentication-related events.

Successful logins, failed login attempts, and logouts are now systematically logged, whether authentication is performed through Orkestra's native mechanism or via an SSO mode. All of these events can be viewed in Supervision → Journaux / Logs Orkestra (Logs).

Each event is recorded using the platform's standard log model (level, timestamp, message, and any technical details), ensuring full consistency with the rest of the supervision system.

The following events are now covered:

• Successful login (Information level) — Message: Connexion réussie de l'utilisateur [UserLogin] / [UserLogin] logged in successfully
• Failed login attempt (Warning level) — Message: Échec de connexion pour l'utilisateur [UserLogin] (mot de passe incorrect ou utilisateur inactif) / Failed login attempt for user [UserLogin] (invalid password or inactive user)
• Logout (Information level) — Message: Déconnexion de l'utilisateur [UserLogin] / User [UserLogin] has logged out

Messages are automatically generated in the language of the user's session (FR/EN).

This change makes it possible to:

• improve monitoring of platform access,
• facilitate diagnostics in the event of authentication issues,
• ensure consistent auditability between standard authentication and SSO,
• and strengthen compliance with security and governance requirements.

Supervision – Renaming the "Instances ParallelU" submenu to "Workers"

In the Supervision → Journaux (Logs) module, the submenu previously called « Instances ParallelU » (ParallelU Instances) has been renamed to align the terminology with the platform's actual architecture.

To harmonize naming across modules and improve technical understanding, this submenu is now called « Workers », in both French and English.

The changes are as follows:

• FR: Instances ParallelU → Workers
• EN: ParallelU Instances → Workers

Administration

Permissions - Users label update

In the Administration / Habilitations (Permissions) module, an improvement has been made to the label of the field used to duplicate an existing user's rights.

The previously displayed label, « les mêmes droits que » (FR) / « same rights as » (EN), could be ambiguous about the exact role of the user selected in this field. To improve functional clarity, the label has been refined.

It is now displayed as follows:

• FR: les mêmes droits que le modèle
• EN: the same rights as the model

This change clarifies that the selected user serves as the reference template for duplicating permissions, rather than merely a point of comparison.

Relaxing the "Description de l'affectation" field in user management

A functional change has been made to the Administration → Utilisateurs (Users) screen when adding or editing a role assigned to a user.

Previously, the « Description de l'affectation » (Assignment description) field was mandatory, which could block validation when adding a role if no information was entered. However, since this field is purely informational, making it mandatory could create an unnecessary constraint in the administration process.

The « Description de l'affectation » (FR) / « Assignment description » (EN) field is now optional. A role can be added or edited and saved even if this field is left empty, with no validation error message.

Configuration

Configuration – Renaming the "Instances ParallelU" submenu

For terminology consistency and alignment with the platform's functional structure, the « Instances ParallelU » (ParallelU Instances) submenu has been renamed in the Configuration module.

The previous label no longer reflected the functional naming used across Orkestra's overall interface. To standardize vocabulary and avoid any ambiguity, this submenu is now called « UTD Manager », in both French and English.

The changes are as follows:

• FR: Instances ParallelU → UTD Manager
• EN: ParallelU Instances → UTD Manager

UTD Manager / Categories - Update to the "Ajouter" (Add) popup

An ergonomic improvement has been made to the add/edit window for categories in the Configuration → UTD Manager module, to improve its clarity and functional consistency.

The window title is now « Catégorie » (FR) / « Category » (EN), in both add and edit modes.

The field previously named « Catégorie » (Category) has been renamed to « Libellé catégorie » (FR) / « Category label » (EN), to better reflect the nature of the expected information.

The « Date de création » (Creation date) field has been removed from the form. This data is now automatically populated in the database at creation time with today's date, ensuring data reliability while reducing user input effort.

Lastly, the « Statut » (Status) field is now a structured dropdown list, offering the values Actif / Inactif (FR) or Active / Inactive (EN), ensuring consistent and controlled data entry.

UTD Manager - Label updates and addition of deletion in software publisher management

An update has been made to the Éditeurs de logiciels (Software publishers) tab of the Configuration → UTD Manager module, to improve label consistency and enrich administration features.

Label clarification

The add/edit popup previously showed generic titles that did not precisely reflect the functional context. The labels have been updated to improve understanding:

• The window title is now « Éditeur de logiciel » (FR) / « Software publisher » (EN).
• The main field is now called « Libellé » (FR) / « Label » (EN), replacing the previous names.

Added secure deletion

It is now possible to delete a software publisher, provided it is not referenced by any other entity (UTD, instance, software, or associated configuration).

When a publisher is not used anywhere, its deletion is allowed and confirmed with an explicit message:

« L'éditeur a été supprimé avec succès. » / « The publisher has been successfully deleted. »

However, if the publisher is still referenced, deletion is blocked to preserve the integrity of existing configurations. A warning message then informs the user:

« Impossible de supprimer cet éditeur : il est utilisé dans une ou plusieurs configurations. » / « Unable to delete this publisher: it is used in one or more configurations. »

UTD Manager - Harmonization of the Servers popups

Improvements have been made to the Serveurs (Servers) tab of the Configuration → UTD Manager module, to harmonize the add and edit windows and strengthen deletion handling.

The add and edit popups have been aligned in terms of titles, labels, and visible fields to ensure better ergonomic consistency.

The add window now displays the title « Ajout d'un serveur » (FR) / « Add server » (EN). The edit window displays « Édition du serveur : <nom du serveur> » (FR) / « Edit server: <server name> » (EN), making it possible to clearly identify the item being edited.

The « Nom » (Name) field has been renamed to « Nom du serveur » (FR) / « Server name » (EN), to remove any ambiguity. This field is now the only mandatory one.

The « Date de dernière activité » (Last activity date) and « Durée d'exploitation » (Uptime) fields are no longer displayed in the popups; they remain available for viewing in the main grid. This simplification lightens the interface and refocuses data entry on the information that is actually configurable.

The « Statut » (Status) field is offered as a dropdown list with the values Actif / Inactif (FR) or Active / Inactive (EN). When adding a new server, the default value is set to Actif / Active.

Secure deletion of servers

It is now possible to delete a server provided it is not referenced by any other entity (UTD, instance, associated configuration, etc.).

If the server is not in use, deletion is allowed and confirmed with the message:

« Le serveur a été supprimé avec succès. » / « The server has been successfully deleted. »

However, if the server is still referenced, deletion is blocked to guarantee the integrity of existing configurations. An explicit message then informs the user:

« Impossible de supprimer ce serveur : il est utilisé dans une ou plusieurs configurations. » / « Unable to delete this server: it is used in one or more configurations. »

UTD Manager – Evolution of the Workers tab (formerly Clients ParallelU)

In the Configuration → UTD Manager module, the tab previously named « Clients ParallelU » (ParallelU Clients) has been renamed and aligned with the platform's current terminology to reflect how the execution engine actually works.

Tab renaming

The label now reads as follows:

• FR: Clients ParallelU → Workers
• EN: ParallelU Clients → Workers

This change harmonizes naming with that used in other modules, notably in Supervision.

Update to the add and edit popups

The add and edit windows have been harmonized:

• Add popup: « Ajout d'un worker » (FR) / « Add worker » (EN)
• Edit popup: « Édition du worker : <nom du worker> » (FR) / « Edit worker: <worker name> » (EN)

The field previously called « Nom de l'instance ParallelU » (ParallelU instance name) has been renamed to « Nom du worker » (FR) / « Worker name » (EN).

The Status field is offered as a dropdown list with the values Actif / Inactif (FR) or Active / Inactive (EN). The default value when adding is set to Actif / Active.

The First activity date, Last activity date, and Uptime fields are no longer displayed in the popups. This information continues to be managed automatically by the system and remains available in the grid.

The mandatory fields are now:

• Nom du worker / Worker name
• Serveur / Server

Secure deletion of workers

It is now possible to delete a worker provided it is not referenced in any other configuration (UTD, instances, productions, etc.).

If the worker is not in use, deletion is confirmed with an explicit success message. The label now reads as follows:

• FR: Le worker a été supprimé avec succès
• EN: The worker has been successfully deleted.

However, if the worker is referenced elsewhere, deletion is blocked to preserve the integrity of the configurations. A clear error message informs the user that the worker is used in one or more configurations. The label now reads as follows:

• FR: Impossible de supprimer ce worker : il est utilisé dans une ou plusieurs configurations.
• EN: Unable to delete this worker: it is used in one or more configurations.

Platform

Security – Implementation of OIDC (OpenID Connect) authentication

Orkestra now includes an authentication mechanism based on the OIDC (OpenID Connect) protocol, enabling centralized and secure management of access to applications.

This change makes it possible to interface the platform with an OIDC-compatible Identity Provider, and to externalize authentication management while retaining control of permissions within Orkestra.

Thanks to this integration:

• Authentication can be centralized at the information system level.
• Users benefit from Single Sign-On (SSO) across connected applications.
• Security mechanisms (password management, MFA, access policies, etc.) are handled by the identity provider.

The OIDC integration is part of Orkestra's security and industrialization strategy, making it easier to deploy in demanding enterprise environments.

1.0.48.2

Technical

Worker blocking on schedules and sequencing

When sending end-of-production emails, a check is performed to determine whether an email template is associated with the module in question. For older schedules and productions using sequencing, no template had yet been registered. This caused an error during the check, which blocked the worker's execution.

1.0.48.1

Technical

1.0.48.0 migration failure issue

In some environments using Tags (Étiquettes), updating to version 1.0.48.0 could prevent the platform from starting due to a malfunction in the migration phase of the associated data.

Version 1.0.48.1 fully fixes this behavior.

After installing this version, the platform starts up normally and access to Tag-related features works as expected.

Recommendations:

• This update is strongly recommended for all customers using Tags.
• No functional changes are introduced: this is a stability fix only.

1.0.48.0

Data Fabrik

Assigning production email recipients

Previously, notifications were automatically sent only to the person who requested the production, which limited information sharing and traceability.

With this change, it is now possible to explicitly assign one or more people as recipients of notifications related to a UTD production. This configuration is built directly into the UTD production screen.

Users can now select multiple recipients using a simple, integrated search engine. When a similar production has already been run, the platform automatically suggests the recipients used previously, making configuration easier.

The list of recipients remains fully editable until the production is finally validated.

Selecting the email template for production recipients

This change allows the user to choose which email template to use to inform recipients of a production, adapting the message content to the nature of the job or its intended audience.

A simple selection field allows the user to choose the desired template from a predefined list. Only active email templates are offered, to ensure the choice remains relevant. When the production is similar to a previous run, the platform automatically suggests the template used previously, making configuration easier.

This selection remains entirely optional: if no explicit choice is made, the system will automatically use the standard end-of-production template (FIN_PROD).

Note: regardless of how recipients and custom emails are configured, the requester will always receive the default production follow-up email, as before.

UTD Manager

Viewing governance assignments

This change aims to make the oversight responsibilities associated with each module visible and explicit.

A new section titled "DATA GOVERNANCE" is now available on the detail page of each UTD module. It shows, as a list, all the users assigned to managing governance rules for the module in question.

Each row shows the first and last name of the assigned user, the assignment date, and the first and last name of the person who made the assignment.

Viewing end-of-production email recipients

Improved visibility of notifications by showing, directly from a UTD module's detail page, the list of users who receive the end-of-production email.

A dedicated section, titled « Destinataires du mail de fin de production » (End-of-production email recipients), is now available on the detail page of each UTD module.

For each recipient, the system shows the user's first and last name, the assignment date, and the name of the person who made the assignment.

This list can be edited via a production.

REF Manager

Excel import & export

This change allows users to perform bulk updates to their business reference data from an Excel file, simply and completely independently.

Specifically, a reference dataset can now be exported to Excel format, edited offline, and then re-imported into the platform to be updated.

During import, Orkestra automatically analyzes the file to check column matching, data typing, and the presence of any anomalies. A detailed validation report is then displayed, showing for each row the success or error status, together with the field involved and an explanatory message.

The identifier (ID) of each record remains read-only to ensure consistency between existing rows and new data.

Administration

Assigning a standard set of rights to a user

This new approach considerably simplifies assigning rights to users by making it possible to create template profiles grouping consistent sets of rights.

A template user is a reference account on which an administrator configures specific application rights (for example, UTD Manager Super Admin, Data Fabrik Creator, or Ref Manager Viewer).

These accounts are not intended to log in to the platform; instead, they serve as a basis for quickly duplicating their rights to real users. A dedicated interface allows an administrator to select a template user and replicate their permissions onto a given user.

Configuration

Creating and managing custom email templates

Previously, only the standard email templates provided by the platform could be used for UTD end-of-production notifications.

This version removes that limitation by introducing the ability to create and define new custom email templates directly from the module's interface. A new « Ajouter » (Add) button is now available on the email template management screen.

It allows the creation of a template tailored to a specific context — for example, a type of production, a business audience, an internal validation procedure, or Data Governance.

This change complements the new UTD notification recipient assignment feature and offers full flexibility in managing the communications generated by the platform. Teams can thus adapt the content, tone, and presentation of messages as needed, while retaining centralized governance of the available templates.

Technical

SAML2 SSO

The Orkestra platform introduces support for the SAML2 protocol for single sign-on (SSO).

This change allows companies to centralize identity management and provide their users with simplified, secure access to the platform via their existing identity provider. SAML2 SSO integration strengthens access security while improving the user experience through federated authentication.

Technical prerequisite: a valid X.509 certificate must be installed on the server to enable the signing and validation of SAML exchanges.

Orkestra on SQL Server

A major evolution of the platform's architecture with full support for Microsoft SQL Server as the single database engine.

This unification significantly improves performance, security, and maintainability while ensuring better integration with corporate IT infrastructures.

All Orkestra components (runtime, reference data, workflows, governance, UTD) now run on a centralized SQL Server database, providing a more robust and industrialized architecture.

Technical prerequisite: the platform must have access to a properly configured SQL Server 2019 or later instance before installation.

Migration to .NET 8 – Modernization, performance

With version 1.0.48.0, Orkestra adopts .NET 8, the latest version of the Microsoft framework.

This change strengthens the platform's performance, security, and stability while ensuring compatibility with modern cloud environments and long-term support (LTS).

This update marks an important step in Orkestra's technological modernization and prepares the platform for future functional and integration developments.

Technical prerequisite: the .NET 8 Runtime & Hosting Bundle must be installed on the server before deployment. This operation may require a server restart.