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.
Estimated time to implement the story
When all of the assets are in place, this task consists
only of mapping the assets into the letter. This task should require
less than half a day.
Common questions to ask to clarify requirements
Is the data XML in sync with the data model used
in the letters?
Will the letter be system-generated, or will a business user
such as a Claims Adjustor create the letter? Binding to User should
only be done is a business user will create the letter.
Which parts of the letter should be prefilled?
Which
paragraphs in the letter can be edited by a business user and which
are optional?
Requirements addressed
Combine assets into a letter and finally generate a piece
of correspondence.
Implementation overview
The Application Specialist uses the Letter Template Editor
in the Manage Assets UI 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 postprocess for the letter.
Map content to target areas in the layout.
Map fields and variables in the selected content to data
dictionary elements, literals, etc.
The Application Specialist creates letter templates.
Best practices/tips and tricks
Use a consistent naming convention to avoid duplication.
Use appropriate data dictionary binding to enable mapping
of assets from that data dictionary.
Fields should be bound to User only if the letter is generated
by a business user (such as a claims adjustor). For system-generated
letters, fields should not be bound to User.
For mandatory and fixed content, mark the content as preselected
and mandatory.
Content should be marked as editable only if it requires
the business user (such as a Claims Adjustor) to modify it.
The following rules apply when using the Letter Template
Editor to make changes to a letter template:
Addition of variable:
Not
applicable
Removal of variable:
Not applicable
Updating of properties:
Allowed
Change of data dictionary:
Allowed until no item that
uses the data dictionary is associated with it.
Addition of layout fields:
Not applicable
Removal of layout fields:
Not applicable
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, and “N/A” indicates
that it is not applicable. “TLC” stands for text, list, and condition.
“IC” stands for image and condition.
