Skip to content

Release 26.09.111

Version Test release Production release Agent update
26.09.111 (September 2026) September 11, 2026 September 25, 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.

  • New APIs: return unmatched members within a branch, and exclude request lines from deployment
  • Request lines: reordered when a new member is moved under a newly created parent
  • Renames: error when a member is recreated with a renamed member's original name
  • PBCS: Application Import handles dimension names that contain parentheses
  • Deployments: temporary tables are purged after deployment completes

New Features

None listed for this release. All items in this release are listed under Fixed Issues.

Enhancements

None listed for this release.

Fixed Issues

EW-2613: PBCS Application Import Fails When Dimension Name Contains Parentheses

PBCS Application Import failed when a dimension name contained parentheses.

For example, if the dimension name was Attribute (Growth), Oracle Snapshot converted the opening parenthesis ( to %28 and the closing parenthesis ) to %29 in the file name. As a result, EPMware could not locate the expected file during the import process.

This issue has been corrected so that dimensions with parentheses in the name are handled properly during PBCS Application Import.

EW-2619: Show Error Message When a Member Is Renamed and Recreated with the Same Name

Previously, if a user renamed a member and then created another member using the original member name, the system allowed the action. This caused unexpected issues in the Export module and created confusion for users.

EPMware now prevents this scenario and displays an appropriate error message when a user attempts to recreate a member using a name that is already involved in a rename action.

EW-2621: New API to Return Unmatched Members Within a Branch

Added a new Hierarchy API to return unmatched members within a branch based on either a member name prefix or a property value criteria.

Business Use Case: Customers may need to identify branches that do not contain specific members and then either delete those branches or move them to a parent outside the main branch.

Package: EW_HIERARCHY

Purpose: The API scans members under a given Top Member Name and identifies members or branches that do not contain matched descendant members.

Example Hierarchy:

All Projects
  Alternate Projects
    Alternate Corporate Projects
      PRJ001
    Alternate APAC Projects
      Alternate Japan Projects

Case 1: If the requirement is to identify ancestors within the Alternate Projects branch that do not contain members beginning with PRJ, the API can return the unmatched ancestor branches.

Example parameters:

TOP_MEMBER_NAME   : Alternate Projects
MATCH_CRITERIA    : MEMBER_NAME_PREFIX
MATCH_VALUE       : PRJ
RETURN_MATCH_TYPE : ANCESTORS

Result:

Alternate APAC Projects

Case 2: If the requirement is to return each unmatched member instead of only the ancestor branch, the API can return all unmatched members.

Example parameters:

TOP_MEMBER_NAME   : Alternate Projects
MATCH_CRITERIA    : MEMBER_NAME_PREFIX
MATCH_VALUE       : PRJ
RETURN_MATCH_TYPE : MEMBERS

Result:

Alternate APAC Projects
Alternate Japan Projects

API:

PROCEDURE get_unmatched_branches
 (p_app_dimension_id  IN NUMBER,
  p_top_member_name   IN VARCHAR2,
  p_match_criteria    IN VARCHAR2,
  p_match_value       IN VARCHAR2,
  p_return_match_type IN VARCHAR2 DEFAULT 'ANCESTORS',
  x_members_tbl       IN OUT g_members_tbl);

Notes:

  • p_match_criteria may be MEMBER_NAME_PREFIX, a Property Label, or a Property Name.
  • If p_return_match_type = ANCESTORS, the API returns unmatched ancestor branches.
  • If p_return_match_type = MEMBERS, the API returns each unmatched member.

EW-2622: Reorder Request Lines When a New Member Is Moved Under a Newly Created Parent

When users created new members and then moved one of those members under a parent that was created later in the same request, the request line order became incorrect.

This caused deployment issues for applications such as Essbase and OneStream, where parent members must be created before child members. It could also visually confuse users because the request lines no longer reflected the final hierarchy order.

Example Scenario:

Users create two new branches:

Branch 1: Root → P1 → P2 → P3 → P4 → P5
Branch 2: Root → P6 → P7 → P8

If the user moves P3 under P7, the resulting hierarchy becomes:

Branch 1: Root → P1 → P2
Branch 2: Root → P6 → P7 → P3 → P4 → P5
                         → P8

However, the request lines may still show P3 created before its new parent P7, which can cause deployment failures.

Fix: EPMware now reorders request lines so that newly created parent members appear before their child members.

EW-2626: New API to Exclude Request Lines from Deployment

Added a new API to allow users to exclude specific request lines from deployment based on business requirements.

This API can be called from a Workflow Custom Task or from On Submit Workflow Logic Scripts.

Package: EW_REQ_API

Function: EXCLUDE_LINE_FROM_DEPLOYMENT

Input Parameters:

  • Request ID
  • Line Number

Output Parameters:

  • Status: Success (Y) or Failure (N)
  • Message

API:

ew_req_api.exclude_line_from_deployment
 (p_request_id IN NUMBER,
  p_line_num   IN NUMBER,
  x_msg        IN OUT VARCHAR2);

EW-2632: Purge Deployment Temporary Tables After Deployment Completion

Deployment temporary tables are now purged after deployment completes.

This helps prevent unnecessary data buildup and avoids potential performance issues in future deployment processing.

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

Copyright © 2026 EPMware Software. All rights reserved.

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.