Release Highlights
- Notifications & Comments
- Split user language & data language in windows client
- Import through API
- Import: Smart hierarchy match
- New import: Windows GUI
More details can be found in the pptx file (Perfion Update Q3 2025 - Webinar for Perfion Customers.pptx) attached at the bottom of this page.
Downloads
| Component | Files | Related Guides |
|---|---|---|
| Database Installer | Perfion.DBInstaller 2025-R2 (5.7.1).zip | Database - Installation guide |
| Application Server | Perfion.ApplicationServer 2025-R2 (5.7.10).zip | Application Server |
| API Service | Perfion.APIService 2025-R2 (5.7.10).zip | Installation guide |
| Web Client |
Perfion Web Client 2025-R2 (5.7.10).zip |
Web Client - Installation Guide |
| Windows Client | Windows Client - Installation Guide | |
| Supplier Portal | Perfion Supplier Portal 2025-R2 (5.7.10).zip | Supplier Portal - Installation |
| API Tester | Perfion.APITester 2.1 (2.1.0).zip |
Release Notes
5.7.10 (May 27th, 2026)
| Release Note |
|---|
| Deleting and item: Deleting an item in Perfion with permissions enabled could delete entire parent chain. This has been fixed. |
5.7.9 (March 12th, 2026)
| Release Note |
|---|
| Sync of individual Content Stores: Previously, the scheduled job for synchronizing content stores would sync all stores at once. This caused issues when multiple Perfion installations (e.g. Test and Production) were running simultaneously, as each could overwrite data intended for the other. The scheduled job now supports selecting which content stores to sync per installation. |
5.7.8 (February 4th, 2026)
| Release Note |
|---|
| Windows Client could appear frozen on closing the Item Editor. Perfion Windows Client could in some cases appear frozen for a few seconds after closing the Item Editor window. This has been optimized. |
5.7.7 (December 22th, 2025)
| Release Note |
|---|
| Security vulnerability: Fixing identified security vulnerabilities that could potentially expose data under specific conditions. We recommend all systems update to this version as soon as possible. |
| Item Editor: Hotfix of an issue that caused images in a specific dependency configuration to be removed if unrelated image changes were performed. |
| IMPORT.SUPPLIER Action: The action could fail with a "Column Status does not allow Null-values" error. This has been fixed. |
| Empty specs for base values: New Perfion Importer (IMPORT.FEATUREDATA action, Import Wizard, and non-legacy Import in WinClient) could create empty specs for base values. This has been fixed. |
| Active Directory: Fixed a bug in Active Directory authentication where login could fail due to a duplicate key exception, resulting in access being denied. |
| TLS encryption required: From version 5.7.7, TLS is mandatory for Perfion Web Client and Supplier Portal. A valid SSL certificate must be installed on the web server. Self-signed certificates are supported but may need extra browser configuration. |
5.7.6 (October 7th, 2025)
| Release Note |
|---|
| Editable read-only categories: Supplier users of the Supplier Portal could modify categories marked as read-only. This is now blocked. |
| Missing "Expose Read Only" grouping: Dashboards can now group by "Expose Read Only" features, which was previously unavailable. |
| Accepted items deletable: In the Supplier Portal, accepted items could be deleted by Organization Users. Now only Draft and Rejected items can be removed. |
| Error on non-localizable category grouping: Grouping by non-localizable categories in the Supplier Dashboard caused a query error. This has been fixed. |
| AD sync matching too narrow: AD sync now uses UPN, Email, and Other emails to link users to Perfion accounts. Previously, when synching users with Microsoft Entra ID, only the User Principal Name (UPN) was used, which could result in unmatched users being marked as inactive. |
| Execute-clause mishandling in API queries: In earlier versions of Perfion, the API did not correctly handle Execute clauses when queries combined data from both Supplier and Standard Items. This was especially problematic for Supplier Dashboard widgets using filter properties. The issue has now been resolved. |
5.7.5 (August 26th, 2025)
| Release Note |
|---|
| Error synching formulas to Content Store: When configuring a formula feature to be exposed to a Content Store, the sync job could fail with an 'Object reference not set to an instance of an object' error and the store would not be correctly synced. This has now been fixed. |
5.7.4 (August 21th, 2025)
| Release Note |
|---|
| Supplier Portal: Importing Supplier Items having a non-localized categorizer gave "Key not found" error in import. This has been fixed. |
| Channel Management: When creating a channel or editing an existing channel the error message "Channel name could not be saved." was shown. This is fixed. |
| Fetching remote values could fail under special circumstances: Using created or modified date in a Perfion query with remotes, could make fetching remote values fail with a null-value exception. This has been fixed. |
| Partially disabled Logging: Upgrading to 2025-R1 partially disabled Logging, The database installer 5.7.1 enables the missing logging setting if logging are enabled in Settings. |
5.7.3 (August 14th, 2025)
| Release Note |
|---|
| Fixed issue where multi-cell editing affected unselected cells |
|
When editing users in the web client, administrators could experience an error stating that 'userId' is missing. This was unfortunately introduced in the 5.7.2 hotfix, but has now been fixed. |
5.7.2 (July 29th, 2025)
| Release Note |
|---|
| Active Directory - Users would experience errors when logging into Perfion using Entra ID single-sign-on, when Perfion was configured to use "Advanced Integration". The error was caused by incorrect handling of the user groups specifying what languages a user have access to. It has now been fixed. |
| Active Directory - When clicking the 'Sync with AD' button in User Management, users could experience a syntax error, and the sync of inactive users would not be performed as expected. Additionally, an error may be displayed when using the Migrate User button to enable AD login for an existing user in Perfion. These issues have been fixed. |
5.7.1 (July 10th, 2025)
| Release Note |
|---|
| Permissions - Editing a feature with permits enabled could result in permits being deleted from items. This occurred in the Windows Client when switching to the "Advanced tab" and then clicking OK. This issue has been fixed. |
| Notifications - In certain cases, notification emails were not sent. This issue has now been fixed. |
| Notifications - The button in the Comments section is now disabled if the comment box is empty. |
| Notifications - A bug causing line breaks (Shift+Enter) in comments to malfunction has been fixed |
| Notifications - An error occurred when adding comments with mentions from the Item Editor |
5.7.0 (July 2nd, 2025)
| Release Note |
|---|
| Context menu of items: A Comments button was added. Clicking it opens the comments section for that item. |
| Added Edit/Delete icons for default values in selectable features in searches. This supplements the existing right-click functionality. |
|
The new Importer now checks user roles:
|
| The Perfion API now supports execution of the new Importer via REST. Jobs are submitted to the Perfion Application Server, and job status can be queried via the API. See documentation for details. |
| The Perfion Web Client installer now includes support for Integrated Security in the database connection. |
|
The following properties have been added to the ActFeatureInfo Action object:
|
| Validation for the Service URL field now rejects special characters more strictly. Only letters and numbers are allowed. |
| Image selection in Content Store settings is now limited to standard web formats: PNG, JPEG, and WEBP. |
| Theme Color error messaging: When an invalid hexCode is entered for themeColor in the Content Store, the last attempted hexCode is now preserved and shown in the error message. This ensures clarity while maintaining consistent input validation behavior. |
| The Connection button has been removed from the Windows Client menu. If no configuration file is found on launch, users are prompted to enter connection details as before. |
| Admins can now define both the interface language and data language for a user via “User Properties". |
| PDF Preview Error on Supplier Data Columns fixed an issue where right-clicking a supplier data column (e.g., [SUP]User Guide) to preview a PDF caused an error ("Not possible to get values on supplier data") and an infinite error dialog loop. |
| The message shown when deleting a Content Store user now correctly displays the user’s name in a readable format. |
| Password change failures now show more relevant and helpful error messages. |
| Exported single path hierarchical feature values are now prefixed with a pipe "|" by the Exporter to indicate a full path. This ensures re-importability, as a full path (prefixed with "|") is never ambiguous, while a single path element can be. When re-imported, the Importer recognizes the value as a full path and only looks for it at the root of the hierarchy. Note that _ParentPath is always treated as a full path and does not require a leading "|". |
| The new Importer is now available in the Perfion Windows Client under the "Import Data" tab. The original importer is still available as “Legacy Import Data" in a submenu. |
| Fixed an issue preventing command-line upgrades of the DB installer from v5.4 to v5.5 on Azure databases. |
| Resolved an issue where remote connections containing certain special characters could not be saved. |
| Cells hidden by filters are now automatically picked when using 'Ctrl+Shift' |
|
The IMPORT.FEATUREDATA action now supports the new parameter “AmbiguousSelectableValueHandling”. It controls how the importer behaves when a selectable value is shared across multiple items. It can be set to one of the following 3 values:
Notes:
|
| Mail Settings have been moved from the Supplier Portal Settings to the main Settings menu. |
| Fixed an issue where bearer tokens generated using a ServiceAccount user could not be used to authenticate with the Perfion API that the token is not valid for this use, |
| There was no indication of the currently selected group. |
Comments
0 comments
Please sign in to leave a comment.