Release 26.08.110¶

Version	Test release	Production release	Agent update
26.08.110 (August 2026)	August 21, 2026	August 31, 2026	No agent update

Highlights¶

This is a minor release containing new features and enhancements to existing features, and API additions. The features of this release were developed to enhance the design capabilities, performance, and improve ease of use of applications. System administrators and users will benefit from the enhancements across their application.

Email: new tags for application and dimension names and prior-stage approvers, plus separate Approve and Reject line templates
Bulk Upload: customizable templates by property category, hierarchy action, or required properties
REST APIs: request line details and member properties
Validation: a child Delete Member line can't be deleted or canceled while an ancestor is being deleted
Performance: large ERP Imports, the Metadata Audit Report, and deployments for large applications
Fixes: OneStream text containing colons, Essbase BSO Dynamic Calc parent and child members, and request locking after Bulk Upload

New Features¶

None in this release. New capabilities are listed under Enhancements.

Enhancements¶

EW-2616: New Email Tags for Application and Dimension Names¶

Added new email tags that can be used in Review and Approve email templates to display application and dimension information associated with a request.

The following email tags are now available:

<APP_NAMES>
<DIM_NAMES>
<APP_AND_DIM_NAMES>

Example: If a request contains two applications and five dimensions, the tags will return values similar to the following:

<APP_NAMES> → HFM, Essbase
<DIM_NAMES> → Account, Product, Project, Measures, Scenario
<APP_AND_DIM_NAMES> → HFM:Account, HFM:Product, Essbase:Project, Essbase:Measures, Essbase:Scenario

EW-2580: Custom Bulk Upload Template Options¶

Enhanced the Bulk Upload template download process to allow users to generate customized templates based on property categories, hierarchy actions, required properties, or all properties.

This improvement is especially useful for customers with large Generic Applications and many properties, where different users are responsible for different categories of metadata.

When users choose to download a Bulk Upload template, a new popup allows them to customize the template using the following options:

Property Categories

Users can select property categories they have access to. This prevents users from uploading metadata for properties they are not responsible for managing.

Hierarchy Actions

Users can select from the eligible hierarchy actions for the selected dimension. Only actions available for the dimension and the user are shown.

Show Required Properties Only

A checkbox allows users to include only required properties in the downloaded template. This option is unchecked by default.

The Download button is enabled by default in the new popup.

EW-2586: Notify Prior Stage Approvers for Reject and Recall Actions¶

Added functionality to notify users who approved or reviewed a request in prior workflow stages when a request is rejected or recalled.

This enhancement includes the following changes.

1. New Email Tag: <PRIOR_STAGE_APPROVERS>

At runtime, this tag is replaced with the email addresses of all users who approved the request during previous approval stages.

This allows prior approvers to be notified when a request is rejected later in the approval workflow or recalled to the start.

2. Separate Email Template for Reject Actions

Previously, the same email template was used for both approve and reject actions on request lines.

This has been split into two separate templates:

FYI: Request Line User Action - Approve
FYI: Request Line User Action - Reject

3. Use of the New Email Tag

The following templates can optionally use the new <PRIOR_STAGE_APPROVERS> email tag in the To or CC field:

FYI: Request Line User Action - Reject
FYI: Recall Request from Workflow

4. New Workflow Task Email Template Field

Workflow Task configuration now separates approval and rejection email templates.

The existing field has been renamed to:

Approve Line

A new field has been added:

Reject Line

Default Values:

Approve Line: FYI: Request Line User Action - Approve
Reject Line: FYI: Request Line User Action - Reject

EW-2601: New REST APIs for Request Line Details and Member Properties¶

Added new REST APIs to fetch detailed request line information and member property details.

Previously, REST APIs were available to fetch request header details. These new APIs provide line-level information.

Request Line Details API: Returns the information displayed in the Request Lines grid on the Request page, excluding line action LOV choices.

Member Properties API: Provides member property details using a supporting database view.

EW-2605: Prevent Delete or Cancel of Child Delete Member Line When Ancestor Is Also Being Deleted¶

Added validation to prevent users from deleting or canceling a request line with the Delete Member hierarchy action if the member's parent or any ancestor is also marked for deletion in another request line.

This prevents orphan members from being created.

Example:

Create Request #1 to delete a child member.
Create Request #2 to delete the child member's parent.
Attempt to delete or cancel the child member delete line in Request #1.
The system now prevents this action because the parent or ancestor is already marked for deletion.

This ensures hierarchy integrity is maintained.

EW-2606: Metadata Download from Explorer Missing Shared Instance Properties¶

Resolved an issue where downloading metadata from the Metadata Explorer or Request page did not include member-level properties for shared instances when the selected top member contained only shared instances.

Steps to Reproduce:

Select a top member that contains shared instances but does not contain primary instances in that branch.
Use the Excel icon from the Metadata Explorer or Request page to download metadata.
Member-level properties such as Alias, Account Type, or UDA were missing for shared instances.

This issue has been corrected.

EW-2610: Performance Improvement for Large ERP Import Processes¶

Improved performance for large ERP Import processes, especially those containing 100,000 or more records.

Previously, large ERP Import executions could show inconsistent run times, where the same dataset sometimes processed quickly and other times processed much more slowly.

Database views used by ERP Import have been tuned to provide more consistent performance.

EW-2612: Performance Improvement for Metadata Audit Report¶

Improved performance of the Metadata Audit Report, especially when executed across all applications.

EW-2617: Deployment Performance Improvement for Large Applications¶

Improved deployment performance for large applications, especially HFM and Planning application types.

A deployment step that generates data for empty property records was optimized to provide better performance for both direct and file-based deployments.

Fixed Issues¶

EW-2602: OneStream Text Fields Do Not Display Values Correctly When Text Contains a Colon¶

In OneStream applications, text field values were not displayed correctly when the text contained a colon character (:).

This issue has been corrected.

EW-2603: Essbase BSO Deployment Failure When Creating Dynamic Calc Parent and Child Members¶

Essbase BSO deployments failed when a new parent and child member were created together and both members had Data Storage = Dynamic Calc.

Scenario:

Select an Essbase BSO application and the Account dimension.
Select a member that has Data Storage = Label Only.
Create a child member with Data Storage = Dynamic Calc. Example: P1.
Create a child member under P1 with Data Storage = Dynamic Calc. Example: C1.
Ensure C1 has a member formula. Otherwise, Essbase will throw an error during deployment.
Deploy the request.

Previously, the deployment failed with an Essbase error indicating that when a single child member is Dynamic Calc or Dynamic Calc and Store, the parent must also be Dynamic Calc or Dynamic Calc and Store.

This issue has been resolved.

EW-2604: Bulk Upload Request Description Save Locks Request¶

After performing a Bulk Upload in a request, updating the request description and clicking Save incorrectly stored the Task ID on the request header.

As a result, the system treated the request as still being processed, causing it to remain locked and marked as In Progress.

Steps to Reproduce:

Create a request and add a description to the header.
Perform a Bulk Upload.
After successful submission, verify that request lines are created with status New.
Update the request description and save.
The workflow and line statuses were incorrectly changed to Pending.
If the user attempted to recall the request, a request locked error was displayed.

This issue has been corrected.

EW-2618: Drill-Through to Newly Created OneStream Extended Members¶

Drilling from the Request Lines grid to an extended member in OneStream did not always navigate to the correct line member when the member was newly created in the dimension.

Example: A new member is created in the OneStream Entity dimension, such as 1313 under Concentra. The same member is then created in the extended dimension, such as ConsolidatedSM, under a parent. Drilling from the request line should navigate directly to that member in the consolidated dimension.

This issue has been resolved.

Known Issues¶

None listed for this release.

Action Required¶

No agent update is required for this release.

Deprecations¶

None listed for this release.

Questions about this release? Contact EPMware Support or email support@epmware.com.

Legal notice

Any warranty with respect to the software or its functionality will be expressly given in the Subscription License Agreement or Software License and Services Agreement between EPMware and the warrantee. This document does not itself constitute a representation or warranty with respect to the software or any related matter.

EPMware Software and the EPMware logo are trademarks of EPMware Software in the United States and other countries. Oracle, Hyperion and OneStream are registered trademarks or trademarks of Oracle and OneStream Software Corporation in the United States and/or other countries. EPMware is a registered trademark of EPMware, Inc. Other names may be trademarks of their respective owners.