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
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,
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 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 that cannot be implemented in a reasonable time.
Please use the following category to raise ideas for these offerings for all environments (traditional on premises, containers, on cloud):
Cloud Pak for Automation - incl Business Automation Studio, Business Automation Insights
Business Automation Workflow (BAW) - incl BAW, Business Process Manager, Workstream Services, Business Performance Center, Advanced Case Management
Content and Capture Services - incl Filenet, Automation Document Processing, Daeja, Navigator, Content Collector, Enterprise Records, Business Automation Content Analyzer, Datacap, Automation Mobile Capture, Content Manager OnDemand, IBM Content Manager
Robotic Process Automation with Automation Anywhere
IBM Blueworks Live
If you encounter any issues accessing the Ideas portals, please send email describing the issue to firstname.lastname@example.org for resolution. For more information about IBM's Ideas program visit ibm.com/ideas.
Extend migration policy to support move token without token orphanization and restarting of tasks
When defining a migration policy, it should also support move token for steps that arent orphaned, to support rerunning added steps prior to the current task. The migration policy should also support restarting of tasks, that currenty would crash due to extensive internal changes in it.
Why is it useful?
When making extensive changes inside a task the task might need to rerun its constructors, or take in more data from the process instance. If tokens could be moved without the step being removed in the instance, this would simplify this matter.
Tasks should also be able to be "restarted", so all their internal steps will be rerun, and their startdata read in anew.
Our current solution is a tool to move tokens with, where we move the token to the step it already is standing on, to force a task recreation. This however recreates the task, resulting in a new taskId, recreated due date for the task, removed assignment, which is a behaviour that we would rather avoid.
Do not place IBM confidential, company confidential, or personal information into any field.