Email & Text Messaging, Including Internal Alerting

Created by Migration Bot, Modified on Fri, 23 Oct at 2:29 PM by Migration Bot

Originally written by John Hardwick, last updated Nov 08, 2024, on the Swan Retail knowledge base (FRS).


Based on SwanFRS release 1200

Overview

SwanFRS can send emails and / or text messages to customer and / or employee at key stages (or milestones) throughout the life of the sales order. This document details how to configure and use this facility.

This package is provided as an optional additional module to the standard SwanFRS application and cannot be operated without Swan enabling this feature.

Text messaging sends messages to a ‘service provider’ who convert the instruction to a text message.  Such services generally incur a service / delivery charge per text message which is outside the control of Swan.

The package works with

  • Intelli SMS (www.intellisms.co.uk)

  • Plivo (www.plivo.com)

Linking with alternative providers may require modifications to the interface, which would be chargeable therefore it is advisable to discuss your requirements and potential SMS supplier prior to signing to the service to ensure the service is compatible with SwanFRS.

SwanFRS must be connected to your exchange email server and allow email relaying to operate.

The C:\windows\system32\logfiles\FRSPOSCA folder must exist on the application server for the system to operate. Please ensure this folder has been created prior to sending test emails.

Configuration

It will be necessary for Swan IT support services to configure an email forwarding system.  If intending to use email, please discuss your requirements with your implementation consultant or contact Swan support.

Application Parameters

Menu Location: System Admin > Admin > Set Up Application Parameters

To commission the text messaging system the following application controls will require setting.

CUSTOMER_ALERTER_RUN_ASYNCHRONOUSLY

Tick to instruct the alerter process to run in background.

IS_CUSTOMER_ALERTER_SYSTEM_ENABLED

Tick to turn on customer facing email / text messaging

SMS_FROM_TAG

Specify the name / title to be used as the from or sender of the text message

SMS_PASSWORD

This is the password required by the provider of your SMS service for it to process a text request.

SMS_USER_NAME

This is the username required by your SMS service provider.

These application controls can be set at company level and therefore it is possible to have different email servers, and SMS providers per company.

Role Privileges

The following controls enable access to Text/Email functionality.

SETUP_ALERTS

This privilege provides access to the setup order progressions / milestones.

SETUP _SEND_EMAILS

This privilege enables the operator to access the send email control routin

Send from Email Address Control

Menu Location: System Admin > Sales > Set Up Send From Email Addresses

Access to this routine requires the user to possess the SETUP_SEND_EMAILS privilege.

This list of email addresses will be used when processing the alert as the ‘send from’ email address and therefore it is recommended they reflect the company name in some form e.g., Sales@SofasRus.com

The routine allows the operator to choose a location from a drop-down list.  The drop-down list will contain only the locations visible to the operator with 2 possible additions.

  •  If the operator possesses the POWER_USER privilege the list will also contain the ‘all companies’ selection.

  •  If the operator possesses the CHANGE_LOCATION_ALL the drop-down list will also contain the ‘all locations’ option (again sequenced at the top of the list immediately below the ‘all companies’ option – which if available is always first)

Once the operator has made a selection from the ‘location’ list they will then be able to enter a ‘sending’ email address. The system will ensure the email has at least one character before the @ sign followed by at least one character before a full stop and then at least 1 character following it.

The delete icon will not operate if the email has been linked to an alert – to remove an email the address must be removed from the alert first.

Alert Control

Menu Location: System Admin > Sales > Set Up Location Alerts

Access to this routine requires the user to possess the SETUP_ALERTS privilege.

The company and location drop down lists will only show companies / locations visible to the operator.

If the header control is set to all companies and / or all locations the alert will be available for all sites, where a specific location is selected, the alert applies to that location only. (Specific company / all locations indicate the control is for all locations trading within the specified company – all companies & all locations are applicable to all locations within the database)

Users with the SETUP_ALERTS and POWER_USER can set up alerts for any company / location combination they have visibility of.  Users without the POWER_USER privilege cannot set controls at company level.

The system has several preconfigured alerts.  See Message Types for a breakdown of preconfigured messages.

If the operator selects a specific location the list of alerts will consist of settings for the specific location where an alert has not been built the system will show the all location alert.  I.e., a full list of alerts will always be presented.

If the operator, whilst working with a specific location, chooses to edit an alert set to ‘all locations’ the system will create a location specific clone of the alert.  The operator may then amend, as necessary.  The new location specific alert will then replace the all location alert within the system. 

If the operator makes a location specific alert in-active the system will ask if that template is to be purged and replaced by the ‘all locations’ specific template.  The operator may choose to leave the template in-active thus turning the alert off for that location but leaving it active for other locations.

Clicking the icon instructs the system to edit the alert control.

Clicking the NEW FREESTANDING ALERT button (or option on the side menu) allows the generation of a new free-standing alert.  These alerts require manual intervention to ‘trigger’ them.  

Both options generate a screen like the one shown below –

Field

Comments

Order Alert

Only amendable when processing a free-standing alert (blocked for system alerts)

Alert names must be unique within the location (all location control)

Company

Not amendable – for reference only

Location

Not amendable – for reference only

Alert Customer

Tick to instruct SwanFRS to send a message to the customer when the alert triggers.

Send From Email

Select one email address from the list of email set for the alerts location.  The list of authorised emails will only contain emails set for the location linked to the alert. For example, if the ‘all locations’ option is chosen, then only ‘all locations’ emails will be allowed.  If the alert is for ‘location X’ then only emails for this location will be shown.

If the alert has no email addresses set the control cannot be completed.

This option is not required if the message is to be sent internally.

Email Subject

Specify a subject for the email

Email Message

Specify the message content.  The message may consist of a combination of text and merge tags.

Merge fields will be replaced with the text they represent for example <%SO%> would be replaced with 12345 at time of use (12345 being the sales order number)

See Merge Tags for a list of all the merge tags available.  Merge tags can be copied from the side panel and pasted into the message

The easiest way to generate a merge tag is –

  •   Click the mouse in the message section of the screen.

  •   Move the cursor so it is hovering on the desired merge tag.

  •  Click the mouse button three times – (first time selects the tag, 2nd time selects the word, and the 3rd time selects the whole tag)

The screen will appear like that shown below.

With the text highlighted now hold down the left mouse key and drag the cursor to where you want the merge tag to appear in your message.

Releasing the mouse button places the merge tag in your message.

Alternatively use Control-C to copy once highlighted and then Control-V to paste into your message.

Email Type

Choose from HTML or plain text

HTML File:

If the email type is set to HTML file, the system will allow the specification of a HTML template.

To use this, feature the HTML file must be present on the server and the field contain the fully path of the file.

The easiest way to generate a HTML data file is to create the file using Microsoft Word® and save with the html suffix.

It is recommended that all HTML templates are held within a single folder on the application server within the C:\inetpub\wwwroot folder and to ensure this folder has suitable read, write, and update permissions.

For hosted operation, the documents should be saved on the shared file system and the path set to

\\fs-01\ImportExport\<company_name>\<company_name>Live\HTMLTemplates\<file_name>.html

An example of a word document is shown below –

This document is made from 4 tables joined with a repeat section in the central section designed to allow each product on the order to be displayed within the ‘repeat’ control.

When saving a word document as an HTML it is necessary to edit the HTML produced to ensure the <% tag is replaced.  Failure to do so will stop the merge tags from working.

SMS Text

Specify the message to be sent if a text message is to be sent to the customer.

Merge fields will be replaced with the text they represent.

for example, <%=SalesOrder.Number%> would be replaced with 12345 at time of use (12345 being the sales order number)

Internal Contact – Salesperson

Tick if the alert is to be sent to the primary salesperson linked to the sales order using SwanFRS internal message system. 

This option is not available for free-standing alerts – I.e., operator generated alerts cannot be used to generate internal message alerts.

If the user triggering the alert is also the primary salesperson on the order the alert relates to, the system will not deliver the internal message.

Internal Contact - User

Optionally choose a ‘user’ who is to receive the alert using SwanFRS internal message system.

This option is not available for free-standing alerts – I.e., operator generated alerts cannot be used to generate internal message alerts.

If the user triggering the alert is also the internal contact user, the system will not deliver the internal message.

Active

Tick to turn this alert on or completely off

Test SMS

This field in not retained on the database and is designed to test the alert delivery.

This feature is only available if SMS operation has been configured and there is an SMS text message associated with this alert.

To test the operator must enter a telephone number (usually a mobile) and then click the SMS TEST button.  This will deliver the SMS text (prefixed with the word ‘TEST’) to the specified number making a log of the test communication.  A confirmation message will be displayed to screen.

Test Email

This field in not retained on the database and is designed to test the alert delivery.

This feature is only available if email operation has been configured and there is an email message or HTML file set (dependent upon the email type setting)

To test the operator must enter an email address and then click the EMAIL TEST button.  This will deliver the email (prefixed with the word ‘TEST’ in the subject) to the specified address presenting a message to the operator that the message has been sent.

Further screen controls are message type dependent.

Once created the system shows the alert as active indicating the message delivery type.

The icon be used to remove an alert.

Message Types

At time of installation an alert trigger will be set as inactive and linked to ‘all locations’

Alerts are only generated when the active flag is switched on for the operators processing location (or if no location specific alert control, for all locations)

The alert will deliver messages to the parties indicated in the alert settings – it is possible to send up to 3 alert messages out per trigger (customer, primary salesperson and / or a designated operator.)

If the alert is configured to send a message to the customer, the customer record must have preferred alert control set to SMS or Email.  If set to none the alert will be ignored.

The list of order alert triggers is listed below

Alert Name

Action Causing Triggering of the Alert

New Sales Order Acceptance

This alert is triggered when the sales order is fully accepted for the first time.

Accepting a second time (after an amendment does not generate this alert)

Sales Order Amendment

This alert is generated whenever a sales order is accepted following an amendment.

If sending an alert via the internal message system this alert will only occur if the operator making the change is not the primary salesperson on the sales order.

Change of Proposed Delivery Date

This alert is triggered if the delivery date on the sales order is changed either by purchase order acknowledgement or manually.

If sending an alert via the internal message system this alert will only occur if the operator making the change is not the primary salesperson on the sales order.

Goods Receipt

This alert is triggered with the receipt (and unreceipt) of goods linked to sales orders

Only 1 alert is triggered per sales order irrespective of the number of items received linked to that sales order.

Allocation of Scheduled Delivery Date

This alert is triggered when a line on the sales order is allocated a delivery run.

Only 1 trigger per sales order at a time is generated – i.e., if 2 items are scheduled for delivery off the 1 sales order on the same delivery run the alert is sent once.

Change of Scheduled Delivery Date / Timeslot

This alert occurs when the date or timeslot of a scheduled delivery changes or if the delivery is cancelled or changed during delivery planning.

Only 1 alert per sales order is triggered.

If sending an alert via the internal message system this alert will only occur if the operator making the change is not the primary salesperson on the sales order.

Purchase Sending

SwanFRS already can send POs via email (sent with a PDF attachment) 

This feature will be migrated to alert messaging thus allowing the retailer to define how the email is sent.

For this alert, the customer is effectively the supplier.  The email address is taken from the setup supplier routine.

Delivery Run

There are several alerts for the delivery run.

The alert creation for delivery runs is a manual process and will use the status of the delivery run to decide which alert message to use.

Delivery run status catered for are –

  • Prior to despatch – the run is not flagged as despatched

  • Despatched - the run has been flagged as despatched

This option can be run at any stage and will send a block of alerts out to all recipients on the delivery run.

Customer Collection Date

This alert is triggered when an item delivered to the customer is flagged for collection back via a scheduled delivery run. – see the Delivery section.

Freestanding Customer 

This alert is manually instigated - see section Freestanding Event

Free-standing alerts cannot be generated for issue to the internal message system.

Merge Tags

Tags are NOT case sensitive (i.e., <%=service.id%> is the same as <%=Service.ID%>).

The = symbol is optional (i.e., <%=Service.Note%> is the same as <%Service.Note%>).

It is possible 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%>.

Merge tag

Comments

<% Repeat%>

e.g.  <%Repeat%><%stock.detailnumber%><%EndRepeat%> this text would generate a list of all stock details linked to the alert. (One per line)

<%=Customer.AccountNumber%>

Customers account number

<%=Customer.Address.AddressLine1%>

First line of the customers address

<%=Customer.Address.AddressLine2%>

Second line of the customers address

<%=Customer.Address.AddressLine3%>

Third line of the customers address

<%=Customer.Address.AddressLine4%>

Fourth line of the customers address

<%=Customer.Address.AddressLine5%>

Fifth line of the customers address

<%=Customer.Address.AddressLine6%>

Sixth line of the customers address

<%=Customer.Address.County%>

Country of the customers address

<%=Customer.Address.FlatNumber%>

Flat number

<%=Customer.Address.FullAddress%>

Full address (all customer address fields concatenated together)

<%=Customer.Address.HouseName%>

House name

<%=Customer.Address.HouseNumber%>

House number

<%=Customer.Address.Postcode%>

Postcode

<%=Customer.Address.PostTown%>

Post town

<%=Customer.Address.State%>

State

<%=Customer.Address.Street%>

Street

<%=Customer.Address.Suburb%>

Suburb

<%=Customer.Email%>

Customers email address

<%=Customer.Forename%>

Customers first or forename

<%=Customer.FullAddress%>

Customers full address

<%=Customer.FullName%>

Customers full name (For example Mr A Smith)

<%=Customer.HomePhoneNumber%>

Customers home phone number

<%=Customer.Initials%>

Customers initials or name

<%=Customer.MobilePhoneNumber%>

Customers mobile phone number

<%=Customer.Number%>

Customer reference number

<%=Customer.Surname%>

Customers surname

<%=Customer.Title%>

Customers title / salutation

<%=Customer.WorkPhoneNumber%>

Customers alternative phone number

<%=Date%>

System date

<%=DateLong%>

Long date

<%=DateShort%>

Short date

<%=NumberOfRepeats%>

The number of occurrences

<%=Product.Description%>

Product description

<%=Product.ModelNumber%>

Products model number

<%=Product.Range%>

Product range

<%=Product.SKU%>

SKU reference

<%=PurchaseInvoice.Number%>

Purchase order invoice number

<%=PurchaseInvoice.PurchaseInvoiceDate%>

Purchase order invoice date

<%=PurchaseOrder.AcknowledgementDate%>

Purchase order acknowledgement date

<%=PurchaseOrder.AcknowledgementReference%>

Purchase order acknowledgement reference

<%=PurchaseOrder.Number%>

Purchase order number

<%=RepeatCount%>

The record id of the repeat process (row count)

<%=SalesOrder.Number%>

Sales order reference

<%=SalesOrder.PadNumber%>

Manually specified sales order reference

<%=Service.ID%>

Service reference

<%=Service.Note%>

Service notes

<%=Service.Number%>

Service number

<%=Service.Operative%>

Service operator

<%=Stock.Number%>

Stock number

<%=Supplier.Address.AddressLine1%>

Suppliers address (line 1)

<%=Supplier.Address.AddressLine2%>

Suppliers address (line 2)

<%=Supplier.Address.AddressLine3%>

Suppliers address (line 3)

<%=Supplier.Address.AddressLine4%>

Suppliers address (line 4)

<%=Supplier.Address.AddressLine5%>

Suppliers address (line 5)

<%=Supplier.Address.AddressLine6%>

Suppliers address (line 6)

<%=Supplier.Address.County%>

Suppliers' country

<%=Supplier.Address.FlatNumber%>

Supplier flat number

<%=Supplier.Address.FullAddress%>

Suppliers full address

<%=Supplier.Address.HouseName%>

Suppliers house name

<%=Supplier.Address.HouseNumber%>

Supplier house number

<%=Supplier.Address.Postcode%>

Suppliers' postcode

<%=Supplier.Address.PostTown%>

Suppliers post town

<%=Supplier.Address.State%>

Suppliers state

<%=Supplier.Address.Street%>

Supplier street

<%=Supplier.Address.Suburb%>

Suppliers' suburb

<%=Supplier.FullAddress%>

Suppliers full address

<%=Supplier.Name%>

Suppliers trading name

<%=Time%>

System time

<%=Today%>

Current date

<%=User.Email%>

Operators email address

<%=User.Fullname%>

Operators full name

<%=User.LoginID%>

Operators login ID

<%=User.ServiceOperative%>

Service operator

<%=User.Username%>

Users name

<%=Delivery.DateShort%>

Delivery Date Short

<%=Delivery.DayOfWeek%>

Delivery Day of Week

<%=Delivery.Time%>

Delivery Time

<%=Delviery.DateLong%>

Delivery Date Long

<%=PurchaseInvoice.PurchaseInvoiceDateLong%>

Purchase Invoice Date Long

<%=PurchaseInvoice.PurchaseInvoiceDateShort%>

Purchase Invoice Date Short

<%=PurchaseInvoice.PurchaseInvoiceDayOfWeek%>

Purchase Invoice Day of Week

<%=PurchaseOrder.AcknowledgementDateLong%>

Acknowledgment Date Long

<%=PurchaseOrder.AcknowledgementDateShort%>

Acknowledgment Date Short

<%=PurchaseOrder.AcknowledgementDayOfWeek%>

Acknowledgment Day of Week

<%=PurchaseOrder.AcknowledgementTime%>

Acknowledgment Time

Customer Control

To use the email / text messaging system it is necessary to set the appropriate fields when creating / amending the customer.

The mail-out options (3 tick boxes in the third column) are used to control marketing information and not order progression alerts.

To send email / text messaging ensure the mobile and / or email address is defined and choose the preferred alert communication method.

  •    If the system is switched off the operator will not be able to make a change to the default alert settings.

  •    When switched on, the operator may choose from either SMS (text), email or none.

  • SMS option will be blocked if the mobile number is not set.

    • When operating in the UK market the system will ensure the mobile number begins with ‘07’

    • Email option will be blocked if the email address is not set.

  •  The system will ensure the email has at least one character before the @ sign followed by at least one character before a full stop and then at least 1 character following it.

The default option for a new customer will be none however if ‘order alerting’ is operational a warning will be produced a time of accepting the page, if the none option is set.  The warning will remind the operator that the customer is not configured to receive order progression alerts.

A new message will be displayed on the sales order header page if one or more freestanding alerts are active, and the customer is configured to accept email or text messaging.

This message is also shown on customer summary screen.

The message will replicate the preferred communication method for the chosen customer.

  •          This customer accepts SMS if the customer prefers text messaging, and it is active

  •          This customer accepts Email if the customer prefers email messaging, and it is active

  •          No message is displayed if the customer is not configured to receive SMS or email message

Internal Messages

The system will not generate an internal message if the user processing the action is also the primary salesperson on the sales order or if the action does not relate to a sales order.

If the user triggering the alert is also the internal contact user, the system will not deliver the internal message.

If the alert is set to send an internal message, the alert will be sent via the internal message service in addition to sending the alert to the customer (where configured to do so).   The message will be delivered to the recipient’s message board.

Clicking the avatar opens a drop down, clicking the # messages field produces the users’ message list.

The message will remain open until completed.

Clicking the message ID opens the details of the message.

The message text is that of the SMS text with the merge tags completed.

Follow up actions are as per the buttons on the right of the page.

Operation

This section details how the alerts / triggers operate within SwanFRS.

Alert Triggers

The system offers several preconfigured alert trigger points. 

  •          New sales order acceptance 

  •          Sales order amendments

  •          Change of proposed delivery date

  •          Goods receipt

  •          Scheduled delivery

  •          Change of scheduled delivery

  •          Purchase order sending

  •          Delivery run

  •          Customer collection

  •          Free-standing event

New Sales Order Acceptance

This alert is triggered when the sales order is fully accepted for the first time.

Subsequent order amendments and acceptances do not trigger this event.

A message is only sent if the customer has indicated they will accept an electronic order alert / notification and there is an active message alert set for selling location (or company)

Where an alert is issued a record of the message is recorded in the order comments (as show below)

Clicking the order notes icon presents the viewer with a screen like that shown below

Sales Order Amendments

This alert is triggered when the sales order is accepted following each amendment

The alert is only issued when the amend process is completed. I.e., the order is accepted for a second time.

Where an alert is issued a record of the message is recorded in the order comments (as show below)

In the example above, the event log shows the customer was sent a text message when the sale was originally accepted, the operator then amended the order and a text message sent once the order was accepted, post amendment.

Clicking the event opens the details for amendment or completion (subject to permission)

Change of Proposed Delivery Date

There are two places where the proposed delivery date can be revised.

Change of Lead Time

This alert is triggered when the lead time of a demand item on the sales order is altered.

This alert is issued immediately the lead time change has been applied

There are no ‘on screen’ messages for this alert however alert delivery are recorded against the sales order.

Purchase Order Acknowledgement

This process advises the operator if an order has not been acknowledged within a predefined number of days since point of issuing the purchase order to the supplier.

Acknowledgements

SwanFRS enables the creation of an expected Acknowledgement alert.  When the PO is raised and if the Acknowledgment Time is set, SwanFRS generates a forward dated reminder advising the designated recipient that the PO has not been acknowledged.

If the PO is acknowledged before this reminder is delivered, the message is cancelled.

This processing is configured and controlled via the Set Up Suppliers program.  Per supplier, the following controls are available.

Field

Comments

Acknowledgement Time

Specify the number of days, from point of ‘sending’ the PO an acknowledgment is expected.

Setting to 0 turns off this feature.

Reminder Prompt Days

Specify the number of elapsed days, after point of first ‘sending’ the PO, the system is to prompt the recipient that an acknowledgement has not been received.

The message is auto closed if a PO acknowledgement is processed before the message delivery date is reached.

Internal Contact

User

Tick the Operator option if the person sending the PO is to receive the not acknowledged message or select the recipient from the pick list available.

All three component parts must be set for the not acknowledged message to trigger.

Purchase Order Sending

Not currently available

Goods Receipt

This alert is triggered when a purchase order is receipted which is linked to a sales order where the customer has indicated they will accept order messages by text or email and there is an alert trigger available.

There are no on-screen messages – this is a fully automatic process however a record of the message issue is recorded within the sales order diary screen (as shown below).

Please consider the user of this alert as the system will send a message when goods are receipted into stock you may not want the customer to know this information. 

The main purpose of this alert is to advise via the ‘internal message’ system that goods have arrived into stock.

Also, be aware the system sends a message each time the goods are receipted therefore if goods are receipted, unreceipted and then receipted a second time the system will send two message alerts.

Scheduled Delivery

This alert is issued when goods on a sales order are scheduled for delivery.

Where configured to send internal messages the notes on the sales order will be updated to show the scheduling event and a follow up action note.

Change of Scheduled Delivery

Not currently available

Removal of Scheduled Delivery

The system can be configured to alert if one or more items are removed from a delivery schedule.

If sending internal alerts, the message will appear like that showing below –

Delivery Despatch

Dispatching a delivery run, where configured, will issue an alert.

Internal dispatch alerts will appear as shown below –

Customer Collection

Not currently available

Freestanding Event

SwanFRS offers the ability to add free format narrative against the customer and / or sales order.

If the customer has email or text alerting switched on and there is at least one active free-standing alert active for the processing location, a new button on the sales order page / customer account or diary history page (for customer or order) will be available.

The button will reflect the customers communication method (text customer or email customer)

The TEXT CUSTOMERor EMAIL CUSTOMER button will be available if there is a free-standing alert set for the subjects processing location.

Having elected to send a free-standing message to the customer the system will offer a selection of ‘free standing’ alerts.

Having selected the message text the system presents a screen like that shown below –

Clicking the red text opens the message in your browser but will not allow modification.

The system allows editing of the plain email and text formats.  In all scenarios the operator will be required to click the ACCEPT button to send the message to the customer.

Audit Log

2.14.1            SMS Log

Not currently available

Administrator Notes

SwanFRS generates a log of issued alerts

  •   For 32-bit systems this is held on the server within the C:/WINDOWS/System32/Logfiles/SwanFRSPOSCA folder

  •  For 64-bit servers this is C:\WINDOWS\system32\Logfiles\SwanFRSPOSCA

A log file is created per day containing a record of alerts issued.

Creating the HTML

If you are familiar with HTML generate the file using your preferred code generator.

An alternative is to use Microsoft’s Word package – create the design and save as a docx (this preserves the original for future change)

It is recommended that a table control be used to format the text as this gives a degree of control. 

Set the table edges to ‘no boarders’

Images

When using an image, the image must be available via the internet – use the insert picture online feature for this however it will be necessary to change this once saved as HTML.

Use merge tags as appropriate.

Then save the file as a html via the save as feature choosing ‘Web Page’ option.

This will save the file as a html document and generate a folder of matching filename.

The first step is to rename the file to an .html format.

The using an appropriate editor (suggest Notepad++) open the html and make a change to the image filename

Find the section of the html pointing to the image file (search for src)

Change the path to the full URL of the image e.g.

Src=”https:<full image path>/<image filename>.png”

The filename occurs twice and needs changing in both highlighted rows.

Creating html in this method may result in some changes to presentation when viewed in the browser.

Tags

When using merge tags, word embeds addition characters around the tag which stops SwanFRS merging the data correctly.

Within your editor program search for &gt; and &lt;

These text sequences need replacing with < and > respectively.

To make the tag operational the highlighted text needs replacing

Same section with edit to work within SwanFRS.

If available process a replace string replacing &lt; with < and &gt; with >

It is necessary to check every tag as word may have embedded other characters – e.g.

<%=<span class=SpellE>SalesOrder.Number</span>%>

Remove any text within the tag – the above example would end up as

<%=SalesOrder.Number%>

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

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article