Originally written by John Hardwick, last updated Jan 30, 2026, on the Swan Retail knowledge base (FRS).
A service template is a pre-defined rich text (.rtf) data file which is used as a merge template to produce a document which can be forwarded to a customer, or service provider. The document may contain keywords used to merge in event specific data.
Documents may be created in any third-party application capable of saving the output to a rich text format.
Menu Location: System Admin > Customer Service > Set Up Service Templates
-
It is possible to filter the events listed by selecting an event type from the Group Filter at the top of the page.
-
Click the NEW button or New on the side panel to generate a new record.
-
Click the CLOSE button, or Back option on the side panel to leave the page (or select another option from the menu)
-
Click the icon to amend an existing record.
-
Once in amend / insert more, click the to save changes or to abort the action.
|
Item |
Description |
|
Event |
The operator must choose an event from the list of provided. Blank options are not allowed. See Set Up Service Events (1206 onwards) for details. |
|
Type |
Dependant upon the event type selected, further clarification is required. Where required, the pick list will offer a series of choices. See Set Up Service Events (1206 onwards) for details. |
|
Subject |
Dependant upon the event type selected, further clarification is required. Where required, the pick list will offer a series of choices. See Set Up Service Events (1206 onwards) for details. |
|
Template Description |
Specify the name to be presented to the operator when processing the event this template is linked to. |
|
Template Filename |
Specify the filename as saved in the templates document folder. |
|
Active |
Tick to make this template active. |
Template Merge Tags
The following merge tags can be used within a template and will be replaced with the corresponding data element when used within service.
-
Tags are NOT case-sensitive (i.e. <%=service.id%> is the same as <%=Service.ID%>).
-
The equals symbol is optional (i.e. <%=Service.Note%> is the same as <%Service.Note%>).
-
It is possible to include spaces after the first % symbol and the optional = symbol and before the second % symbol, for clarity. That is, <% = service.Note %> is the same as <%=service.Note%>.
Tags are presented in groups relevant to the type of tag.
System
General system merge tags.
|
Tag |
Description |
|
<%=today%> |
Current date |
|
<%=date%> |
|
|
<%=datelong%> |
Long date format |
|
<%=dateshort%> |
Short date format |
|
<%=time%> |
Time |
Customer Details
Customer specific merge tags.
|
Tag |
Description |
|
<%=customer.fullname%> |
Full Name |
|
<%=customer.accountnumber%> |
Account Number |
|
<%=customer.title%> |
Title |
|
<%=customer.initials%> |
Initials |
|
<%=customer.forename%> |
Forename |
|
<%=customer.surname%> |
Surname |
|
<%=customer.homephonenumber%> |
Home Phone Number |
|
<%=customer.workphonenumber%> |
Work Phone Number |
|
<%=customer.mobilephonenumber%> |
Mobile Phone Number |
|
<%=customer.email%> |
|
|
<%=customer.fulladdress%> |
Full customer address |
|
<%=customer.address.housenumber%> |
House Number |
|
<%=customer.address.housename%> |
House Name |
|
<%=customer.address.flatnumber%> |
Flat Number |
|
<%=customer.address.street%> |
Street |
|
<%=customer.address.posttown%> |
Post Town |
|
<%=customer.address.suburb%> |
Suburb |
|
<%=customer.address.county%> |
County |
|
<%=customer.address.state%> |
State |
|
<%=customer.address.postcode%> |
Post Code |
|
<%=customer.address.addressline1%> |
Address Line 1 |
|
<%=customer.address.addressline2%> |
Address Line 2 |
|
<%=customer.address.addressline3%> |
Address Line 3 |
|
<%=customer.address.addressline4%> |
Address Line 4 |
|
<%=customer.address.addressline5%> |
Address Line 5 |
|
<%=customer.fulldeladdress%> |
Full delivery customer address |
|
<%=customer.deladdress.housenumber%> |
House Number |
|
<%=customer.deladdress.housename%> |
House Name |
|
<%=customer.deladdress.flatnumber%> |
Flat Number |
|
<%=customer.deladdress.street%> |
Street |
|
<%=customer.deladdress.posttown%> |
Post Town |
|
<%=customer.deladdress.suburb%> |
Suburb |
|
<%=customer.deladdress.county%> |
County |
|
<%=customer.deladdress.state%> |
State |
|
<%=customer.deladdress.postcode%> |
Post Code |
|
<%=customer.deladdress.addressline1%> |
Address Line 1 |
|
<%=customer.deladdress.addressline2%> |
Address Line 2 |
|
<%=customer.deladdress.addressline3%> |
Address Line 3 |
|
<%=customer.deladdress.addressline4%> |
Address Line 4 |
|
<%=customer.deliveryaddress.addressline5%> |
Address Line 5 |
Operator Details
Operator / user tags.
|
Tag |
Description |
|
<%=user.fullname%> |
Full Name |
|
<%=user.loginid%> |
Login ID |
|
<%=user.email%> |
|
|
<%=user.username%> |
Username |
|
<%=user.serviceoperative%> |
Service Operative |
Product Details
Product specific merge tags.
|
Tag |
Description |
|
<%=product.range%> |
Range |
|
<%=product.description%> |
Description |
|
<%=product.modelnumber%> |
Model Number |
|
<%=product.sku%> |
SKU |
Supplier Details
Supplier specific merge tags.
|
Tag |
Description |
|
<%= supplier.name%> |
Name |
|
<%=supplier.fulladdress%> |
Supplier Full Address |
|
<%=supplier.address.fulladdress%> |
Supplier Address Full Address |
|
<%= supplier.address.housenumber%> |
House Number: |
|
<%= supplier.address.housename%> |
House Name |
|
<%= supplier.address.flatnumber%> |
Flat Number |
|
<%= supplier.address.street%> |
Street |
|
<%= supplier.address.posttown%> |
Post Town |
|
<%= supplier.address.suburb%> |
Suburb |
|
<%= supplier.address.county%> |
County |
|
<%= supplier.address.state%> |
State |
|
<%= supplier.address.postcode%> |
Post Code |
|
<%= supplier.address.addressline1%> |
Address Line 1 |
|
<%=supplier.address.addressline2%> |
Address Line 2 |
|
<%= supplier.address.addressline3%> |
Address Line 3 |
|
<%= supplier.address.addressline4%> |
Address Line 4 |
|
<%= supplier.address.addressline5%> |
Address Line 5 |
Stock Details
Stock specific merge tags.
|
Tag |
Description |
|
<%=stock.detailnumber%> |
Detail number |
Purchase Order Details
Purchase order detail merge tags.
|
Tag |
Description |
|
<%=purchaseorder.number%> |
Number |
|
<%=purchaseorder.ackref%> |
Ack Ref: |
|
<%=purchaseorder.ackdate%> |
Ack Date: |
Sales Order Details
Sales order specific merge tags.
|
Tag |
Description |
|
<%=salesorder.number%> |
Number |
|
<%=salesorder.padnumber%> |
Pad Number |
Service Header
Service header merge tags.
|
Tag |
Description |
|
<%=service.number%> |
Service reference |
|
<%=service.location%> |
Service location (description) |
|
<%=service.date%> |
Creation date |
|
<%=service.linkedto%> |
Linked to service |
|
<%=service.owner%> |
Service owner (name) |
|
<%=service.reviewdate%> |
Review date |
|
<%=service.status%> |
Status (description) |
|
<%=service.calltype%> |
Call type (description) |
|
<%=service.firstevent%> |
New service event narrative |
Event Details
Event specific merge tags.
|
Tag |
Description |
|
<%=event.number%> |
Event sequence number |
|
<%=event.type%> |
Type of event |
|
<%=event.subject%> |
Event subject |
|
<%=event.date%> |
Event creation date |
|
<%=event.notes%> |
Event narrative |
|
<%=event.review%> |
Event review date |
|
<%=event.owner%> |
Event owner |
|
<%=event.subjectdesc%> |
Linked to product description |
|
<%=event.subjectSKU%> |
Linked to SKU |
|
<%=event.deldate%> |
Delivery / collection scheduled date |
|
<%=event.addeddesc%> |
Item addition description |
|
<%=event.addedSKU%> |
Item addition SKU |
|
<%=event.deldate%> |
Delivery / collection scheduled date |
|
<%=event.adjustmentvalue%> |
‘selling’ price addition / reduction to order |
|
<%=event.invoiceref%> |
Invoice reference |
|
<%=event.supplier%> |
Supplier name |
|
<%=event.invvale%> |
Value |
|
<%=event.origdeldt%> |
Specified delivery date |
|
<%=event.invoiceno%> |
Invoice number |
|
<%=event.paid%> |
Paid indicator |
|
<%=event.cancelled%> |
Cancelled |
|
<%=event.technician%> |
Technician (name) |
|
<%=event.vistidate%> |
Visit date |
|
<%=event.partsin%> |
Parts in |
|
<%=event.collectcash%> |
Collect cash |
|
<%=event.estarrival%> |
Estimated arrival time |
Repeat Iterative
This tag instructs the system to repeat the tags within the start / end repeat tags. It is designed to allow the merge document to show multiple subject lines / stock items, for example.
|
Tag |
Description |
|
<%=Repeat%> |
Used to instruct SwanFRS to repeat the following tags. Example of use <%Repeat%><%stock.detailnumber%><%EndRepeat%> this text would generate a list of all stock details linked to the alert. (one per line) |
|
<%=EndRepeat%> |
Stop repeating |
Merge Example
The following HTML … (merge tags are highlighted in red for illustrative purposes only)
<p><span class="text-big" style="color:hsl(240, 75%, 60%);"><strong>Sales Order Confirmation</strong></span></p> |
|---|
… Produces the following email
Completed documents should be saved in rtf format on the FRS server in the CSFiles\Templates folder.
E.g. C:\…\inetpub\wwwroot\FRStest\CSFiles\Templates
For Swan hosted systems, the folder is within the Syncthing® share folder
This path may vary dependent upon whether you are linking to the live or test system. Please consult with your implementation consultant for clarification as to the exact path used on your system.
Files from the Confluence page
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article