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 for token authentication
Some of REST APIs for IBM products have token authentication implemented. I.e., call a sign in API to get a token, and then use the token in a HTTP Header for all other API calls.
IBM Sterling Secure Proxy: https://www.ibm.com/su...
Status "Wait Queue" on SMF record
Add the Wait Queue" statuses (WC, WP, WT, and WX) in the SMF records.
Add TLS 1.3 Support to Sterling B2B Integrator
Partner invitation should identify the duplicates and warn the sponsor.
PEM should throw an warning saying that the user is already registered or Invitation sent to partner as soon as sponsor clicks on Invite button and the a partner is registered with that Email Id already.This avoid sending the duplicate invites to ...
Safety Stock at Node Level
Enhancements to support Safety Stock at Node Level.Would require an IV API which accepts input at Ship Node and Safety Stock quantity.Node Level Safety Stock applies to all items present in the ship node if there is no safety stock configured at I...
Store more than 10 data fields
Often we have scenarios where SFG Solution uses external database tables. These tables can have any number of columns. When PEM activities are customized to collect data from sponsor/partner for the table and if the number of columns is more than ...
IDoc Control Record must contain tag EDI_DC40_U for Foreign Language to be in readable format within the SAP Environment
Changing the Control Record EDI_DC40__ (__ equals two trailing spaces) to EDI_DC40_U (one space and a U). Which when exported to a single file the output is okay, but the very first field in the record is 300, so the output = "EDI_DC40_U300" the f...
InFlight - Add Protocol Process ID as an addable column on search page
Adding Protocol Process ID as a visible, searchable field in the results page would allow isolation of traffic by connection for easier troubleshooting. This would be beneficial for both clients and support, and seems like it should be easy to im...
Trigger SupplyChange Event based on change in timestamp in addition to quantity change
Currently, IV triggers supply change event for an item only when there is an update to supply bucket quantity. To make the event updates robust, we need capability to generate the events on the change of timestamps.
Remove the validation of the X520SerialNumber in the PKI-J toolkit
An error occurred when updating a certificate for a client with a Serial number too long issue. Certicom found that certificate is not valid and cannot be used since the X520SerialNumber contains more than 64 characters which violates the RFC.
Do not place IBM confidential, company confidential, or personal information into any field.