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
I have been to two customers that use session attributes that exceed the current limit of 64. One customer used session attribute placed on different user group search templates and wanted to exceed the 65 limit. This usage can easily exceed the current 64 limit. Another customer wanted session attributes for AJAX variables. as well as, normal session attributes (Login ID, account #, etc.). There were many AJAX values and this use easily exceeded the 64 limit.
How will this idea be used?
Used when customers have legitimate needs exceed the 64 limit.
|What is your industry?||Professional Services|
|What is the idea priority?||Low|
|Link to original RFE|
Thanks for submitting this. Other similarly situated are urged to comment and vote!