IBM Sterling Ideas
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.
There are 2 requirements that lead to this idea:
1.) external requirements like GDPR force us to anonymize/pseudonymize data in non-production environments
2.) A-B-testing would be much easier if we can mask dynamic attributes (e.g. timestamps)
This idea is a solution for both requirements: we want to have a boolean attribute in the typetree on each field like this:
[x] mask in non-production environments
And we want to be able to run the ITX engine in test mode (non-productive mode), which has the following property: for all fields that are enabled to be masked in non-production environments TX does not apply the mapping rule. Instead TX writes the following static data:
text fields: X
numeric fields: 0
date fields: 1970-01-01
boolean (e.g. xml): true
Padding and formats must also be applied, so that the output data is valid.
|What is your industry?||Banking|
How will this idea be used?
This idea will be used in order to fullfil compliance and regulatory requirements. Another benefit will be simpler A-B-testing with less manual work, thus reduced costs and faster time-to-market.
Do not place IBM confidential, company confidential, or personal information into any field.