SaleMove

This package provides capabilities that extend the Avoka Transact platform for users wishing to include SaleMove functionality in their forms.

SaleMove is fully contained within Maestro and the Form definition. There are no Transact Manager Services. The Maestro components are described below.

1. SaleMove API

   A Maestro native widget to enable SaleMove functionality. Text/voice/video chat, as well as co-browsing and other SaleMove features, are automatically activated, hardware permitting.

2. Push To SaleMove Button

   Maestro Component that demonstrates one feature of the SaleMove API -- programatically pushing data from the Form to SaleMove for view by the Customer Service Rep.

   The SaleMove API native widget must be included on the Form.

Licensing

Clients must ensure they are appropriately licenses in order to use this package. Organisations who wish to use this package are required to establish a commercial relationship with SaleMove directly.

Compatibility

This package has the following compatibility requirements:

Installation Instructions

To install this package please walk through the following proceedure:

1. Unzip the package to a directory on your computer
2. Import each archive found in the libraries folder to Maestro. Importing these into the Organisation level libraries folder is recommended as this will make the components available to all projects, however they can be imported at the Project level if required.

CSP Configuration

The Content Security Policy (CSP) response header helps you reduce XSS risks on modern browsers by declaring what dynamic resources are allowed to load via a HTTP Header, thereby protecting your solution from a range of vulnerability attacks.

The SaleMove integration loads a remote JavaScript library which is injected to the form, and this will get blocked if the form header includes strict Content Security Policy (CSP) settings. By default, Avoka Transact has strict CSP settings configured so these will likely need to be modified in order to enable the SaleMove integration.

You can configure CSP settings in Transact Manager at a system wide level via the 'Form Submission Access Controller' service, or at an Organization level in the Security tab. The following Sample CSP demonstrates how to enable the SaleMove JavaScript integration:

script-src 'self' https://*.salemove.com 'unsafe-inline' 'unsafe-eval'; object-src 'none'

Note the 'unsafe-inline' and 'unsafe-eval' directives are present because the SaleMove JavaScript SDK use in-lined JavaScript and eval statements

For more information see CSP on The Avoka Community

Usage Instructions

To configure this component please walk through the following procedure:

1. Open your form in Transact Maestro and drag and drop the 'SaleMove API' component from the Palette. This widget is invisible, so it can be placed at the top or bottom of the form. Best practice is to place this object so that it appears first in the Form on the Structure Panel

If you require to push data from your form to SaleMove, to be viewed by the Customer Service Rep, please walk through the following procedure:

1. Drag and drop the 'Push To SaleMove Button' button from the Palette
2. Open the SaleMove section from the properties of the Push To SaleMove Button button

3. Open the Standard Inputs screen, and map all the fields you would like to send to SaleMove, to be viewed by customer service representative. The supported fields are: Name, Email, Phone Number and Notes

To include other fields:

4. Open the Custom Inputs screen, and add all the fields you would like to send to SaleMove, to be viewed by customer service representative (For example add new record with Key as 'Gender' and Field Reference as 'data.gender')
5. Typically you would hide the button and fire the click rule from another trigger in the form using Form.fireRule("click" ,"pushToSalemoveButton" , data);

Masked Fields

SaleMove supports the ability to mask sensitive field contents such that the operator cannot see the data. To apply this operator masking to selected fields add a Dynamic Class rule that adds the following CSS class:

return "sm_cobrowsing_masked_field";