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

Bug fixes for addRecipient API call

Many of our clients have issues with using the addRecipient call to add a contact to a contact list. A developer for one of our clients found some bugs and has provided fixes on GitHub. See below info from the developer. Thank you!

.............................................................................................................................................................................................................

I've gotten things to work, but had to work outside the engage API because I could not get things to work with only the subset of API functionality provided by the Node package. I've opened 2 bug reports / feature requests for the workarounds I had to implement locally in order to get things working.

1.addRecipient incorrectly formats CONTACT_LISTS in XML request * Issue #18 * Silverpop/node-engage https://share.polymail.io/v1/z/b/NWIyZDg1Y2E5NTJh/lzh1f32gbMT7Ict5TlNrUJGTpVgbwueZDJZOsagpuofhbcvOTmRzASo_Ao655a1goqriychAmP1jsoH3LlRgMq2yN1aoHwYyrzoPnflSd0MJvnc59W3-A0oe8qZWqfF2vUp62sI1qP2KIbBjAojU2B4HsalPmgP3F4yRtOyZBdDsrwai0JAwSX7f0R6OiQTkE_WTTh8TrWj9BdqZMJYfCAWh

Cannot add a recipient specifying the contactLists option because the child items of CONTACT_LISTS is malformed. Currently being added as an array index, not CONTACT_LIST_ID. Can be fixed by adding the following to add-recipient.js if (t... https://share.polymail.io/v1/z/b/NWIyZDg1Y2E5NTJh/lzh1f32gbMT7Ict5TlNrUJGTpVgbwueZDJZOsagpuofhbcvOTmRzASo_Ao655a1goqriychAmP1jsoH3LlRgMq2yN1aoHwYyrzoPnflSd0MJvnc59W3-A0oe8qZWqfF2vUp62sI1qP2KIbBjAojU2B4HsalPmgP3F4yRtOyZBdDsrwai0JAwSX7f0R6OiQTkE_WTTh8TrWj9BdqZMJYfCAWh

GITHUB.COM https://share.polymail.io/v1/z/b/NWIyZDg1Y2E5NTJh/lzh1f32gbMT7Ict5TlNrUJGTpVgbwueZDJZOsagpuofhbcvOTmRzASo_Ao655a1goqriychAmP1jsoH3LlRgMq2yN1aoHwYyrzoPnflSd0MJvnc59W3-A0oe8qZWqfF2vUp62sI1qP2KIbBjAojU2B4HsalPmgP3F4yRtOyZBdDsrwai0JAwSX7f0R6OiQTkE_WTTh8TrWj9BdqZMJYfCAWh

2. RemoveRecipient is not implemented * Issue #19 * Silverpop/node-engage https://share.polymail.io/v1/z/b/NWIyZDg1Y2E5NTJh/lzh1f32gbMT7Ict5TlNrUJGTpVgbwueZDJZOsagpuofhbcvOTmRzASo_Ao655a1goqriychAmP1jsoH3LlRgMq2yN1aoHwYyrzoPnflSd0MJvnc59W3-A0oe8qZWqfF2vUp62sI1qP2KIbBjAojU2B4HsalPmgP3F4yRtOyZBdDsrwai0JAwSX7f0R6OiQTkE_TU4Z7-vCxqKehPBbBqKly1
Has this been deprecated? If so, how can we remove recipients from contact lists if opt-out is a global concept? I solved this locally by creating a remove-recipient.js class in the xml-api folder. https://share.polymail.io/v1/z/b/NWIyZDg1Y2E5NTJh/lzh1f32gbMT7Ict5TlNrUJGTpVgbwueZDJZOsagpuofhbcvOTmRzASo_Ao655a1goqriychAmP1jsoH3LlRgMq2yN1aoHwYyrzoPnflSd0MJvnc59W3-A0oe8qZWqfF2vUp62sI1qP2KIbBjAojU2B4HsalPmgP3F4yRtOyZBdDsrwai0JAwSX7f0R6OiQTkE_TU4Z7-vCxqKehPBbBqKly1

GITHUB.COM https://share.polymail.io/v1/z/b/NWIyZDg1Y2E5NTJh/lzh1f32gbMT7Ict5TlNrUJGTpVgbwueZDJZOsagpuofhbcvOTmRzASo_Ao655a1goqriychAmP1jsoH3LlRgMq2yN1aoHwYyrzoPnflSd0MJvnc59W3-A0oe8qZWqfF2vUp62sI1qP2KIbBjAojU2B4HsalPmgP3F4yRtOyZBdDsrwai0JAwSX7f0R6OiQTkE_TU4Z7-vCxqKehPBbBqKly1

To recap what I ran into with the approach you suggested, if I use addRecipient directly to add the contact to a contact list, it fails because of issue #18 above. Once I implemented the fix described in the bug report, it became clear that this is an "add-only" feature; any contact lists included would be added, but the system will not remove lists that are not included. Therefore, I had to implement a Node version of RemoveRecipient (described in issue #19 above). Once this was in, I could handle things appropriately by programmatically removing undesired contact lists and adding newly selected ones.

I would love to be able to commit these fixes to the codebase and get a new version of the API released to npm so we don't have to maintain a modified version of the Engage API. Is this something you'd be able to look into? I have branches ready to commit, but I don't have permissions to do so.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jun 27 2018
  • Delivered
How will this idea be used?

To improve the addRecipient API call

What is your industry? Travel & Transportation
What is the idea priority? High
DeveloperWorks ID
RTC ID
Link to original RFE
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    09 Jan 12:18

    Hello, when an item is 'delivered' does that mean the fix has been deployed?

  • Admin
    Zack Bazemore commented
    24 Jan 01:31

    Hi Kristin,

    Yes when an item is marked as Delivered by those of us on WCA's Product Management team, it means the fix or enhancement has been deployed into production.  In this instance, it's a little different as the original requests were for issues in our XML API Node.js library, and not for the WCA product itself.

    The original description makes mention of issue #18 & #19. The updates that prompted this Idea to be marked as Delievered can be viewed here:

    https://github.com/Silverpop/node-engage/issues/18

    https://github.com/Silverpop/node-engage/issues/19

    Thanks,

    Zack Bazemore