IBM Sterling Ideas
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:
Post your ideas
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you, 1. Post an idea 2. Upvote ideas that matter most to you 3. Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
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.
Do not place IBM confidential, company confidential, or personal information into any field.