-
Make Chrome Plugin compatible with the new WCA interface
According to WCA support, the Chrome WCH plugin is not compatible with the new WCA interface, thus breaking the WCA/WCH integration. Support suggested raising the issue here. This needs to be fixed as we have clients currently using this integration.0 Will not implement
-
Website User Permission
Allow Acoustic Content Administrator give or not website user permission. This is interesting for customers who have many websites where each user is responsible for one specific website.0 Future consideration
-
Bulk Asset Download
Let users from Acoustic Content UI select assets to be downloaded on a compressed file. -
Asset and Content Reports
Create reports to help identify where assets and content are being used: - How many assets were imported by users - How many assets are not being used - Assets and contents per channel (Email, Push, Website, Landing Page, etc) - How many assets an... -
Avoid Akamai configuration activation delay during tenant onboarding
Problem The tenant delivery APIs require an activated Akamai configuration that map the specific tenant URLs to the right service endpoints / folders on Akamai NetStorage. When a tenant is freshly on-boarded, this configuration is not yet availabl...0 Will not implement
-
wchtools push -a --set-category CAT1,CAT2
Allow uploaded assets to have a specified set of categories. Probably with libraries this need might fade, but the general idea is to allow putting assets in "drawers".1 Future consideration
-
Have a URL which directs to editing of the content object
It would be great to have a URL which would get us to the editing of a specific content object. This would allow to use a headless front where editing of individual objects could be handled by opening the editing view of Content Hub.0
-
Default site resource path for headless sites to be configurable in tenant settings
When not using the default managed website mechanism, the default site resource path for headless sites should be configurable in tenant settings to avoid the need for an explicit resource path in the site URL.1 Future consideration
-
User limitation - they cannot upload/attach databases of more than XYZ contacts t
To make it possible to put limitations on users where they cannot upload/attach databases of more than XYZ contacts to a mailing0
-
Form Builder connecting WCH & WCA
This is about using Watson Campaign Automation(WCA) web forms inside the WCH At the moment the WCA web forms have following drawbacks1. Preserve last published data2. Very difficult to style or to make it responsive3. Publish the forms to a new pa...0 Future consideration