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
OpenPages 220.127.116.11 introduced the capability to anonymize data through a set of API methods. These methods do not work on encrypted fields, meaning that there is currently no way to anonymize data if it is stored in fields that are encrypted. When storing sensitive data in OpenPages it is a common practice to encrypt the data fields this data is stored in. Anonymization is generally applied to sensitive data. With the current restriction in the anonymization API it is not possible to anonymize sensitive data stored in encrypted fields, thereby severely limiting the usefullness of this new capability. Please either 1) provide the capability to anonymize data in encrypted fields in the anonymization API, or 2) provide a means to encrypt / decrypt fields through the API, so that the encryption on fields can be programmatically removed before performing the anonymization and then again applied after the anonymization process is complete.
Do not place IBM confidential, company confidential, or personal information into any field.