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
Post 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,
Post an idea
Upvote ideas that matter most to you
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 notification 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.
For product documentation, see Knowledge Center. Create and View Support Cases and Use the Discussion Forum here
Workflow: Extending the concept of auto start to also encompass auto-transition from one stage to another
In a similar way to auto-start, there will be instances where we would want the workflow to move onto another stage when the conditions and validations are met, without the user having to do this.
- If using the Custom API to create objects (e.g. Evals), then this would require this Custom API as a stage, followed by an additional stage to populate the values of the new record by using conditions. The user doesn't care that this is a two stage process - for them it's a single process to create a fully populated Eval. We shouldn't ask them to have to manually movce the stage on
- When a user makes a record inactive, we'd like to end the workflow for them, but instead they have to choose the finish stage off the action button, then decide whether they are finishing due to an object closing, or being made inactive.
- When a control is collected, we'd like to automatically move it to an awaiting collection stage (to make use of the operations)
Do not place IBM confidential, company confidential, or personal information into any field.