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
Objectmanager export dependencies similar to UI configuration export
When you export profiles or other artifacts from the UI (Administration/Export Configuration), the tool export all the required dependent objects automatically. Allow similar dependency export via Object Manager Few options. 1) The UI already has ...
8.2 Workflow End Stages - set Notify Oversight to FALSE by default
Currently when editing a workflow and either changing an existing stage to an end stage, or creating a new end stage, the default setting for Notify Oversight is TRUE. This setting is not expanded by default so it is easy to spot the email is set ...
V8.1 TFUI – HeatMap Chart – allow sorting of X/Y axis values so that WORST appears top right corner.
The Heatmap chart for Risk needs to show Impact (Y) vs Likelihood (X) with worst values being top right. However, the order of the values in the enumvals currently determines the order resulting in worst Likelihood being on the left instead of rig...
V8.1 TFUI – Admin export for new TFUI Views must have option to export WITHOUT schema content to allow deployment without impacting enumvals/field dependencies etc.
Development of TFUI views will happen over a number of months with incremental deployment. The underlying field definitions, field values (enumvals) and dependent picklists are all exported too making it difficult to migrate just the views onto a ...
Performance of Admin UI Import very slow compared with Object Manager importing the same XML
The performance of Admin UI Import is much slower for Object Types and Profiles than Object Manager. The same XML files when loaded via object manager vs Admin UI import timings are below:
- Object Type = SOXDocument, SOXExternalDocument. UI = 1 ...
TFUI - Make validation and operation definitions re-usable across stages within workflow and across workflows
Many validation and operations would occur during many/all stage transitions. Currently the whole definition has to be re-entered for every stage required which is error-prone and time-consuming.
Ideally it should be possible to define the val...
Admin Export should either export the selected dependent picklists and field dependencies or remove the optiion to make the specific selections
The current Admin export feature allows you to select specific field dependencies and specific dependent picklists - however the XML exported contains ALL rather than the selected ones.
Ideally the export XML should only contain the selected i...
In addition to the existing filters on 'Workflow Instances', it would be very useful to be able to filter by folder path. Ideally this would form part of a cut-down Business Admin access, but if not, it's still useful if the system administrator h...
Allow more complex evaluation conditions in JSON rules
Currently, the field types supported for editable/readonly, and visible/hidden rules in JSON are only enumeration and actor fields, and rules are defined as all-AND (allOf) or all-OR (anyOf).
There is no way to:
make a field visible or require...
Do not place IBM confidential, company confidential, or personal information into any field.