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.
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Currently not under consideration for General availability. We might revisit and review for if there are critical business challenges.
Guest, sure the other idea is under B2BI-I-1108 the reason that it's not easily identified is because the two ideas are, this one, which is use Sterling Envelopes without the Sterling DocExtract Process and make the process more pure ITX, OR alternatively fix the Sterling DocExtract process so that even if the Sterling mapper isn't likely to support JSON any time soon at least if you are going to support it with ITX support the JSON single root take issue withing DocExtract the way you do XML data, or similarly.
I'm not sure if I have a strong opinion which one wins out ideally both should be options, my biggest concern is a volleyball match of each side throwing the issue at the fence at one another and neither happening. Which sort of started with the prior incident ticket which only got closed because our present ask needed differed enveloping but we don't want that to be something we need to do for everything because that doesn't always make sense and adds delay to more real time processes.
Is the second 'IDEA' is a separate AHA! ? If so, can you provide the number? If not, can you please open one with a bit more detail please?