Skip to main content

(XPF) Xperiflow 4.3 Upgrade Guide

Author: Connor Stabnick, Created: 2026-07-29

Background​

The 4.3.0 release of SensibleAI Forecast and Studio enables deeper cross functionality with the OneStream Platform and external MCP tooling. With this, an upgrade deployment is required to configure the newly required components. As this is not self-service, a support request is required and requires downtime to be facilitated.

Schedule the Upgrade​

In preparation for this please:

  1. Ensure your OneStream environment is on platform version 9.3.1 or greater
  2. Make a request for the upgrade using the “AI Services Upgrade” request in ServiceNow: CSM Service Catalog - OneStream Customer Portal
  3. Schedule downtime related to this request with the OneStream Cloud Services Booking: https://bookings.cloud.microsoft/book/OneStreamSoftware@onestreamsoftware.onmicrosoft.com/s/jR-RMbuUn0CocOMZTq21wg2?ismsaljsauthenabled

After the Upgrade​

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.3.0 Release Notes. No additional steps in XCT need to be taken for this upgrade.

Things to look out for:

  1. Custom Business Rules

    1. Problem: Xperiflow now requires that the App Name be submitted in each request. This is built mainly for agents and to follow consistent logic.
    2. Solution: This should be a non-breaking change. Most of this should be handled in the background with how we edited the clients in XBR. IF NOT -- validate prior, and new instantiation. Should be 1 line of code change wherever clients are being instantiated.
  2. Custom Dashboards

    1. Problem: All Xperiflow Web URLs now require qpp name to be in the URLs
    2. Solution: We have a built out class in XBR that will be a 1 line of code change, really easy that will format the URL for you and you can reference that one instead. This should standardize everything moving forward so if we run into something like this in the future, it won't be an issue.

Was this page helpful?