Watson Campaign Automation Ideas
Submit new product ideas for Watson Campaign Automation, Watson Real-time Personalization, Watson Content Hub and Universal Behavior Exchange. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed.
Connect with your peers and IBM experts on the Watson Marketing and Commerce Community
Submit ideas for other Watson Customer Engagement Products:
• Other Watson Marketing solutions
• Watson Commerce
• Watson Supply Chain
Creating a constrained database allows user to choose a key during the set up. This key field may be email address but can also be other field depending on the need of the organization. But with implementation of GDPR, records have to be removed based on the Key field. But current setting for the database ( non-flexible or constrained Dbs) email address is set as default lookup field and it is not possible to add any other field as GDPR lookup keys in the database setting. Could we have this feature implemented same as in flexible database ?
How will this idea be used?
This feature will allow deletion of records based on Key field defined by the organization as single email address may be used across multiple accounts by users and they just want one of their account be removed as a part of GDPR request.
|What is your industry?||Travel & Transportation|
|What is the idea priority?||High|
|Link to original RFE|