Access Communications Packaging Details from Automation Services in Chorus

[gmunden]

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.

[gmunden]

One thing I forgot to mention is that we will need the ability to rename enclosures.  Also, assign existing sources as an enclosure as well as a URL for an enclosure.  Most of our client forms are at publicly accessible URLs, so if we can dynamically pull these in as enclosures, that would be a big time savings.

[Karen_Hunter]

Added to Communications backlog - Design component CMM-I-16.

[gmunden]

A couple other thoughts to add to this. 

1. If the packaging details screen is presented to a user, it would be helpful to have programmatic access to what selections were made by the user.  

2.Also, the ability to automatically set the packaging details would be particularly helpful for the secure message center integration.