|
After all of the individual assets (layout, text, images,
lists, conditions) have been created for a letter, the Application
Specialist can combine them into a letter template, which defines
the appearance and behavior of the letter.
Common questions to ask to clarify requirementsIs the data XML in sync with the data model used
in the letters?
Will the letter be system-generated, or can a business user
such as a Claims Adjustor create the letter?
Which parts of the letter is prefilled?
Which paragraphs in the letter a business user edits, and
which are optional?
Implementation overviewThe Application Specialist uses the Letter Template Editor
in the Manage Assets user interface to create letter templates.
The Letter Template Editor enables you to:
Provide the necessary properties/metadata for the letter
template, such as its name and description.
Select a layout for the template.
Select a fragment/table fragment for the target area
Select a post-process for the letter.
Map content to target areas in the layout.
Map fields and variables in the selected content to data
dictionary elements, literals, and so on.
Team membersThe Application Specialist creates letter templates.
Best practices/tips and tricksUse a consistent naming convention to avoid duplication.
Use appropriate data dictionary binding to enable mapping
of assets from that data dictionary.
Bind fields to User when a business user (such as a claims
adjustor) generates the letter. For system-generated letters, fields
do bind to the User.
For mandatory and fixed content, mark the content as preselected
and required.
Mark content as editable only if it requires the business
user (such as a Claims Adjustor) to modify it.
Data mapping is set on the Data Map tab in the Letter Template
Editor. The following table describes which types of data mapping
are available for various types of fields. “Yes” indicates that
the field type listed in the leftmost column supports that type
of mapping. “No” indicates that it does not. “N/A” indicates that
it is not applicable. “TLC” stands for text, list, and condition.
“IC” stands for image and condition.
| |
Literal
|
Content
|
Data Dictionary
|
Ignore
|
User
|
Field
|
Variable
|
|---|
date
|
Yes
|
No
|
Yes
|
Yes
|
Yes
|
N/A
|
N/A
|
time
|
Yes
|
No
|
Yes
|
Yes
|
Yes
|
N/A
|
N/A
|
datetime
|
Yes
|
No
|
Yes
|
Yes
|
Yes
|
N/A
|
N/A
|
integer
|
Yes
|
No
|
Yes
|
Yes
|
Yes
|
N/A
|
N/A
|
float
|
Yes
|
No
|
Yes
|
Yes
|
Yes
|
N/A
|
N/A
|
richtext
|
Yes
|
TLC
|
Yes
|
Yes
|
Yes
|
N/A
|
N/A
|
plain text
|
Yes
|
TLC
|
Yes
|
Yes
|
Yes
|
N/A
|
N/A
|
image
|
No
|
IC
|
No
|
Yes
|
No
|
N/A
|
N/A
|
signature
|
No
|
No
|
No
|
Yes
|
No
|
N/A
|
N/A
|
|
|
|
