This article includes overview, sample use cases, creation workflow, and differences between Interactive Communication and letter.
Interactive Communications centralizes and manages the creation, assembly, and delivery of secure, personalized, and interactive correspondences such as business correspondence, documents, statements, benefit notices, marketing mails, bills, and welcome kits.
Following are the key capabilities of Interactive Communications:
To create an Interactive Communication, have the building blocks for Interactive Communication ready and then complete the following steps:
Choose to create an Interactive Communication.
Using the drag-and-drop interface, add document fragments, images, components to print and web channel of the Interactive Communication as required.
Configure the properties for the components inserted, such as the following:
Preview print and web channels and, if required, edit the Interactive Communication.
The agent uses the Agent UI to prepare the Interactive Communication for sending it to the recipient/post process.
Following are the building blocks required for creating an Interactive Communication:
Interactive Communication is the default and recommended approach to create customer communications. To continue using the letters creating in AEM 6.3 Forms and AEM 6.2 Forms, you need to install a compatibility package. Following is a comparison between capabilities of Interactive Communication and letter.
|Output||Print and Web|
|Schema||Form data model||Data dictionary|
|Localization||Not supported in form data model||Supported in data dictionary|
||No UI for creation of conditional expression|
|Authoring||Drag-and-drop interface for constructing print and web channel||No drag-and-drop mechanism|
|Charts||Charts supported in print as well as web channel||Not supported|
|Themes||Uses themes to style web channel||Does not support themes|
|Versioning||Not Supported||Supported||Batch processing||Supported||Supported|
|Agent signature||Not supported||Supported|
|Remote functions||Not supported||Supported|