🚀 New functionality

• Audit. Portal has incorporated the ability to log all actions of creation, modification, or deletion performed by users on currently auditable Portal entities: User, User Configuration, and Tenant.

🔨 Improvements

• Diagnostics. From a device's detail view, you can see the analysis of resource consumption (CPU, RAM, GPU, Network, and Disk), based on application usage and system processes during a user's session.

  This feature allows you to select the user, date range, and view an interactive chart with details per time period.

• Delete a microservice. Allows deletion of archived microservices, provided it is not active on any tenant and not assigned to any flow.

• Fishing pattern field. You can now define the device attribute on which the regular expression defined in the search pattern will be applied: Full Name, Description, OU, and Current Subnet.

• Simultaneous flow request processing is supported to improve performance and responsiveness.

🔨 Improvements

• Flexxible Remote Assistance

  • Connection detection.

    The functionality of logging remote assistance jobs has been improved to accurately reflect the actual activity of operators. Previously, a job was completed when the link to download the .flxra file appeared on the operator's screen. or .exe.

    Now, the system detects and records all relevant information in the job details, including the closing and reconnection circumstances.

  • Sensitive data protection. In unattended remote assistance, operator sensitive information (like photo and username) is hidden to protect privacy.

• Compatibility of popup notifications with Windows Home editions has been added.

• Performance optimization when filtering by workspace groups with a large number of items.

• Improved sub-organization management for workspace groups, simplifying multi-client workflows.

• Increased reliability of job submissions from Workspaces to Portal.

• The API timeout has been increased to reduce errors in environments with very large datasets.

• The Force update custom fields action is now processed in the backend to avoid client-side timeouts and improve reliability.

• The flexxibleMID field has been added to the crowstrikedetections API endpoint to provide additional context in detections.

• An EDR field has been added to the device API endpoint to expose the endpoint protection status.

• Jobs initiated via the API now display the API access name in the job details, improving the traceability of automated actions.

• When a connection error with Service Bus occurs, the error message now suggests checking to ensure the device clock is correct, aiding in diagnosing time sync issues.

• Flows and microservices run by FlexxAgent Universal are now logged as jobs in Workspaces for consistent operational visibility.

• The API and Swagger documentation has been improved to provide clearer guidance for developers.

🔨 Improvement

• Prevent the configuration window from being shown to the user when an internal configuration error occurs at startup.

• The error The parameter is incorrect in attended remote assistance flows has been resolved.

• The Select all action in paginated or filtered tables now works correctly when using complex fields as filters.

• Applying a workspace group filter along with equality conditions in complex fields no longer results in failures or leaves jobs in a Pending state.

• Notifications are now sent in batches of 500 devices, and subsequent batches are correctly initialized for processing.

• The Force update custom fields job no longer blocks when there is no microservice configured for CustomFields.

• Running get pending patches or get installed patches no longer causes the web interface to become unresponsive.

• Device domains now appear correctly in the table for assignment to tenants.

• CrowdStrike is now appropriately detected as an antivirus/EDR product.

• The antivirus details view no longer shows duplicate entries for detected products.

• Running a System type microservice no longer produces the error Object reference not set to an instance of an object.

• Popup messages in sessions work correctly when pagination is applied.

• The job execution details for microservices now correctly show the time log instead of incorrect UTC hours.

• The Auth0 info field was removed from the Workspaces connection log table to avoid unnecessary data exposure.

• The BIOS version field now reports the correct value.

• Pending patch counts have been corrected so that the number of missing patches matches the actual status.

• The Save button no longer erroneously appears in the connection log detail view.

• The UnitOfWork column no longer appears where it does not belong in connection log lists in Workspaces.

• The unexpected error when requesting a Flexxible Remote Assistance session that previously returned An unexpected error occurred has been resolved.

• The report group listing has been corrected to show the appropriate fields and values.

• Build version numbers displayed for Windows 10 / Windows Server 2016 or later have been corrected.

• The Total login duration field in the session detail pivot table in Workspaces no longer shows random decimal values.

• The Uncategorized category for microservices is now translated correctly in Workspaces when changing the default language.

• The listing of workspace groups now remains correctly sorted after saving.

• Text search now works for microservices created from Portal.

• Server shutdown operations now complete correctly.

• Connection logs without an associated session are now deleted as expected, preventing the accumulation of obsolete information.

• Forcing the update of custom fields after selecting a set of devices now generates a job correctly.

• Agents that were not reporting their capabilities are now correctly recognized, allowing actions to be executed on them.

• The error Nullable object must have a value when attempting to disconnect multiple sessions has been resolved.

• Differential reports from FlexxAgent are correctly sent to Workspaces again, preventing unnecessary bandwidth usage.

• WoL job execution details now appropriately show the time log instead of incorrect UTC hours.

• The WoL process no longer marks devices as pending to turn on when they are already on.

• Threads for CreateUserNotificationRecipient and SendNotification no longer remain active continuously.

• The method InsertUpdateCrowdStrikeDetection no longer throws the error Object reference not set to an instance of an object when the tenant has CrowdStrike alerts not linked to PCs/devices.

• PCR7 configuration is no longer reported as Binding possible on devices without TPM.

• The agent now correctly reports the operating system version.

• A null reference error in the compliance component that could generate exceptions under certain conditions has been resolved.

• Errors related to sending operations to Flexxible have been fixed, including:

  • Session log messages in mass sessions (disconnect, log off, etc.) are now assigned only to one device.
  • Automatic OS update actions now appear with OperationName or RemoteOperationExecute.
  • When executing a microservice via the API, workspaceIds are now assigned correctly.
  • Operation UpsertWorkspaceGroup.

🚀 New functionality​

• More information on devices with multiple antivirus installed. In the Security tab of a device’s detail view in the Workspaces module, a new field showing additional information appears when more than one antivirus is installed, helping identify and prevent conflicts between security solutions. These data are also available as a column in the views of Workspaces and Servers.

🔨 Improvements​

• Predefined categories in microservices. Allow defining classification categories for microservices. This helps maintain consistency and avoid the creation of random or duplicate categories.

• Reorganized Portal menu. The Information, Products, and Modules sections are now found in Portal -> Settings -> Organization, within the tabs: General, Products, and Modules.

• Clone microservices in sub-organizations. Sub-organizations have the option to clone the microservices created in their environment to the main organization.

• Improved flows

  • New format. A left sidebar menu has been added to facilitate access to all functionalities.

  • New cooldown minimum time. The minimum value has increased from 1 to 10 minutes, providing greater control and stability in flow execution.

• Static workspaces groups without agent. Static workspaces groups can now include devices that do not have FlexxAgent active.

• Filter optimization. Filters by workspaces groups and installed applications in the workspaces module have been improved for more agile use.

• CrowdStrike

  Transition to Alerts. The integration has been adapted to changes in the CrowdStrike API, using the Alerts endpoint instead of Detections, which is now obsolete.

  Better performance. Threat detection collection is now 40% faster. And they are collected completely and without delay, even with a very high volume of logs.

  Greater data consistency. The displayname field in detections now always contains valid information, preventing it from appearing empty.

• Optimized searches

  • In the Event Log list of the Workspaces module, searches and filters are faster and more efficient.
  • In the Jobs section of the same module, record query performance has been improved.

• API improvements. Documentation now includes details of the fields returned by each endpoint. Additionally, inconsistencies were fixed where numeric fields returned "" (empty string) instead of null when no values were available.

• DeviceManagerEntries API endpoint fixes for startswith/endswith functions.

• Stricter parameter validation in API. Previously, if an API call included a non-existent parameter, the system ignored it and executed the query, this could cause issues (e. g., writing filer instead of filter). Invalid parameters are now validated correctly, returning a 40X error instead of unexpected results.

• Status updates for scheduled shutdown jobs. Previously, jobs were marked as Completed with errors when some machines were already shut down, causing confusion. Now the job ends as Completed.

• Status updates for Wake on LAN jobs. Previously, jobs were marked as Completed with errors when some machines were already shut down, causing confusion. Now the job ends as Completed.

• Bulk support for pop-up, disconnect, log off, and force log off actions. Multiple actions are now grouped into a single bulk job, simplifying execution at scale.

✅ Bug fixes​

• Fixed an issue where alert thresholds remained linked to the former tenant after a change.

• Fixed the ability to add networks from other tenants to Locations. There is now a restriction preventing cross-assignments between tenants.

• Fixed an issue that prevented marking notifications as attended on devices outside the domain.

• Resolved a security vulnerability in notifications. If a notification was sent with JavaScript code, it could execute when accessing the Workspaces menu after expiring. The risk has already been eliminated.

• Fixed a translation error when removing messaging services.

• Fixed an issue where workspace group updates included null elements.

• Fixed an incorrect state in remote assistance jobs when the screen closed before receiving the AnyDesk ID.

• Optimized operation execution with overall performance and stability improvements.

• Fixed an error that automatically changed the report group with the same title as another modified by a user, making differentiation difficult.

• Fixed the ReportingGroup endpoint, which did not correctly apply groupby/aggregate.

• Fixed an issue in the notification detail view on a device, which incorrectly opened navigation.

• Fixed inconsistency in public IP information between different machine views.