Acoustic Ideas

Submit new product ideas for Campaign, Interact, Marketing Operations, Marketing Platform, Campaign Managed Hosted, interact Managed Hosted, Marketing Operations Managed Hosted, Digital Analytics, Experience Analytics, Exchange, Watson Marketing Insights, Content, Web Content Manager and WebSphere Portal solutions. 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 Acoustic experts on the Watson Marketing and Commerce Community

Submit ideas for other Acoustic Products:

Watson Commerce
Watson Supply Chain

More advanced Step attributes

Currently any step attributes can't retrieve complex objects (i.e. arrays/lists). It would be desirable that this could be implemented to be able to build more intelligent events.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jun 12 2019
  • Needs review
How will this idea be used?

We need to work with information coming from datalayers (for example), and some fields in the json structure are given in arrays/lists or hashmaps.


object: {

  item1: [




  item2: {

    "hashkey1": "hashvalue1",

    "hashkey2": "hashvalue2"




But when you design any step attributes you can't retrieve the object (array/list, hashmap) from an event, and all that you get from an array/list is the last item of the array.

The idea is that Tealeaf can support step attributes that return array/hashmap objects that could be run afterwards in an event, giving more power to the decisions over the data you manage.

What is your industry? Telecommunications
What is the idea priority? High
DeveloperWorks ID
Link to original RFE
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    August 05, 2019 14:08

    This is also crucial for our organization. The fact that we cannot scrape everything from our data layer greatly limits our ability to use Tealeaf to its full potential. Let's say our data layer looks like this: 

    "product variation ": [
    "name": "product X - variation 1",
    "availability": "4"


    "name": "product X - variation 2",

    "availability": "0"



    To define a step attribute that scrapes the availability of each variation of product X, we would then need to define two step attributes, since there is no way to work with wildcards the pattern path:

    productvariation[0].availability and productvariation[1].availability

    Since some products can have up to 20 variations and our data layer consists of more than 20 elements per product variation, defining these step attributes for each element in our data layer is cumbersome.