Skip to Main Content
IBM Sterling

This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Categories Maps & Type Trees
Created by Guest
Created on Aug 21, 2020

Improve performance of SERIESTOTEXT function

Currently the SERIESTOTEXT function does not distinguish the type of an object when the same field from the type tree is passed at different level.

To make things clear, below is an example of a typical ANSI X12 type tree and the 'X12 Segment' is a simple blob type field in the type tree.

The same field is being passed as different type of an object under the header & Message group.

Assuming the Header occurs 3000 times and the Message occurs 300,000 times in the input file , the SERIESTOTEXT function currently gets evaluated for 303,000 times for SERIESTOTEXT(X12Segment:Header)

When executed 3000 times, the run time of the rule is less than a second and when executed 303,000 times the rule completion time is around 55 seconds.

The current product behavior is that the SERIESTOTEXT(X12Segment:Header) & SERIESTOTEXT(X12Segment:Message) gets evaluvated 303,000 times as they share the same field .

Eventhough the right output is produced, the idea is to change the behavior so the SERIESTOTEXT takes the type of the object into account instead of just the name.

Typical X12 Message Type tree



- ISA Segment

- Header (0:1)

-> X12 Segment (s)

- Functional Group (s)

- GS Segment

- Message (s)

-> X12 Segment (s)

- GE Segment


What is your industry? Automotive
How will this idea be used?

The idea will improve the map performance to a great extent under all circumstance when SERIESTOTEXT function is used.

Currently we are ensuring that each field in the type tree has got a unique name to avoid issues. Changing the behavior would save lot of time and allows faster transformation.

  • Guest
    Sep 2, 2021

    We're unable to contain this work within the current archiitecture and within 12 month horizon.

  • Guest
    Aug 21, 2020

    Develpment to review