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.
Add ability to send e-mails from within a Portal activity
It would be beneficial to be able to send custom e-mails from within a PEM portal activity, as part of the workflow. For example, when a task for a specific group is the next task to be executed, the activity could be coded to send an e-mail to t...
Escape Special Characters in URL for Get Request
HTTP rest client's such as Postman typically allow for special characters in the Get request, PEM HTTP requests do not.
We would like the ability to complete sponsor and user tasks simultaneously.
Sponsor view to see all automated e-mailed sent
We would like to request a master view for the Sponsor of all the automatic emails sent. This master view should include, the date/time sent, the email content, and the recipient name.
Sending mass PEM registration email after bulk upload
In a project for migration partners from legacy MFT to SFG, we want to use the connectivity information of partners from legacy system. PEM campaign is used to inform partners of the move, and any change they have to make at their end. Automatic r...
PEM Cloud - Integration with Sterling Secure Proxy and Sterling File Gateway
Provide guidance on integration with other IBM systems (Sterling File Gateway, Sterling Secure Proxy, etc.) via API calls through Sterling Secure Proxy. Client is using PEM Cloud to make API calls to IBM systems located in the trusted network zon...
Add a flag to the get partners API to have the partners custom fields included in the results
For the get partners API (pemws/sponsors/<sponsorContext>/partners/) add an optional flag which indicates that the partners' custom fields should be included in the results. The custom fields are currently returned when retrieving a single ...
Provide the ability to create custom sponsor user types
Provide a way for a sponsor admin to define custom sponsor user types, beyond the current sponsor admin, LOB and standard users. For the various permissions, there should be a way to indicate what that role can do with each one (nothing, read onl...
API for "Invite Again" functionality
If partners are bulk uploaded but not sent an invite, the only way to send the invite is to manually click "Invite Again" in the UI. An API should exist for this.
Be able to rollout activities based on the union (common partners) of multiple attributes
Currently, when rolling out an activity, you have the option to do so using groups, attributes or by selecting individual partners. If you choose attributes, you can specify multiple attributes upon which to invite partners but the behavior is th...
Do not place IBM confidential, company confidential, or personal information into any field.