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.
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.
Email notification when API task is failed in Activity
Whenever activity failed due to any reason an email should get triggered. So that current search manual work will be reduced and also this functionality will increase the sponsor user experience.
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.
It would be better if we can
-> had a failure handling option in PEM (like on fault in SI)
-> call another activity from one activity
Let us know, for more details
Be able to rollout activities based on the union (common partners) of multiple attributes
Currently, when rolling out an activity, you have the option to do so using groups, attributes or by selecting individual partners. If you choose attributes, you can specify multiple attributes upon which to invite partners but the behavior is th...
Able to View Sponsor Task before the Task is complete
When we are executing an activity and are in the middle of Sponsor Task and there is a Exit Validation Error. Now, if we want to see what components are ran in that task, we can't because there is no View Option, when the Task is in progress.FYI :...
Rich Text Functionality for Labels
Would like to be able to change the font style, size and color within one single label. Currently you are required to have multiple labels if you want different text formatted differently.
"End of Task" Dialog Update
We would like to request a change in the current workflow. When a task has entry and exit conditions which cause the last dialog in the task to be skipped a confirmation box appears stating, ‰ÛÏYou have reached the last dialog of the task. Do you ...
Do not place IBM confidential, company confidential, or personal information into any field.