When configuring an automated document in the communications cog the designer is forced to use drop-downs to define the document. The designer can not use a variable.
The automated configuration requires a task for each automated letter. BPO has a thousand or more automated letters and forcing this causes the service layer to become extremely complex and difficult to support.
When new letters are added for Automation use we will no longer have to update the service with a new Communication Cog. We would want to require the use of a variable to pass the document name. The service could require some modifications and the current Communication Cog may the ability to be “Refreshed” to pull in any new Data Sources that may be added for use within the letter.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.