Release History for Motivate

What's New?

Version 3.4 (8.14.2 base app release) | 14th March 2019

Improved Gallery

The Gallery has a fresh new look having been re-designed using the Lightning Design System. Improvements have also been made to the categorisation and tagging of images, which makes searching even easier. The copy-to-clipboard functionality has also been improved so that there is no reliance on Adobe Flash support.

Improved Insight Page Layout

Enhanced layout and sections which mirror the Reward page layout in order to aid readability and familiarity when transitioning from Reward records to the new Insight records.

Fixed Scheduled Behaviours execution

An issue was identified when upgrading from v7 to v8 that could cause Scheduled Behaviours to not be correctly scheduled for execution.

Fixed Seed Base Behaviour updates

A subset of new seed Base Behaviours have had their criteria updated to ensure that they function correctly, as well as minor naming and description updates.

Fixed Assessment Engine

The assessment engine was being needlessly initiated in certain scenarios and, therefore, was unnecessarily consuming resources.

Version 3.4 (8.11 base app release) | 22nd February 2019

New! Observations

The new Observation structure allows interactions that are performed by licensed SuMo users within Salesforce to be discreetly recorded, with this information being the basis for Insights and Rewards. Observations can be triggered by any type of SuMo user in accordance with Base Behaviours that have been configured. When active Base Behaviours' criteria are met, an Observation record will be created and tagged with information that allows for Insights and Rewards records to be subsequently generated where applicable. The Observation structure, therefore, provides a concise and complete record of the behaviours that are performed by all SuMo users within Salesforce. This information is then utilised within the SuMo app to deliver behavioural Insights and recommendations, as well as drive the motivation features which include Rewards.

New! Insights

The Observation framework also provides the basis for the new Insights capabilities that are included as part of this release. When enabled, Insight records are now generated from Observations that can then be used by Opportunity Insight to provide the performance analysis capabilities and to drive predictions. As a consequence, Experience Groups (or Competitions) no longer need to be created and configured specifically for Insight, as Reward data is no longer used for these purposes. However, the greatest benefit is that aggregate Behaviour data can now be included as part of Opportunity Insight, which was not previously possible. Therefore, behaviours that count Tasks performed on Opportunities, or the total amount of Products added to Opportunities, for example, can now be surfaced and used within Opportunity Insight.

New! Milestones

Within Competitions and Experience Groups, Behaviours can now include individual Milestones that can be configured as interim goals towards the overall Behaviour target, or alternatively as stretch goals beyond the target. Milestones can be customised with specific Badges, Points and Reward Messages that are different to the associated Behaviour, and these Milestones can be visualised in the SuMo UI components both on Desktop and Mobile devices. Milestones can be configured on any type of aggregate Behaviour, whether it be a count of actions or a sum of a specific standard or custom object field. Milestones, therefore, provide a mechanism to incentivise and award users along the path to completing Behaviours - which in turn builds cadence and increases the likelihood of completion.

Improved Assistants

The Competition and Experience assistants have been re-engineered in this release, and now include a number of feature enhancements and bug fixes. These enhancements include the ability to immediately edit Behaviour properties when they have been added, revert changes made to Competitions and Experience groups while they are being edited, show the count of active Behaviours and Participants, and allow Competitions and Experience groups to be marked as 'Draft' when they are incomplete. In addition, there have also been improvements to member management, including the ability to categorise and define roles within templates and across multiple members.

Fixed Timeout when deleting Competitions

An error was being thrown when attempting to delete competitions that contained over 1000 Members, this has now been resolved as a result of the re-engineering of the Assistants.

Fixed Adding/Removal of Members is incorrect

Scenarios were identified where adding and removing members from Competitions and Experience Groups could lead to the incorrect number of members to be persisted on save, this has now been resolved as a result of the re-engineering of the Assistants.

Fixed Unable to re-schedule Experience Groups

An issue was identified where the start and end date/times on Experience Groups could not be correctly updated, which meant that Experience Groups could not be unscheduled.

Fixed Null Points set on Behaviours

When updating Behaviours in Competitions and Experience Groups the Points value could be inadvertently changed or deleted without the user knowing.

Fixed 'Show More' button incorrectly displayed

When adding Members to Competitions and Experience Groups the 'Show More' button was being displayed when there were too few members listed to require further members to be displayed.

Fixed Incorrect Badge information displayed

When adding Behaviours to Competitions and Experience Groups the Badge Type value was being incorrectly displayed in the Badge column, instead of the Badge Name.

Fixed Behaviour Criteria missing picklist values

The picklist values for newer object fields (e.g. AssetLevel on Asset) in the Standard Behaviour Criteria component were not loading correctly as a result of this and other related components being on an older Salesforce API version.

Fixed Behaviour Criteria and Record Types

Searching for Record Types within Behaviour Criteria was either not returning the correct results or was not saving correctly. Behaviour Criteria that contained Record Type names that included brackets was also causing Rewards not be generated.

Fixed Behaviour Criteria Date Literals

Certain date literal values used in Behaviour Criteria were not being displayed correctly when viewed via the Criteria tab on the corresponding Base Behaviour.