Shape the future of IBM!
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
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
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,
1. Post an idea
2. Upvote ideas that matter most to you
3. 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 which cannot be implemented in a reasonable time.
Test Mode for Context Data
Since context data has been added to PEM we have created a second activity for transmitters who need the same activity rolled out to them multiple times. The issue with the second activity is that all APIs with the reference to context data automa...
Define Partner User Standard and Partner User Admin on approval screens
When a Partner Administrator receives a registration confirmation they must approve the Partner User. When doing so they must choose "Standard" or "Administrator" for the user. Without a description of each kind of user, the Partner's are choosing...
podman support for PEM
RHEL 8 native provides podman instead of docker. While it's possible to install docker ce on RHEL, that puts the user into unsupported area with RHEL 8 support. Would like to have podman as a support container engine.
Ability to add partner admin when original partner admin has not registered yet
Currently, it is only possible to send the registration email and the original activity roll-out to one partner administrator. We would like to be able to send the initial registration and activity roll-out to multiple users. Currently the alterna...
Give Sponsor access to SendGrid for PEM instance
We would like to request access for the SendGrid for the Sponsor.
Add New User ID Variable for Partner Invitation Email Templates
Sponsors (e.g. US Bank) want to be able to include the User ID that the partner should be using when they register in the partner invitation email.
Add more columns to table
PEM Dialog UI has the Table component, which helps in creating tables in the UI.
As per default, the Table creation is limited to 11 columns.
We have various scenarios, where we need to fill into more than 11 columns.
So, we request for an e...
Sponsor Log-In With Company Details for Multiple Users
The Sponsor typically has more than one user who administrates activities. They would like to be represented as one unit, as opposed to individual members of the company. Currently each partner/partner user must be registered separately and with t...
Support for STARTTLS with Office 365
There has to be many companies using Outlook with Office 365. This Mail server requires STARTTLS, but it does not work with Pem Standard
Provisioner activities should acknowledge parent PEM activities on failures
The provisioner activities should send acknowledgement to parent PEM activities on failures, this is must needed else the Parent activity doesn't know what happened to the triggered provisioner activities. The Sponsor admins will be not notified a...
Do not place IBM confidential, company confidential, or personal information into any field.