Property checklist information can be used in letters/emails/tasks (via creation of merge codes)

Property checklist information can be used in letters/emails/tasks (via creation of merge codes)

This guide has been reviewed against our global customer base and classed as relevant to all regions

Available from version 12.223

Property checklist functionality is a configurable option for Enterprise customers
For more information, click here: Property checklists - configuration option

To request for property checklists to be set-up on your system and/or to request merge codes to be created for your property checklists (as outlined below): click here to contact Reapit Support

When using property checklist functionality, information from the checklists can be included in letters, emails or tasks - in order to take information from checklists, merge codes need to be created and added to the relevant letter/email/task templates

As property checklists are completely customisable, merge codes are not available in the Letter Template Editor, and instead need to be created manually using the format outlined below

If you have access to edit letter/email/task templates, use the guidelines outlined below - if not, an Enterprise client key contact can use the link above to request assistance from Reapit Support
(non-Enterprise clients can request access to setup templates themselves, also using the above link)

1. Obtain variable field name for checklist item

Merge codes can be created for use on a letter, email or task template - the merge code needs to include the Variable name for the required property checklist item

From Setup Property Checklist screen:

  • Locate the check you wish to create a merge code for

  • In Variable column, note the name given to that check
    The text in the Variable column is used in the merge code(s)

Prop checklist example.png

Using this example property checklist (titled: Pre-completion), in order to include any of the information in a letter/email/task template, the relevant Variable name should be noted
For example, to include the name of the Completion consultant in the template, PreCompConsultant should be noted

2. Create merge code

The format shown below can be used to create a merge code for any checklist item, replacing the example text (i.e. PreCompConsultant) with the relevant Variable name for the check (as entered into the Setup Property Checklist screen, outlined in step 1):

  • Letter template
    <Property.GetPropertyCheckListItemDisplay("PreCompConsultant")>

  • Email template
    <%Property.GetPropertyCheckListItemDisplay("PreCompConsultant")%>

  • Task template
    {Property.GetPropertyCheckListItemDisplay("PreCompConsultant")}

With the exception of the variable name shown above (i.e. PreCompConsultant), the brackets, symbols and text used in the merge code need to be copied exactly as shown above for the required template type

3. Add merge code to template

Merge codes need to be added manually to the required template type:

  • For a letter or email template:

    • Add the merge codes to the letter or email template

    • Upload new/amended templates, as usual

  • For a task template:

    • Add merge codes via the Setup Task Templates screen (in the Text field)

    • Set the Applies To field to any type which can access a property

If you need access to setup your own letter, email or task templates, use the link at the top of this guide to contact Reapit Support to request this

Related articles

Need more assistance? No problem! Just log a ticket on the Reapit Service Desk Portal at https://reapitsupport.refined.site/ and a member of our Support Team will be happy to help