Currently in AWD 20.3 the max length of a manually created variable is limited to 75 characters.  Client has need where they enter up to a 750 character variable text that they need to be included in letter. Within Communications - Data Source Setup, created variable with field type of "textarea" but length cannot be set beyond 75 characters.  Has this been addressed in later release? On horizon?  If not then this is desired so larger text variables could be passed into Word during letter generation. ... View more

The Current date format is YYYY/MM/DD and needs to be changed to Month/DD/YYYY. ... View more

When generating letters using Chorus Communications, there are a number of options that are only available from the Packaging screen.  This means this functionality can only be accessed in a Presentation Flow and it must be manually updated by a user.  For instance, changing the output from Print to Email, or selecting enclosures.   We would like all of this functionality available by other means to support automation.  For instance, via  webservice calls or via a custom cog in Design.  The goal is to be able to access these additional functionality from an Automation Service so we can have a wider range of letters that do not require human interaction. ... View more

Currently conditional content relies on variable or LOB data to select content.  Our clients need an option to let the user select content from a list presented in Word that is driven by conditional content rules. Alternately providing a simple list of content to choose from fulfills the need. ... View more

Chorus is unable to store email addresses of more than 75 characters.   Email standards allow for up to 320 characters in email addresses and we cannot control the addresses used by our clients/CMOs so we need Chorus to store email addresses of the full 320 characters. This is currently leading to email uploads failing silently and requires urgent remediation.   ... View more

A significant number of documents sent for quality review are failed for due to issues with values configured in the Packaging Details task.  As of now we are unaware of any way to edit any of those values after the document is released to quality review.  This causes the user to rewrite the entire document.  We would like a way to edit those values when making corrections to an existing document. ... View more

It is my understanding that the communications print server prints one document at a time.  If for some reason the current print job is corrupted or slow performing a bottleneck is created for other released documents. We'd like to see an option to print up to x (configurable) documents concurrently. ... View more

The Chorus 'ROS' functionality currently requires that all Chorus users are given access to write and/or delete files from the template directory. PLRE considers this at minimum an operational risk, as there is no way to prevent users from deleting/altering the templates and/or adding further templates which are then available to other users. We would like the Chorus ROS process to remove the requirement for update access to the template folder so that all non-admin users can have only read access. ... View more