Copy to case participants (multiple recipients)
| The content of this website is last updated to F2 version 11. cBrain are working hard on supplying you with the newest documentation of F2. |
A letter template can be used for generating multiple identical letters to different recipients simultaneously. The process differs slightly from letter templates for a single recipient. This is partially due to differences in merge codes and to the structure of the process.
Use this function when sending the same information to a large number of participants. The following sections describe this process of generating letters.
Generating individual letters for multiple recipients
First add the relevant participants to the case in question. The participants and their information must exist in F2’s participant register. The participants are added by entering their names in the “Case participants” metadata field.
The figure below shows the case window with two participants added to “Case participants”.
Choose a template containing merge codes for this particular type of merging.
The merge code must begin with “mergeparty” when merging data from multiple participants with a template.
The table below contains some examples.
| Merge field | Description |
|---|---|
mergeparty_name |
Recipient’s name |
mergeparty_address1 |
First line of recipient’s address |
mergeparty_postalcode |
Recipient’s postcode |
mergeparty_city |
Recipient’s city |
dossier_sendername |
Case manager’s name |
case_f2casenumber |
Case number |
The corresponding merge codes are created by adding “$” before and after the merge fields' names.
The example from the previous section, Example of merging data for a letter, is used here to illustrate a letter template for sending standardised information to multiple recipients. In this example, the template uses the string “mergeparty” in the merge codes to ensure that the letter will be sent to any participant identified in the “Case participants” metadata field.
To generate letters for multiple recipients, choose a record from which to retrieve the letter template. The record must be attached to the case with the participants.
Click on New document from template as shown below.
No final letters are generated immediately upon attaching the letter template. If the document is previewed, it will still contain merge codes (mergeparty).
Save the record with the template. Click on Copy record and then on Merge to case participants to start generating the letters to multiple recipients as displayed in the figure below.
Click on Merge to case participants to open a dialogue in which it is possible to select the participants for merging.
A record is generated for each selected participant.
Options in the “Merge to case parties” dialogue
| Function | Description | ||
|---|---|---|---|
Set participant as recipient |
Tick this box to add the selected participants as recipients on the newly generated records. |
||
Send to recipient |
Tick this box to automatically send the records to the selected participants when clicking OK.
|
||
Set participant as involved participant |
Tick this box to add the selected participants as involved participants on the record. |
||
Participant type |
From this drop-down menu, it is possible to assign participant types to the participants on the new record. 
Figure 6. Select participant type
|
||
Remove original record from the case |
Tick this box to remove the original record from the attached case. |
||
Open case |
Tick this box to automatically open the case window after clicking OK. |
| The fields shown in the dialogue “Merge to case participants” depend on the installation’s configurations and add-on modules. F2 is configured in cooperation with cBrain. |
Click on OK to generate the emails and add them to the case. Each record contains a copy of the attached document with all merge codes replaced by the corresponding information. If the records have not already been sent via the “Merge to case parties” dialogue, they can now be sent to the different recipients.
Participant types
Participants can be assigned specific participant types. Each type has a number of corresponding merge fields, which makes it possible to refer directly to the wanted participant type when creating templates.
Participant types are assigned in the case window. A participant who has been assigned a type is automatically merged with the corresponding participant type merge codes.
