Correspondence form
|
|
Complete the Corr tab to define the text, formatting, property values, and, included correspondence fragments, and appearance of the correspondence.
If this correspondence rule is to be used with the Work-.AttachandHold flow action and a Word template rule, enter only plain text, directives, and JSP tags in the text area. Do not include HTML tags, such as <P> or <H3>. The Word template file provides the formatting.
When the Correspondence Type key part of the rule is Email, all correspondence produced for outgoing email includes HTML formatting, even if no HTML elements appear within in the source. The recipient's mail client must have the capability to accept and display HTML-formatted email.
When the Correspondence Type key part of the rule is PhoneText, the correspondence produced for outgoing email includes no HTML formatting. The destination may be a digital cell phone that supports Short Message Services (text messaging) or an email client program.
In source mode, you can use references based on linked properties. For example, in a work object, the property Work-.pxCreateOperator is a linked property identifying a key to a unique instance of the Data-Admin-Operator-ID class. To include the full name of the create operator, enter the reference as:
<pega:reference name=".pxCreateOperator.pyUserName"></pega:reference>
Note the leading . before the linked property name.
As a best practice to ensure quality and security, minimize the use of source mode in correspondence rules you create in application RuleSets. While such rules are necessary for specific features, use of generated correspondence is preferable when possible. If your application contains correspondence rules, use the Guardrails landing page to assess guardrail compliance, and use the Rule Security Analyzer to check for security vulnerabilities.
Field |
Description |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(no label) |
Enter rich text for the correspondence. In Design mode, a wide variety of tools are available in the toolbar including fonts, font sizes, colors, lists formatting, graphic elements and alignments. Certain controls are available only in Design mode, and only when text is selected. Toolbar
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Included Section Preview | Select Show the preview of included section check box and any sections included in the paragraph display as they will appear at run time. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Designated Printer |
Optional. For print only. To print correspondence from this rule on a COS printer identified in your system, enter the Printer Name value of a COS Printer data instance. Before you attempt to print correspondence, install COS. See About the Correspondence Output Server. If the correspondence is to be printed on a printer not known at this time, leave this field blank. The operator can select a printer, or your application can compute a destination printer. See More about COS Printer data instances. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Special Print Activity |
Optional. For print only. By default, the system uses the standard activity named Data-Corr-Letter.Send to send correspondence items to a COS printer. To use another activity, create an activity with Data-Corr-Letter as the Applies To key part. Enter the Activity Name key part here. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Display Width |
Optional. Enter a display width as a percentage value between 10 and 100. If your application presents the correspondence item to a user for editing, the system sets the initial correspondence display window to this percentage of the user's full monitor width (in pixels). The user can adjust the window size. Select a percentage that suits the correspondence. The default is 60 percent. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Display Height |
Optional. Enter a display height as a percent value between 10 and 100. If your application presents the correspondence item to a user for editing, the system sets the initial correspondence display window to this percent of the user's full monitor height in pixels. Select a percentage that suits the correspondence. The default is 80 percent. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
After Create |
Select the initial disposition of correspondence items created by this rule:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
User Edit |
Indicate what degree of editing is available at runtime to an application user for correspondence items produced by this rule:
Select |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Generate For |
Typically, the system sets this field to Use of JSP tags offers superior performance and other advantages over directives. Although both directives and JSP tags are supported, JSP tags are recommended for new development. If this rule is circumstance-qualified or time-qualified, make this Generate For value match the Generate For value of the base rule. The base rule and the qualified rules must all use JSP tags or all use directives. Do not save the rule form if you have composed HTML that contains both JSP tags and directives. |
For paragraphs on user forms, you can associate a pop-up SmartInfo section with the paragraph. To configure a Smart Info section:
A SmartInfo pop-up window can supply context-specific help to application users. This feature depends on AJAX technology.
The SmartInfo feature supports interactive users as they complete or review a user form. The SmartInfo feature doesn't operate when a paragraph rule is included in a correspondence rule.