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
Subscribers in workflow need to allow for multiple fields
We have differing demands for oversight, often with different people performing oversight over each object
e.g. 1 Oversight of issues being completed on time, that a Risk or Control depends on to move from Red to Green. These people will be making sure that issues and actions are resolved on time, where the impact of not doing so would be detrimental to the business. This could be a single person or user group for one Business Entity.
e.g. 2 Oversight of work my team is responsible for, to ensure I plan effectively and know I am delivering timely resolution/ assessments etc. This is also likely to be a single person or user group for one Business Entity, but may not equate to the folder path, so does present us with a harder challenge (suggestions welcomed - we don't use enumerated strings, as we don't want to be dependent on a production release).
e.g. 3 Oversight that Loss events don't fester in planning stage, and that they move into remediation within the timescales laid out by Group Methodology. This might be at different levels of Business Entity e.g. one person doing it at group level, but someone else doing it for the Business Entity below it.
At the moment we can only have a single user / user group defined in workflow for oversight, but we'll need the ability to define multiple users / user groups that have oversight demand
Do not place IBM confidential, company confidential, or personal information into any field.