Defining System Settings for Template-Based Correspondence

Enter the characters to be used to demark terms within a template. Choose characters that will not appear in your templates except as term markers. The default characters are double curly brackets: {{ marks the start of a term, and }} marks the end of the term.

Select a system-level setting to determine whether correspondence that is based on external files (RTF or text files) is stored and delivered in its native format or as a noneditable PDF file. Delivering files as PDFs prevents recipients from modifying what you send them. Storing files as PDFs prevents your CRM users from accessing a modifiable version of correspondence that you have sent. Select either Convert to PDF Format or Do Not Convert to PDF.

Select to permit users to set PDF options for individual template packages. The PDF option you select on this page is still used as the default for all new template packages, but users can override it. If you clear this check box, the PDF option you set on this page always applies; the system ignores any package-level PDF options.

Enter the maximum size in kilobytes for external template files that are uploaded to template definitions. This limit does not apply to files that end users upload when adding attachments to correspondence or personalizing correspondence.

Enter the maximum number of template packages that can be included in a single correspondence request.

If you select the Allow Preview check box, enter the number of recipients to be included in the preview-mode template merge. Because document merging is processing-intensive, previewing correspondence for a large number of recipients (such as you might have in PeopleSoft Marketing) is not efficient. Limiting the number of recipients for whom you generate a preview enables you to give users preview capabilities that do not require a full merge process.

Most of the components from which you request correspondence identify only one or two recipients. For these components, a setting of 2 or greater ensures that the system generates previews for all recipients. However, requests that originate in PeopleSoft Marketing can have many more than two recipients. Marketing-related correspondence is therefore the only type of correspondence that it is necessary to limit. Increasing the limit can result in substantial delays for the preview process.

These check boxes work together to control personalization options:

• If both check boxes are selected, users can access all personalization options on the Correspondence Request - Personalize Templates page and the Correspondence Request - Correspondence Summary page. They can drill into documents, download and replace external files, and modify internal text templates or the documents based on them.

• If Show Download Button is selected, but Allow Agent to Modify is cleared, users have access to limited options. They can drill into external and internal text files, and they can download external files. They cannot, however, modify internal text files or replace external files.

• If Show Download Button is cleared, then the Allow Agent to Modify setting is irrelevant. In this situation, users cannot drill into or modify either internal or external documents. Because the Correspondence Request - Personalize Templates page is not operational without these capabilities, this configuration also hides the Personalize Templatesbutton on the Correspondence Request page. The Correspondence Request - Correspondence Summary page remains available as long as the Allow Preview check box is selected.

Select to enable the Previewbutton on the Correspondence Request page. Clicking this button initiates the merge process without sending the merged documents, thus enabling the user to examine the correspondence in its final form before sending it.

The Show Download Button and Allow Agent to Modify check boxes control the user's options on the Correspondence Request - Correspondence Summary page.

Select to enable the Edit Recipients link on the Correspondence Request page. Users click this link to access a recipient list that the originating component creates and to indicate which of the recipients to include in the correspondence. Users cannot add new recipients from the list; they can only select which of the already listed recipients to include.

The setting on this page is a default; the PeopleCode that transfers a user from a transaction to the correspondence request can override this default. For example, when accessing the correspondence request from the List page in PeopleSoft Marketing, the system hides the Edit Recipients link regardless of the system default.

Select to enable synchronous processing of correspondence requests. When this check box is selected, a transaction from which a user submits a correspondence request remains in a suspended state until the correspondence is generated. Once the request is fully processed, a page having the links to access all of the generated documents will be presented.

When this check box is cleared, users can continue to work after submitting a correspondence request. To see the links to the generated documents, users must manually refresh the page where those links appear.

Select this option to delete the intermediate files that are produced either on the application server or on the process scheduler server during the document generation process. Intermediate files include XML files that contain extracted data and FO (formatting object) files that contain the formatting instructions for the final document.

Select this option to enable logging for manual notifications and correspondence requests. When selected, the system logs debug messages for these two types of notifications in the RBC_LOG table. If you clear this option, debug messages are not logged and the View Log link becomes unavailable on the Correspondence Request page.

See Correspondence Request - Correspondence Summary Page, Correspondence Request - Correspondence Request Details Page.

Select one of the following options to control when the system sends notifications related to the merge and delivery processes: Always, Never, On Failure Only, or On Success Only. The same options are available for merge notifications and for delivery notifications.

The merge process runs when a user requests a preview or submits a request. The delivery process runs only after a user submits the correspondence request. The notifications for the merge and delivery processes let the user know the process outcome. For previews, the notification also alerts the user that the preview (which can take a while to create) is ready for viewing.

Choose how users receive merge notifications and delivery status notifications: Email, Worklist, or Email and Worklist. Notifications that are sent to the worklist have a worklist transaction type of Correspondence.

Email notifications are sent to the primary email address of the initiator of that correspondence request. The email contains the correspondence request description, creation date, request ID, recipients, outcome, and if applicable, the reason for failure.

Select the URL that controls the file location for external template files (RTF and text files) that are uploaded as part of a template definition.

Select the URL that controls the file location for template files that are personalized for a specific correspondence request. Users upload these files by clicking the Replace button on the Correspondence Request - Personalize Template page.

Select the URL that controls the file location for recipient-specific XML files that the data extraction process creates. Separating these files from other correspondence files makes it easier for an administrator to periodically purge the files if the system is not configured to automatically delete the intermediate files.

Select the URL that controls the file location for final merged (and perhaps personalized) correspondence that is delivered to recipients.

Select the URL that controls the file location for static attachments that are included in correspondence packages.

Enter the minimum interval for refreshing the preview page of the correspondence. Users can click the Refresh button on that page more frequently, but the refresh command will not be executed unless the specified interval has passed since the last refresh. This setting helps you avoid performance degradation when users click the Refresh button continuously.

Enter the path to the application server temporary directory to be used for parsing terms in .txt template files when they are uploaded. The directory you enter is used only if a temporary directory is not already defined for the application server.

Be sure to format the path according to the operating system on your application servers. For example, you might enter /tmp if you use UNIX, or c:\temp if you use Windows.

Enter the default sender email address for correspondence requests sent by email. This default is used only if the person who created the correspondence request does not have user-level default From addresses defined on the Agent Setup page.

This default is used only on the Correspondence Request page, not on the Send Notification page.

Use these fields to identify the Java programs that perform the indicated subprocesses within the document generation process. The system is preconfigured to use BI Publisher for document generation, and the appropriate values appear by default in this field. Do not change the delivered values unless you are using a different document generation package.

Leave these fields blank if you are using BI Publisher for document generation. If you are using a different document generation package, use these fields to enter any parameters that need to be optionally passed to your Java programs. Enter the parameters in a format that will be understood by your Java programs.

Enter the number of minutes after which the system will attempt to resend an email that the PeopleSoft system was not able to send, and specify how many times the system will attempt to resend.

These fields are for email that was not sent due to, for example, a problem with your SMTP sever. These fields do not apply to emails that bounce because they are undeliverable on the recipient's end.

Select the worklist where the system sends notifications of undeliverable emails. The notification is sent only if the email is still undeliverable after the maximum number of retries.

Select the URL that indicates where you want the system to store attachments in undeliverable email.