Author: Evan Rasmussen, Created: 2026-09-02

Background

The 4.4.0 release of Xperiflow, building off of the 4.3.0 release with deeper integration with the OneStream Platform and external MCP tooling. This upgrade is more self-service than 4.3.0 was, with some important caveats outlined below.

Pre-Upgrade Steps

If coming from a version prior to 4.3.0, you must follow (XPF) Xperiflow 4.3 Upgrade Guide.

Before performing the upgrade to Xperiflow 4.4 via XCT, install the latest AIS Dependency Bundle and XCT solution from the compatibility guide.

The first thing you must do is upgrade the dependency bundle.

If you are upgrading to XPFv4.4.0 between the dates of - , please consult with the AI Support team (or create a ticket) regarding a corresponding upgrade to Synapse (the Xperiflow team’s frontend deployment housing agents). After September 14th, this upgrade will be automatically built into the XCT self-service upgrade and is not something user’s will need to concern themselves with.

Ensure you are on Platform version 9.3.1 or greater.

Post-Upgrade Steps

Pull the updated version of the solutions from Solution Exchange for installation in OneStream: https://solution-exchange.onestream.com/solutions. Version compatibility can be identified in the XPFv4.4.0 Release Notes . No additional steps in XCT need to be taken for this upgrade.

Again, please reference (XPF) Xperiflow 4.3 Upgrade Guide.

Once the upgrade is complete, you should re-visit permissions relating to the Forecast Agent:

Admins in XAT have access to interact with the Forecast agent by default. A user with more restrictive permissions may have previously been able to interact with the Forecast Agent on XPFv4.3.0, but no longer can. This is due to the addition of a permission explicitly for this. Power users may now restrict a user’s ability to interact with the agent independently from the solution itself. These permissions enable more control while the Forecast Agent remains in its Beta state until our next major release with stronger unified access controls. In order to configure these permissions:

1. Open Xperiflow Administration Tools > Roles.

2. Create a role or open an existing one (for example Manager, Editor, or a custom Forecast User).

3. Bind the permission:

   • Forecast only: Forecast Agent Access
   • Studio only: Studio Agent Access
   • Both, current agents only: bind both named permissions
   • Every agent, including future ones: All Agents Access (same object Admin uses). Prefer this for a power-user role.

4. Assign that role to a person or a group on the Application scope (or Global if they should have it in every app). NOTE: using the app solution scope or the solution scope (FOR - Prod or FOR for example) will not grant the permission.