Recent Content
Smart Integration Connector (SIC)
Smart Integration Connector is OneStream's new standard for local data source integration to OneStream's Cloud. OneStream customers use local data sources to import data into OneStream or to facilitate drill through queries to satisfy data lineage inquiries. A Local Gateway Service, installed in your network on a Windows Server/VM, manages all credentials and files necessary for local data source connectivity. The Local Gateway Service establishes an outbound connection using Web Sockets to Azure Relay. With v8.0, OneStream is no longer supporting VPN connections. Transitioning from VPN to SIC is simple - both can co-exist for comparison testing. SIC is intended for self-service configuration. Learn more using the assets below: OneStream Navigator contains a free self-paced SIC Course The latest OneStream Smart Integration Connector Guide Whitelist the Azure Relay to your Firewall by IP Address When following the documentation to Whitelist the Azure Relay to your Firewall by IP address, there is a link to a publicly available script that is needed in order to obtain the list of IPs required to whitelist. It has been reported that this publicly available script does not return IPs in all cases. We have submitted a request to update the publicly available version. Until this script is updated, you can use the version attached to this post.Platform v8 Upgrade FAQs
What is Platform v8? Platform v8 is the gateway to OneStream’s NextGen architecture, providing optimizations to enable the next level of scale and growth for our customers. The NextGen architecture starts with Platform v8, which provides faster processing and computational performance and modernizes OneStream’s authentication and data integration technology. As with most OneStream Platform major releases, we will be deprecating older technology, introducing new technologies, and there are some ‘breaking changes’ that must be addressed during the upgrade process. Customers will need extra time for this upgrade cycle, and OneStream has prepared readiness content and new processes to make the transition to Platform v8 successful. How will Platform v8 modernize technology and why is that important for future growth? Platform v8 has migrated the development framework from .NET4.8 to the .NET6 (sometime referred to as .NET Core – see this video for more background). This migration represents a significant modernization of OneStream’s Platform code that will yield immediate performance benefits for memory intensive operations – such as Consolidation processing, data and meta data loading, and complex cube views. The transition to .NET6 represents a significant developer framework modernization that opens the door for developers to utilize new paradigms, components, and strategies to further advance Platform performance, scale, and adopt modern cloud-native approaches to optimize operations. What are additional features of Platform v8 modernization? With Platform v8, OneStream IdentityServer (OIS) and Smart Integration Connector (SIC) will be generally available. In coordination with these announcements, OneStream cloud customers upgrading to Platform v8+ will migrate from Legacy Authentication to OIS, and if they are utilizing VPN for local data source integration – they will migrate to SIC. Both OIS and SIC represent modern, cloud-native technologies that provide functional, security, and performance benefits to cloud customers. VPN will not be provided with any Platform v8+ release. What are examples of ‘Future Growth’ for the OneStream Platform? With this .NET migration, adopting newer .NET frameworks will be easier – OneStream expects to maintain alignment with Microsoft’s Long Term Support (LTS) release schedule, and therefore migrate to .NET8 for a 2024 release. .NET 8 is expected to further enhance OneStream processing performance gains. Following the release of Platform v8, you will start to hear about development for our NextGen architecture. This is an in-development reference to a new architecture that will implement an elastic scaling infrastructure to automate the application of compute power to meet customer demand. I’m a self-hosted customer – what else do I need to know about Platform v8? Self-Hosted customers will work through their Customer Success Manager to engage in the Platform v8 upgrade process. The v8 installable MSI files will not be downloadable by default on Solution Exchange. Self-hosted customers committed to the upgrade will be provided download access to the install files on Solution Exchange. All customers will benefit from the performance gains for Consolidation processing, data and meta-data loading, and complex Cube Views. Self-hosted customers will also benefit from optimized memory management on their Application Servers. Self-hosted customers are not subject to the required cloud technology migrations to OIS or SIC, but are encouraged to follow guidance in the Upgrade Guide for a successful installation. I’m a FedRamp hosted customer – can I upgrade to Platform v8? OneStream designates a Platform release for FedRamp certification each year, enabling FedRamp hosted customers to upgrade to this approved release at their convenience. Currently, Platform v8 is not certified for FedRamp hosted customer use. Stay tuned for further information on the Platform v8.x version designated for FedRamp certification. What is the process for cloud customers to engage in a Platform v8 upgrade and when does that commence? As of the August release date, customers may indicate their interest in Platform v8 by submitting a Software Upgrade Catalog request. Customer Success will meet with upgrade candidates to review the release benefits and discuss the preparation tasks necessary to commence the software upgrade. In early September, cloud customers who have completed prescribed readiness criteria will be provided v8 migration instances to perform tasks necessary for Platform v8 compatibility. Following successful testing in the v8 Migration instances, production data will be cutover for final verification. What are the steps of a Platform v8 Upgrade for a Cloud Customer? For Cloud customers, the Platform v8 upgrade process is comprised of two phases - Preparation Phase and Migration Phase. Customer Success will lead customers through the benefits of the release, and review the customer-specific activities required. Customers will be required to provide a response to required tasks with evidence indicating their readiness for the Migration Phase. For example, the .NET6 Desktop Runtime must be rolled out to every OneStream user before the Migration Phase can begin. The Migration Phase will commence with taking a snapshot of each existing environment (i.e, Prod & Non-Prod) to create a corresponding v8 Migration environment. Customers will perform Solution Upgrades, Business Rule compatibility maintenance, and SIC implementation (if necessary) in these environments. Upon completion of these activities, then-current data and meta data will be cutover to the Migration instances for final verification and testing. More details on the Platform v8 Upgrade process will be discussed during your Preparation Phase calls. What functionality is being deprecated with Platform v8? With the release of Platform v8 OneStream is deprecating: Cloud-Hosted Customers Legacy Authentication – OneStream IdentityServer (OIS) is the new authentication standard VPN – Smart Integration Connector (SIC) is the new local data source integration standard VBA ROPC – cloud customers are to use OIS Personal Access Tokens when authenticating via VBA macros in Excel Self-Hosted Customers VBA ROPC – self-hosted customers are to use SSO Tokens when authenticating via VBA macros in Excel All Customers Client API – customers are encouraged to utilize Task Scheduler or the REST API to satisfy use cases previously calling for Client API MVC (OneStream Mobile) – customers are encouraged to engage in the BrowserUX Early Access Program for End-User browser access use cases on desktops/laptops or mobile devices Are there new requirements for production use of Platform v8? Yes, to summarize content from the previous FAQ question: Cloud-Hosted Customers OneStream IdentityServer (OIS) is the new authentication standard Smart Integration Connector (SIC) is the new local data source integration standard (VPN is not supported with v8+) OIS Personal Access Tokens for VBA authentication in Excel Self-Hosted Customers SSO Tokens for VBA authentication in Excel Do I have to prepare user laptops and desktops with .NET6 to access Platform v8? Yes, the Windows Application Client requires locally installed .NET6 Desktop Runtime 6.0.14 or greater to operate. Users with administrative access to their machines may individually perform the installation or it can be scheduled to all targeted users through a Corporate push. The .NET6 Desktop Runtime can co-exist with previous versions of the .NET Runtime. Microsoft provides access to the .NET6 Desktop Runtime here. What are the core functional enhancements in Platform v8? Performance Performance enhancements for memory intensive tasks such as Consolidation processing and complex cube views Journal Enhancements Export journals to XLSX BRApi Option to prevent self-approval and self-posting of journals Option to require journal creation using templates Copy journals across time periods Delete multiple journals simultaneously Validate journal for intersection constraints Prevent journals to impact entities not assigned in Parent Workflow profile Show member descriptions in Journal Line Items Option to display UD descriptions from Application Properties in Journal POV and Line Item Headers Workspaces Addition of Cube Views to Workspace object organization Cloud Data Source Integration SIC: Increased throughput for data payloads to 5 million rows and 5GB Identity and Access Management OIS: Self-service integration for SAML Identity Providers User Experience Cube View and Excel enhanced with shortcuts, scaling, and hotkeys Option to disable auto-refresh of dashboards Option to rename and copy form templates Option to rename and copy Data Management sequence/steps What are Breaking Changes? OneStream is continuously innovating the platform to meet the evolving demands of our customers. Evolution often requires the deprecation of older technologies and methodologies, and the adoption of newer technologies and paradigms. New technologies and paradigms that require customers to make changes during a platform upgrade are isolated to Major releases (on average once every 12 – 16 months). A breaking change implies that with an upgrade to a Major platform release, an existing process may ‘break’ and require changes to adapt to new technology or process. With the upgrade to Platform v8, there are occurrences of Business Rules no longer compiling - largely due to compatibilty with OneStream’s adoption of the .NET6 development framework. In rarer cases, changes to Workspaces may cause a breaking change. Deprecated functionality, such as Client API or VBA ROPC authentication are additional examples where customer use cases need to be changed to evolve with Platform v8. Why will Platform v8 cause my existing business rules to break? Mainly due to compatibility with .NET6. Certain DLLs in use with pre v8 platform versions are only compatible with the older version of .NET, and must be upgraded to be compatible with .NET6. In other cases syntax changes are required to fulfil compatibility requirements of .NET6. In a few cases, enhancements to Workspaces require designated Business Rule references to be adjusted to compile. Will I have to upgrade Solutions during the Platform v8 upgrade process? Yes, OneStream has made Business Rule changes to approximately 15 Solutions. Customers may upgrade to the latest version of these solutions to ensure Platform v8 compatibility. See the complete status of Solution compatibility with Platform v8 in the MP Solution Forum post in the ONECommunity Platform v8+ Group. Do I have to perform the Solution upgrade or can I manually make v8 compatibility changes? OneStream recommends upgrading Solutions to ensure comprehensive compatibility, and to maintain alignment with future solution releases. For designated solutions, customer-specific solution configurations may cause upgrade complexities. Under these conditions, customers may reach out to OneStream through their Customer Success Manager to discuss manual solution changes to achieve Platform v8 compatibility. Manual changes are the exception and to be performed only when necessary. I use ERP Connect for integration with SAP data sources – will this continue to work with Platform v8? Yes, support for ERPConnect will now be via the Smart Integration Connector. Note: There is a new version of ERPConnect – ERPConnect20.DLL that is available for download from the DLL tile on the Platform page of Solutions Exchange. See the SIC doc for additional information. What is OIS authentication? OneStream IdentityServer (OIS) is OneStream’s single sign-on (SSO) service for applications hosted in the OneStream Azure Cloud environment. OneStream IdentityServer supports multiple, concurrent OpenID Connect (OIDC) and SAML 2.0 protocol compliant external identity providers (IdPs) and native authentication, so you have more choice and flexibility implementing SSO. Customer Identity Providers may be integrated into OIS to achieve SSO with OneStream using the Identity and Access Management (IAM) Portal self-service user experience. Additionally, the IAM portal provides for the management of Personal Access Tokens (PAT) to facilitate REST and VBA API authentication. Learn more about OIS and the IAM Portal in the ONECommunity Platform v8+ Group. Do I have to migrate to OIS in order to upgrade to Platform v8? Yes! OneStream IdentityServer (OIS) has been the standard authentication technology for all new OneStream cloud customers as of v7.4 with over 150 customers using OIS in production. As of Platform v8, OIS is the required authentication technology for all new and upgrading customers. What are the benefits of OIS? OneStream IdentityServer (OIS) represents a modern, secure, and cloud-native approach to enterprise SaaS solution authentication. There are several benefits provided by OIS to enrich the OneStream customer experience: Enables SSO integration with any OIDC or SAML2P protocol compliant Identity Providers Provides for SSO integration with multiple sources of authentication from a single OneStream cloud instance Secure use of Native IDs in conjunction with SSO authentication Identity and Access Management portal for self-service integration and management of Identity Providers Identity and Access Management portal for self-service generation and management of Personal Access Tokens (PAT) for use in API authentication How to I prepare to migrate to OIS? Migration from your current authentication technology (sometimes referred to as ‘legacy’) should be straight-forward and seamless to your user community’s login / logoff experience. During the upgrade planning, Customer Success will provide you with a document corresponding to your current Identity Provider which identifies the meta data content required to migrate to OIS. What is SIC data source integration? Smart Integration Connector (SIC) is OneStream’s solution for providing local data source integration to the OneStream cloud. SIC is a modern, secure, cloud-native approach to integration that aligns with our customers’ IT security concerns. As opposed to a VPN ‘direct connection’ to a customers network, SIC leverages Azure Relay technology to ‘meet in the middle’. Customers deploy an SIC Local Gateway Server that listens to the Relay via an outbound connection. Additionally, the Local Gateway is responsible for connections to designated data sources, including management of database credentials and supporting dll files. SIC also supports sFTP file exchange and exports to local data warehouse databases. Do I have to migrate to SIC in order to upgrade to Platform v8? Cloud-hosted customers requiring local data source integration will use SIC with Platform v8. Customers currently using VPN must migrate to SIC as part of the upgrade process. Can I continue to operate VPN with Platform v8? No. VPN has been discontinued with Platform v8 and forward. VPN will be supported in pre-v8 releases through August 31, 2024. Does SIC enable direct writeback from OneStream to a Data Warehouse? Yes, in addition to facilitating data loads and drill through queries, SIC permits writeback of OneStream data to Data warehouse repositories. Does SIC enable access to sFTP files? Yes, SIC permits a Web API connection to faciliate sFTP file exchanges. What data payloads does SIC manage? SIC supports data payloads of up to 5 million rows and 5G of data. These defaults can be configured by customers within the Smart Integration Local Gateway Configuration utility. Thresholds can be configured by customers. Are there changes to VBA authentication with Platform v8? Yes, use of ROPC with VBA has been discontinued with Platform v8. Cloud customers will use Personal Access Tokens and self-hosted customers will use SSO Tokens – see the ‘Visual Basic for Applications (VBA) Procedure’ section of the Design and Reference Guide for coding examples. Where did the ClickOnce Tiles Page go with Platform v8? When invoking the OneStream Windows Application client via the ClickOnce URL (https://<your sitename>.com/OneStreamWeb/OneStreamWindowsApp.aspx), users will no longer be presented the familiar ‘tiles page’. The URL will move directly to the acknowledge dialog, and clicking ‘Open’ will immediately begin the Windows Application Client provisioning process. What’s different with Web documentation with Platform v8? When clicking the ‘?’ to invoke help from the Windows client application, users will be brought to a centralized public OneStream documentation portal. Centralized documentation streamlines installations and provide for on-demand access to the latest version of OneStream documentation. What’s the status of Client API with Platform v8? Client API has been removed from the Platform v8 installation and is no longer supported. Use cases calling for Client API should be transitioned to Task Scheduler or the REST API. Contact support for further assistance with managing this deprecation. Is BrowserUX GA with Platform v8? No. While BrowserUX is available with Platform v8, it is not enabled by default. The BrowserUX Initiative continues to progress with a goal of browser-enabling the comprehensive set of OneStream end-user functionality. OneStream is actively seeking Early Access Program candidates to validate browser use case in their self-hosted or cloud-hosted environments. How can I participate in BrowserUX Early Access Programs? Customers having a go-to-production browser use case, and an ‘early adopter’ spirit will be considered for participation in the BrowserUX Private Preview program. Customers successfully validating their browser use case in non-production will be supported to transition to production use through the Limited Availability program. Committed candidates are selected based on a discussion with OneStream to ensure a high probability of success. If you are interested in participating, reach out to your Customer Success Manager.Business Rule Compatibility and Workspace Updates
There are several substantial changes as part of v8 that can impact business rules and custom solutions. These are being driven by: The introduction of workspaces and associated security roles and xfproject changes. Adding Cube Views to workspaces. The expansion of locations where cube views can be created, managed, and stored. Transitioning the business rule compiler from .NET Framework 4.8 to .NET6 (.NET Core). The attached document represents the changes and lessons learned made by OneStream while addressing these changes for the solutions maintained on Solution Exchange.OneStream Identity Server (OIS)
OneStream IdentityServer is OneStream's new standard for cloud site authentication, facilitating direct SSO integration with any OIDC or SAML2P protocol Identity Providers. With OIS, customers may establish connections to multiple IdPs, leverage secure Native ID authenticaiton, and use Personal Access Tokens for REST API or VBA connections to OneStream. All customers adopting Platform v8 or higher will be integrated with OIS Authentication. Learn more using the following assets: Read the latest about OIS in the Identity and Access Management Guide. Learn more about OneStream and authentication using the attached resources.Solution Information
Business Rules may require changes to ensure compatibility with Platform v8.2 .NET8 development framework and this includes Business Rules used in various Solutions. As such, OneStream is releasing solution version updates where Business Rule changes were required. Only the most recent version of the solution will be updated to be compatible with Platform v8. The overview provided in the Solution Exchange will indicate whether the solution is compatible with Platform v8. Sunset Solutions The following solutions were sunset August 2024: Solution Code Solution Name EUCTV End User Training-Cube Views EUTEA End User Training-Excel Analysis EUTRB End User Training-Report Books EUTSA End User Training-Spreadsheet Analysis EUTV End User Training-Videos EUTW End User Training-Workflow EUTXFD End User Training-Extensible Docs Unsupported Solutions Solution Code Solution Name AWS Actor Workspace CMR Close Manager HDK Help Desk PBL Process Blocker PCM Process Control Manager POW PowerShell Scripting PRM Provision Request Manager TXP Tax Provision TRM Train Me (Video Help) Solution Installation Guidance Recommendations For Platform versions 7.1.1 - 7.4.4, upgrade Solutions when possible. ACM must be upgraded to PV710 SV100 If Solution upgrades are performed in a v8+ migration instance: Load the latest MP upgrade package via Application |Load/Extract Within the currently installed version of the solution, navigate to the uninstall dashboard and run the Uninstall UI function Load the MP upgrade package again PAM PV620 SV103 mitigates a low impact security vulnerability in Python 3.6 by loading Python "on-demand" vs. always being resident on server images. Solutions Compatible with v8+ The following solution versions are the minimum versions that are compatible with Platform v8+. Any prerequisites are to be performed prior to upgrading. ACM - Application Control Manager PV710 SV101 Platform 7.0 and earlier - Upgrade to Platform version 7.4.4 Platform 7.1.1 - 7.4.4 - Upgrade ACM to PV710 SV100 AST - Administrator Solution Tools PV740 SV101 CAT - Cloud Administration Tools PV600 SV100 CPP - Capital Planning PV620 SV102 DCU - Dimension Comparison Utility DFM - Data Entry 123 PV440 SV100 FEM - File Explorer Manager PV650 SV102 GDR - Guided Reporting PV600 SV102 LTS - Load Test Suite All versions compatible MDB - Excel Metadata Builder PV520 SV101 MST - MarketPlace Solution Tools PV720 SV100 OFC - OneStream Financial Close PV710 SV203 Platform 7.0 and earlier - Upgrade to Platform version 7.4.4 OPS - Parcel Service PV630 SV100 OSD - System Diagnostics PV620 SV201 OST - Sample Templates PV600 SV100 PAM - Predictive Analytics 123 PV620 SV103 NOTE: Does not require Data Science package. PLP - People Planning PV620 SV102 RCM - Account Reconciliations (OFC PV710 SV201) Platform 7.0 and earlier - Upgrade RCM to PV440 SV200+ and upgrade to v8+ compatible OFC Platform 7.1.1 - 7.4.4 - Upgrade to v8+ compatible OFC SML - Sensible Machine Learning PV650 SV221 TXM - Transaction Matching (OFC PV710 SV201) Platform 7.0 and earlier - Upgrade TXM to PV530 SV201+ and upgrade to v8+ compatible OFC Platform 7.1.1 - 7.4.4 - Upgrade to v8+ compatible OFC UTM - Task Manager PV660 SV102 XAT - XperiFlow Administration Tools PV650 SV100v8+ Upgrade and .NET
Let's talk .NET in non-technical terms and describe it's impact on OneStream Platform v8+ uprades. .NET is the development platform used by OneStream to build the Platform. Prior to Platform v8.0, OneStream used versions of .NET referred to as .NET Framework versions. The v7.x Platform release used .NET 4.8. The development of Platform v8.0 used .NET6, referred to as a .NET Core version. The .NET Core versions leverage modern development paradigms and are much faster! OneStream customers upgrading to Platform v8+ are observing performance improvements in memory intensive operations such as Consolidation processing, and several data loading / copying processes. The modern paradigms of .NET Core had an impact on OneStream Business Rule compilation - older syntax and library references that were not .NET Core compatible failed compilation. This required some minor updates to MP Solutions and customer created Business Rules. No sweat - a one time adjustment with your pre-v8 to v8+ Platform upgrade. OneStream plans to follow Microsoft's Long Term Support (LTS) release cadence for .NET Core versions - every two years. Platform v8.0 and Platform v8.1 used .NET6. The next two years of releases beginning with Platform v8.2, we will use .NET8. See the chart below: OneStream customers must ensure all desktop/laptops providing Windows Client access to OneStream have the corresponding version of .NET Desktop Runtime installed. With v8.0 and v8.1, we recommended version 6.0.14 or higher (within the 6,x line). With v8.2 (target late March 2024), we recommend version 8.0.2 or higher (within the 8.x line). Note: The OneStream Windows Client WILL NOT connect to a v8.0 or v8.1 Server without the existence of a version 6.x of the .NET Desktop Runtime. In other words, a .NET8 Desktop Runtime install isn't 'backwards' compatible. However, .NET8 and .NET6 Desktop runtimes may co-exist together and live in harmony 🙂 See the Microsoft .NET page for support dates and downloads. Notice that Microsoft has indicated an End-of-Service date for .NET6 at November 2024. After this date, Microsoft will not issue patches for issues related to .NET6. OneStream recommends maintaining compliance with Microsoft's .NET support dates - therefore customers running Platform v8.0 or v8.1 should plan an upgrade to Platform v8.2 or higher by the end of 2024. OneStream is targeting Platform releases in March, July, and November of 2024. Platform upgrades from v8+ to higher versions follow tranditional (simple!) upgrade processes. See the chart below to see the .NET6 End of Service impact: We hope this information provides you insightful background on all things .NET! If you have further questions or require clarification, feel free to add your comment in a reply below.DLL FAQs
Why are we writing an FAQ for DLL file management with Platform v8+? In alignment with the goal of 100% customer satisfaction, the OneStream platform is evolving so that Cloud Operations can deliver superior performance, functionality, and customer self-service. This effort requires OneStream to transition existing paradigms and policies to modern cloud native approaches that embrace enhanced capabilities. With Platform v8+, OneStream is facing this challenge by requiring adoption of modern technologies, and creating cloud native procedures that exhibit higher levels of security and automation. With that theme in mind, we are strongly recommending changes to DLL file management to ensure a robust, yet secure cloud operations paradigm. What is changing in Platform v8+ with regards to DLL file management? With the transition from VPN to Smart Integration Connector (SIC) in Platform v8+, any custom DLL used within your application for data source connectivity will be transitioned from its pre-v8 source location in the cloud to the Local Gateway Server Referenced Assemblies folder, which exists within the customer’s network. Typically these DLLs are used to establish connectivity or encrypt data from a local data source. Locally installed DLLs can be leveraged by SIC in a number of ways, including through SIC remote business rules. What are the standard DLLs included with the OneStream Platform and how are they invoked by Business Rules? With v8, the following DLL files are installed with the OneStream Platform: DocumentFormat.OpenXml.dll HtmlTextWriter.dll IronCompress.dll Microsoft.AspNetCore.Mvc.NewtonsoftJson.dll Microsoft.Bcl.AsyncInterfaces.dll Microsoft.CodeAnalysis.CSharp.dll Microsoft.CodeAnalysis.dll Microsoft.CodeAnalysis.VisualBasic.dll Microsoft.Data.Analysis.dll Microsoft.Data.Edm.dll Microsoft.Data.OData.dll Microsoft.Data.Services.Client.dll Microsoft.Data.SqlClient.dll Microsoft.Extensions.Configuration.Json.dll Microsoft.Identity.Client.dll Microsoft.Identity.Client.Extensions.Msal.dll Microsoft.IdentityModel.Abstractions.dll Microsoft.IdentityModel.Clients.ActiveDirectory.dll Microsoft.IdentityModel.JsonWebTokens.dll Microsoft.IdentityModel.Protocols.dll Microsoft.IdentityModel.Protocols.OpenIdConnect.dll Microsoft.IdentityModel.Protocols.WsFederation.dll Microsoft.IdentityModel.Tokens.dll Microsoft.IdentityModel.Tokens.Saml.dll Microsoft.IdentityModel.Xml.dll Microsoft.OData.Client.dll Microsoft.OData.Core.dll Microsoft.OData.Edm.dll Microsoft.Rest.ClientRuntime.dll Microsoft.SqlServer.Server.dll Newtonsoft.Json.Bson.dll Newtonsoft.Json.dll Parquet.dll Polly.dll Rsk.Saml.dll SkiaSharp.dll Snappier.dll System.CodeDom.dll System.Collections.Immutable.dll System.Configuration.ConfigurationManager.dll System.Data.Odbc.dll System.Data.OleDb.dll System.Data.SqlClient.dll System.Net.WebSockets.WebSocketProtocol.dll System.Spatial.dll System.Text.Encoding.CodePages.dll System.Text.Encodings.Web.dll System.Text.Json.dll System.Web.Services.Description.dll WinSCPnet.dll ZstdSharp.dl To utilize a DLL file from this list in a Business Rule, list the name of the DLL in the Referenced Assemblies setting. You can reference multiple assemblies by separating the names with a semicolon: How do I reference a Microsoft DLL packaged with .NET6 in my OneStream Business Rule? Reference a Microsoft DLL in the same way as you would DLLs packaged with the OneStream Platform, as outlined in the previous FAQ. From the Properties tab of the Business Rule, simply refer to the DLL file name (such as “System.IO.Compression.DLL”) in the Referenced Assemblies setting. I’m a new cloud customer, provided OneStream Platform 8.0 (or higher) – can I ask OneStream to place DLL files in the cloud Reference Assembly Folder? Our guidance to new customers adopting Platform 8.0 or higher is to not have DLL files in the Storage Account ‘Integrations’ folder . This practice has been discontinued in alignment with our new Cloud Operation practices. I’m an existing cloud customer, with existing Business Rules that reference DLL files in the cloud Reference Assembly Folder. Can I continue having these DLL file references ? All custom DLL files necessary for local data source integration will need to be transitioned from the OneStream Reference Assembly (“Integrations”) Folder to the Local Gateway Server. This transition will be included in the upgrade plan. Other DLL file references may continue with Platform v8+. This policy is under review and any changes will be publically announced with a one year notice. Continue to use the XF\<dll file name> syntax in the Business Rule Reference Assemblies (“Integrations”) folder to reference these DLLs. Is the ‘Integrations Folder’ the same thing as the ‘Reference Assemblies Folder’? Yes I’m an existing cloud customer upgrading to Platform v8+. Can I store DLL files in the ‘Bin’ folder? No, this is a reserved folder. Has OneStream observed commonly used DLLs failing compilation because the DLLs are .NET framework based? Are .NET Standard or .NET Core equivalents known? Yes. Here are a few examples. If you have any questions, feel free to contact OneStream Cloud Management during the Migration Phase of your v8+ upgrade. .NET Framework DLL failing v8+ compilation .NET Std or .NET Core equivalent Microsoft.Azure.Storage.Blob AzureBlob.zip Microsoft.Azure.KeyVault AzureKeyVault.zip Microsoft.Azure.Storage.File AzureFile.zip Google.Apis.Storage.V1 GoogleS3.zip AWSSDK.S3 AWSS3.zip Netstandard (now included in OneStream install) WinSCPnet (now included in OneStream install) Microsoft.WindowsAzure.Storage.xxx <research tbd> Note: zip files are to be unzipped and DLL file contents replace the corresponding .NET framework version files DLLs that must be transitioned to the SIC Local Gateway Server with v8+ .NET Framework DLL failing v8+ compilation .NET Std or .NET Core equivalent Microsoft.Office.xxx Microsoft.Office.xxx (requires Microsoft license) Oracle.ManagedDataAccess Driver version of DLL is included with Local Gateway Server installPlatform Features by Release 8.0.0 Release Features
These are the features released with 8.0.0. Journal Workflow Enhancements Workflow Profile Security Settings There are two new journal security properties that control self-approval and self-posting. Users need the ability to approve/post journals submitted by other users, but should not always be allowed to approve or post their own. Property Name Description Prevent Self-Approval If True, users can only approve journals submitted by another user within the Workflow. If True (include admins), this will apply to Administrators (anyone in the Administrator Group) in addition to the Workflow users. Prevent Self-Post If True, users can only post journals submitted by another user within the Workflow. If True (include admins), this will apply to Administrators (anyone in the Administrator Group) in addition to the Workflow users. Workflow Profile Control Settings Property Name Description Require Journal Template (t/f) If True, users can only make journal entries using a template. The Create Journal button is disabled in the Workflow. Can Load Unrelated Entities (t/f) If False, users can only make journal entries to the Entities assigned to the Workflow. If True, Entity selection is determined in the journal entry (current behavior). Default is True. Copy Journals You can now copy multiple journals to multiple time periods directly from the Workflow rather than using a Business Rule. Validate Journals You now have the option to manually validate journal intersections when submitting or approving journals. This helps make the Journal Workflow more efficient as errors can be fixed earlier in the process rather than right before posting them. Additional Journal Enhancements You can now delete journals in bulk rather than one at a time. Enable UD Dimension Descriptions to display your UD descriptions in the journal's POV. Note: these are derived from the UD Descriptions under Application Properties. Member Descriptions now display in the journal's line items. This is applicable to all editable Dimensions (those located in your Dimension Library). General Ease of Use Enhancements Data Management and Form Template Copy & Paste Functionality You can now copy/paste Data Management Steps and Sequences as well as Form Templates. Note: This can be done within the same Group or across Groups. Data Management and Form Template Rename Functionality You can now copy/paste Data Management Steps and Sequences as well as Form Templates. Business Rule Confirm Undo The Business Rule editor will now prompt you upon clicking the 'cancel all changes since last save. 8.1.0 Release Features These are the features released with 8.1.0. Journals Copying Journals Across Scenarios The initial journal copy feature made its debut in 8.0 allowing users to copy journals across time periods. With this new feature, you can copy one or more journals to one or more time periods for a given scenario. Export Journals to Excel Template You can now easily create your own Journal Excel Template by exporting select journals directly from the Workflow. Now, you can take advantage of this feature through the new Export to Excel Template icon to the Journal Entry toolbar. This icon will allow you to choose the necessary journals to use as the template's starting point. Workspaces Data Management and Workspaces Data Management joined the Workspaces page. Now, you will notice a few key additions: Maintenance Units have a new Data Management Groups section where your steps and sequences are stored. The Workspace toolbar expanded to include the create step and create sequence buttons. The legacy Data Management Page is still present, and the existing Application Security Roles still apply. Cube Views Long Running Cube Views and Task Activity You will now be prompted to cancel the task if a Cube View takes longer than 10 seconds to render. This cancellation occurs immediately and prevents the task from running/processing in the background. You will also notice a change in Task Activity. Here, you an easily see long running tasks and was updated to ensure it provides proper task statuses upon cancellation and logging detail for Cube Views. Spreadsheet/Excel Add-In Create Quick View from Cube View via Data Explorer Grid You will now notice a new right-click option within your Cube View Data Explore grid. This option will launch a new tab within the Windows Application that creates a Quick View based on the selected Cube View Cell within Spreadsheet. XFGetCell Drill Down Drill Down now exists for XFGetCells in Spreadsheet and the Excel Add-In! You will see the Drill Down option when right-clicking on an XFGetCell. This option follows standard Drill Down behavior you have grown to know and love. Task Activity in Excel Add-In Task Activity is now accessible from the Excel Add-In OneStream toolbar. Identity Access Management (IAM) SAML IdP User Management SAML IdP self-serve management has been enhanced in the IAM portal. You can now manage SAML IdPs more efficiently through auto-discovery or importing an xml file. Smart Integration Connector (SIC) IP Whitelisting With the release of 8.1, we added an IP whitelisting option for ingress communication to both the Local Gateway Server and to the Azure Relay service. This is for our customers who want to filter/limit connection traffic. SIC Utility Enhancement The SIC utility was enhanced in 8.1 to auto-open the XFGateway Config file. This will ensure the correct config file is selected. If it can't find the default file, a new file will be generated upon which the user is notified.Modern Browser Experience
All new customers to Platform v8+ and those upgrading to v8+ have the choice to enable BrowserUX in their non-prod and/or prod instances. BrowserUX has established browser access to OneStream and provides for the comprehensive end-user experience. For SaaS customers - Modern Browser Experience for Platform Version 8.4+, you no longer need to log a ticket or contact your Customer Success Manager. On Platform versions 8.4+ and later, the Modern Browser Experience will be included with every release. For Self-Hosted customers there is additional configuration required to enable it, which is outlined in the modern browser experience user guide. Please reach out to Customer Support for further assistance. The BrowserUX Guide can be accessed at the OneStream documentation site.