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.
Support of IBM WebSphere MQ 9.2
IBM have not claimed support for WebSphere MQ 9.2 support in Sterling B2B Integrator.The enhancement request is for the support of WebSphere MQ 9.2 in Sterling B2B Integrator. The latest version of IBM WebSphere MQ is 18.104.22.168.
Using Valid JSON Schema as the Type tree in the Output Layout ,Array Element/Values are getting generated without closing square brackets
In JSON Output, Array Element/Values are generated without square brackets
When we use the Valid JSON Schema as the Type tree in the Output Layout ,
ITX reading the JSON Schema successfully, but the Array Elements/Values are getting generated ...
need delete option for S3 and SQS Adapters
Verify ControllerWorkflow is functioning properly in 22.214.171.124 with regard to force terminate
ControllerWorkflow.sh doesn't seem to be force terminating a BP when it is in a halting or active state when the BP shows it is in wait queue.
Installation Manager Documentation
IM should be simple to install and easy to use. Since the UI cannot be used for the install there needs to be explicit instructions on how to Install/Upgrade Sterling Integrator, including sizing and recommended location, considering the old way w...
Highlight False Relevancy
First off, I can't find anything that would be close to a Bigfix product in the product drop down. So, please route this and fix the drop down.
Install ALL components either as an User or Administrator
On a windows server things might react differently depending on which user with certain rights installs the software (Designer and Launcher). It shouldn't be a difference or the installer must check on having the proper options. We had some diffic...
ITXA - Option to turn off writing to Correlation_Set while using SPETransformationService
Our BP calls SPETransformationService for HIPAA data translation only. When our BP runs in sync mode (zero persistence), we observed many records created in correlation_set table, about 3 to 6 records per object_id, with names "Map", "MapVersion",...
Do Not Assume GET Responses
Currently, when using a GET API, the 'sample response' must have all values nullified, or the 'sample response' is treated as a default answer, even if the API is skipped. The purpose of the sample response is to provide data structure only - not ...
Remove the requirement for a keystore password when running a silent upgrade
A manual upgrade does not require a keystore password, but a silent upgrade does. Removing the need for this keystore password would simplify the silent upgrade process and be more secure.
Do not place IBM confidential, company confidential, or personal information into any field.