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 product management 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.
Facility to import configuration of the Loss Event Entry app from older to newer versions of OP
Backup should include the configuration files as well like aurora.properties file . The aurora.properties file from old 7.3 version cannot be imported as all the other entries in aurora.properties are different and have to be modified as per 8.0 v...
Workflows: Include support for mathematical operations/transformations in Expressions
It'd be a great addition if we can evaluate mathematical expressions as conditions or operations in Native Workflow.Sample use cases:1. Operate on a field, making it 1.2 times its original value.2. Operate on another field, e.g., adjust the value ...
Enabled / Not enabled checkbox on Workflow configuration Page
Extending the concept delivered to end users on Grid Views (for inactive records), it would be very useful to the developer to be able to exclude workflows that are not enabled, so that redundant workflows do not clutter the screen. This is most u...
Constrain who is allowed to start a particular workflow
We would like to control who can start particular workflows.
Use Case 1: As an oversight user responsible for a large area, I want to personally control which Loss Events get re-opened. If I let anyone do it, I end up wasting time chasing them.
Provide more granular control of actions - i.e. Add New, Copy, Edit
Ability to provide more granular control of Action dropdowns to limit specific actions in the UI, such as Add New, Copy, Edit, Associate, Disassociate, Delete, Submit. There are specific business rules that require us to disallow "Add New" action ...
System: OpenPage v7.0The same authenticated user can log into the application from multiple browsers or locations. We want to have a setting in the application to disable this feature, as it poses a pentential security risk.
Admin: Allow to configure Lock/Unlock at Object/Profile level
The Lock/Unlock permission is at a application level. We would like to be able to selectively allow/block that capability by Object Type and/or Profile. There are numerous cases where there exists a need to have more granular control of this feature.
Admin: Allow ability to allow View-only of configuration settings vs. Edit for all
Today if you have access to a particular Administration function, you are able to edit that function. We would like to be able to have a setting that can limit edit capabilities, but allow View of these settings.
Do not place IBM confidential, company confidential, or personal information into any field.