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.
Ability/ Option to clean up data loaded into IV via a self-serve option/ API
Currently, IV APIs do not give the option to clean up the data loaded into it via the integration with OMoC. There are APIs to perform adjustments or to zero-out the supplies/ demands and hence availability in IV (and thereby the process to clean ...
Allow Workflow to Continue After API has Failed
When creating an API dialog there should be an option to continue workflow even when the API fails. Preferably, it would have conditions to continue based upon what error is received.
Looping Functionality for Dialogs (UI, API, XSLT)
Many times it is not possible to know the number of times that you need an API to execute. Looping would allow the execution of an API or UI dialog to be dynamic. This could be utilized in a great number of use cases, one of which I outlined below.
Reports created in Cognos should be able to be scheudled and managed in SCC
The integration of Cognos has provided unending options for generating reports but anything created in Cognos is not visible to SCC for scheduling or management/modification through the GUI.
File Agent: sort capability missing to guarantee files sequence
FA doesn't provide a mechanism to process the files located in a specific folder in a specific order (i.e. file sorted by timestamp, name, size ). There are scenarios where the sequence the Producer Application generates the files must be respecte...
Supoprt for HDFS (Hadoop Distributed File System)
What version of Sterling Connect:Direct Linux/Windows will support Hadoop HDFS? Do you have any release date? I found similar thread at https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=65228 but I didn't see any updates.Th...
Validation failure message box
Currently it is possible to add validation to dialogs in tasks. When a partner does not complete/answer accurately there is no way to specifically tell them what to fix. There is a red X next to the field which is in violation, but not what they a...
Need SSL/TLS support for Global Mailbox to post its events to Control Center
Most other connections are firmly secured in B2Bi/SFG/GM, with one significant exception; the ability to post events and heartbeats from Global Mailbox to Control Center (ICC or CCM). By default, CCM 6.2 disables its non-secure web port, 58082. ...
compression at the HTTP layer
It would be good to have option like (something like compress="True") to compress the file at HTTP layer, to achieve this do we have any parameter set any of the HTTP Services/adapter level at HTTP Begin Session service/HTTP Client Method service...
Allow PS log file name to be configured with standard name
Currently the PS log file name is like PS.Logger.Dyyyymmmdd.Thhmmss. It should be configurable and follow the same name convention as what's used in CM and SSP etc.
Do not place IBM confidential, company confidential, or personal information into any field.