Standard texts are predefined pieces of text that you can insert into SMS messages and email messages with a single click. Instead of writing the same text again and again – for example a payment link, a welcome greeting or a receipt text – you define the text once as a standard text and select it via a lookup dialog when composing a message.
Standard texts can contain text commands (placeholders such as `{CustomerFullName}` or `{TotalAmountForURL}`) that are automatically filled in with data from the current customer, order or invoice at the time the message is sent.
Access to Standard texts requires the appropriate permissions. If you cannot see the menu item, you probably do not have permission for it. Contact support.
Open Financial via the hamburger menu in the top left. Then go to Setup and select Standard texts. You now see a list of all standard texts defined for the selected location.
Standard texts are a cross-cutting feature available from two central places:
In SMS messages: When you edit the text of an SMS message, a button (Standard texts) is shown above the text field. Click the button to open the lookup dialog and select one or more standard texts. The content is inserted directly into the SMS field.
In email messages: When you edit the body of an email, the HTML editor is equipped with a text command button (Insert text command). Click it to open the lookup dialog and select standard texts to be inserted into the email's content.
The mechanism is generic and can in principle be used everywhere in Sapera where text fields support standard texts.
The list view shows a table with two columns: Heading and Content type. Each row represents one standard text.
At the top of the page you find a location selector. Sapera is organized in a hierarchical location structure (organizational units). Standard texts are associated with a specific location but are inherited downwards in the hierarchy. That is, a standard text defined at chain level is visible and can be used at all store levels below it.
The selector determines which location's standard texts you see and edit. Locations with existing standard texts are shown in bold in the selector. If you change location, the list is updated automatically. The selector is not a field on the standard text itself, but a filter for the display.
The order of standard texts in the list also determines the order in which they are shown in the lookup dialog. You can change the order by selecting a row and clicking the up arrow or down arrow in the left button group. The up arrow is only active when the selected text is not already the topmost on the page. The down arrow is correspondingly only active when the row is not the bottommost.
Above the list there is a search function for free-text filtering. Type a search term to narrow the list. Click Cancel search to reset the filter and show all standard texts again.
See How to search in lists for more about searching and filtering.
Create new (+): Always available. Opens the edit view to create a new standard text.
Edit (pencil): Requires a row to be selected. Opens the edit view with the selected standard text's data.
Delete (cross): Requires a row to be selected. Deletes the standard text and shows a confirmation message on success. Deletion cannot be undone.
Double-click a row to open the edit view directly.
The edit view is used to create and edit standard texts. It contains a form with three fields as well as the buttons Save and close and Cancel.
Heading: The name under which the standard text is shown in the list view and the lookup dialog. The field is required. The heading must be unique within the selected location – if you try to save with a name that is already in use, the error message "A standard text with the same name already exists" is shown.
Content type: A dropdown that determines whether the content is plain text or HTML. Possible values:
Text (PlainText): The content is plain, unformatted text. The content field is shown as a simple multi-line text field. Choose this type for SMS messages, as SMS does not support HTML formatting.
HTML: The content can contain HTML formatting. The content field switches to a visual HTML editor (TinyMCE), which allows bold text, links, lists and similar formatting. Choose this type for email messages, where formatting is supported. The HTML editor also includes a button for inserting text commands directly into the content.
Content: The actual text content for the standard text. The field is required and is multilingual: if Sapera is configured to support multiple languages (cultures), you can specify separate content variants per language. Change the content type from Text to HTML to enable the visual editor.
Text commands are placeholders that are inserted into the content as `{CommandName}` and automatically replaced with actual data when a message is sent. Examples of available text commands:
{CustomerFirstName} – the customer's first name
{CustomerFullName} – the customer's full name
{CustomerLastName} – the customer's last name
{CustomerOrganizationIdentifier} – the customer's CVR number
{CustomerReferenceNumber} – the customer's reference number
{Identifier} – identifier for the relevant record
{InvoiceIdentifier} – invoice number
{MobileNumber} – mobile number
{MobilePayNumber} – the MobilePay number associated with the sending department
{NumberIdentifier} – sequential number
{PostalDistrict} – city
{ProductInstanceDisplayName} – the product instance's display name
{SalesOrderIdentifier} – sales order number
{SerialNumber} – serial number
{TotalAmount} – total amount
{TotalAmountForURL} – total amount formatted for use in a URL (without characters that are invalid in links)
{Address} – address
{ZipCode} – postal code
{DynamicFields} – dynamic fields
When the content type is HTML, you can click the Insert text command button above the content field to open a dialog with available internal command standard texts and add them to the content.
It is important to distinguish between two different concepts, both of which appear in the user interface:
Standard texts are the custom pieces of text you create and maintain on this screen. They are visible in the lookup dialog when you compose a message.
Text commands are internal system placeholders (such as `{CustomerFullName}`) defined by the system. They can be inserted into the content of a standard text and act as dynamic fields that are filled in with real data on send. Text commands are not managed here – they are available via the Insert text command button in the HTML editor or as a separate text command button in certain message dialogs.
Save and close: Validates all fields and saves the standard text. If validation fails (e.g. missing content or duplicate heading), error messages are shown at the relevant fields, and nothing is saved.
Cancel: Leaves the edit view without saving changes and returns to the list view.
The lookup dialog opens automatically when you click the Standard texts button in an SMS message or use the Insert text command button in an email's HTML editor. You cannot open it directly from the Standard texts screen.
The dialog shows a checklist of available standard texts. You can select one or more standard texts. Click OK to insert the selected standard texts into the text field – the content is appended to what is already written. Click Cancel to close the dialog without inserting anything.
The lookup dialog respects location inheritance: you see the standard texts available for the current location, including texts inherited from higher levels. The order in the dialog matches the order in which the standard texts are sorted in the list view.
Here is an example of a standard text intended for sending a MobilePay payment link via SMS. Use the content type Text and insert the following as content:
Here is a payment link for invoice `{NumberIdentifier}` https://www.mobilepay.dk/erhverv/betalingslink/betalingslink-svar?phone=`{MobilePayNumber}`&amount=`{TotalAmountForURL}`&comment=Invoice no.`{NumberIdentifier}`&lock=1
When the SMS message is sent, the three text commands are automatically replaced with the invoice number, the store's MobilePay number and the amount due.
Read the article SMS messages for a walkthrough of how standard texts are used in practice when you send SMS messages.
If you have any questions, you are welcome to contact support.
Want to know more?
Read more in these related articles:
Translated texts
Set up language-specific names for system types such as orders, serial number items and email categories
General settings
General system settings in Sapera. Here you specify the time zone that times on receipts, journals and reports are displayed and calculated from.
