You're viewing help content for version:
- 6.4
- Older Versions
This tutorial is a step in the Create your first Interactive Communication series. It is recommended to follow the series in chronological sequence to understand, perform, and demonstrate the complete tutorial use case. |
Document fragments are reusable components of a correspondence that are used to compose an Interactive Communication. The document fragments are of the following types:
- Text - A text asset is a piece of content that consists of one or more paragraphs of text. A paragraph can be static or dynamic.
- List - List is a group of document fragments, including text, lists, conditions, and images.
- Condition - Conditions enable you to define what content gets included in the Interactive Communication based on the data received from the Form Data Model.
This tutorial walks you through the steps to create multiple text document fragments based on the anatomy provided in Plan the Interactive Communication section. At the end of this tutorial, you will be able to:
- Create document fragments
- Create variables
- Create and apply rules

The following is the list of document fragments that are created in this tutorial:
Each document fragment includes fields with static text, data received from form data model, and data entered using the Agent UI. All these fields have been depicted in the Plan the Interactive Communication section.
While creating document fragments in this tutorial, variables are created for fields that receive data using the Agent UI.
Use FDM_Create_First_IC, as described in the Create form data model section, as the form data model to create document fragments in this tutorial.
Field | Data Source |
Invoice No | Agent UI |
Bill Period | Agent UI |
Bill Date | Agent UI |
Your Plan | Form data model |
Execute the following steps to create variables for fields with Agent UI as the data source, create static text, and use form data model elements in the document fragment:
Field | Data Source |
Customer name | Form data model |
Address | Form data model |
Place of Supply | Agent UI |
State Code | Agent UI |
Mobile Number | Form data model |
Alternate Contact Number | Form data model |
Relationship Number | Form data model |
Number of Connections | Agent UI |
Execute the following steps to create variables for fields with Agent UI as the data source, create static text, and use form data model elements in the document fragment:
Field | Data Source |
Previous Balance | Agent UI |
Payments | Agent UI |
Adjustments | Agent UI |
Charges current bill period | Form data model |
Amount Due | Agent UI |
Due Date | Agent UI |
Execute the following steps to create variables for fields with Agent UI as the data source, create static text, and use form data model elements in the document fragment:
Field | Data Source |
Call Charges | Form data model |
Conference Call Charges | Form data model |
SMS Charges | Form data model |
Mobile Internet Charges | Form data model |
National Roaming Charges | Form data model |
International Roaming Charges | Form data model |
Value Added Services Charges | Form data model |
Total Charges | Form data model |
TOTAL PAYABLE | Form data model |
Execute the following steps to create static text and use form data model elements in the document fragment:
-
On the Create Rule pop-up window:
- Select Data Models and Variables and then bills > callcharges.
- Select is less than as the operator.
- Select Number and enter the value as 60.
Based on this condition, Value Added Services Charges row is displayed only if the value for the Call Charges field is less than 60.