Related articles

DevelopersAPI guides

New Watchlist enhancements offer even more analysis opportunities

February's update provides you with the opportunity to add more in-depth analysis tools to your Enable solution. A significant amount of effort has been put into further developing our new Watchlist app, alongside a wealth of background and performance improvements.


When is the update deployed?

Our latest update was deployed to your UAT environment on 22nd February 2019 and is now available for testing. This UAT environment is separate to your Live environment and provides a suitable testing platform without any risk to the integrity of your live data.

The UAT process will last for approximately 6 weeks. During this time you will be able to try out the new features and give us your feedback. The update will be deployed to your Live Enable environment on 2nd April 2019.

What’s new?

Watchlist app

During this update, Enable have made further enhancements to the Watchlist app. This feature allows Commercial and Finance teams to monitor the progress of targeted deals. The following enhancements have been made to this feature.

UI for actual turnover bands

If a deal has a configured deduction deal or discount percentage, this will be stated in the Watchlist app UI with the amount that has been deducted or discounted. If both a deduction and a discount have been configured for a deal, then the combined total amount will be displayed. This aims to help the user understand the disparity between the displayed actual turnover and the assigned actual turnover band.


Actual band number in downloadable file

For any deals with configured deductions or discount percentages, the actual band number column (column V) in the downloadable file that the Watchlist app generates will make the same assessment of the band row that is used for the Watchlist app UI.

Separate targets and earnings turnover

Modifications have been made to Watchlist calculations to allow for a more sophisticated handling of separate target and earnings.

Growth deal baseline handling

A change has been made across all Watchlist calculations which will require 'manual' forecast values to be entered net of the baseline. This means that the actual forecast spend will be the sum of the baseline and the manual forecast value.

“Reporting only” dimension attribute

A new display type for dimension attributes can now be configured, called Reporting only. Dimension attributes configured as Reporting only will not be visible within the dimension item listing or the selection rule set up screens within the deal set-up area.

If you are interested in utilising this new feature, please raise a ticket via the UAT tile within the Support Hub and Enable’s Client Services team will configure this for you.


Enable have undertaken work on internationalisation of Enable by developing the infrastructure for multiple language options and timezones at the client, user and scheme level.

English, French and German translations have been made available for the Login page and some top level navigation.


Scheme based turnover line

Baseline turnover period

A new setting for Baseline turnover period can now be configured by Enable administrators. This setting can be used to set the deal baseline periods to be based on the scheme baseline period and allows for direct comparison between schemes that contain multiple concurrent deals.

The existing means of determining the baseline period is configured by default, while a new Period relative to scheme baseline period setting will change how the baseline period of deals for a scheme with a duration more than one year is determined. This ensures that the baseline turnover of any deal is the same turnover as the deal from which it was replicated by applying the context of the scheme dates.

Baseline earnings re-calculation triggers

Baseline earnings re-calculations have been updated so that reconciled turnover lines only queue overnight baseline calculations for deals where the reconciled turnover is within its baseline period rather than its actual period.

Centralisation of calculation of baseline periods

The logic for determining baseline periods is now shared across the application to address any inconsistencies that may have previously been encountered.

Enable API

Enable is continuing to invest development time on a Enable API. This aims to facilitate both the ongoing development of Enable itself as well as the development of future products, both first party and potentially by third parties.

Security improvements

Recent penetration test feedback has been addressed to improve the security of the Enable application.

This includes adoption of Content Security Policy and XSS headers, removal of server-identifying headers, disabling TLS 1.0, turning off auto-complete on password fields, and an account lockout feature.

Responsive breadcrumbs

The breadcrumb navigation has been enhanced to adapt to smaller screen sizes and support more navigation items by overflowing into a dropdown menu.

Deal description calculation improvements

The logic to automatically calculate deal descriptions has been improved to ensure that any changes to dimension collection item attribute values will always result in a correct description recalculation for all affected deals.

Calculation job triggered deal calculations

The selection rule job processor has been updated such that any deal calculations that it generates are correctly marked as being created by a “Dimension collection saved” action, rather than a “Deal refresh” action.

Deal replication improvements

The deal replication logic has been improved and selection rule jobs are now always ran for a newly replicated deal. This ensures that the selected dimension items are correct.

Duplicate dimension collection item values

An issue was occasionally causing duplicate dimension collection item values to be displayed within scheme PDFs. This has now been fixed.

Duplicate trading partner portal emails

An issue was occasionally causing duplicate approval emails to be sent from the trading partner portal. This has now been fixed.

What’s coming up?


In line with Enable’s commitment to release an Enable update every six weeks, our next update will be deployed for testing within your UAT environment on 5th April, with deployment to your Live environment to take place on 15th May.

What we’ve got planned

As part of our April update, we will be making further performance optimisations and platform enhancements. Alongside this, we will be introducing a series of new functionality, as well as enhancing existing Enable features. Further details of our next update will be provided as part of the April ’19 Enable update.

Automated turnover import batch controls — Database deadlocks

Multiple changes to the automated turnover import system will be made to reduce the number of database deadlocks that occur. The delete step within the automated turnover import functionality will be changed to no longer be transactional. If the deletion fails due to transient database issues, the system will automatically retry the deletion step with an increasing amount of time between retry attempts. Imports made using the automated turnover import functionality will also be batched according to the “Transaction date” value for each trading partner.

Cash App updates

Bulk payment adjustment upload

A new area called Uploads will be accessible to admin users in the Cash App. This area will allow the user to upload a Payment allocation CSV file, and the deal lines within the CSV file will be adjusted in bulk. This bulk adjustment will have the same effect for multiple deal lines as a manual individual payment adjustment has for a specific deal line. This will allow users to adjust amounts of debt for large numbers of deal lines in a more efficient manner.

User interface changes

The platform administration area will have a new setting for the Cash App, Accounts type, where a user can choose Receivable or Payable. When set to Receivable the Cash App the current UI will remain unchanged. When set to Payable the Cash App will be optimised for customer rebates, with the labels within the UI being changed from representing money being owed to the client to money owed by the client to customers.

Multi-partner reporting — Performance impact research

The Enable development team will research the impact and viability of enabling multiple trading partner selections on a report for a client. The performance impact of key metrics such as the number of trading partners selected and the time period being queried will be reviewed in order to determine limitations to future multiple trading partner reports in order to ensure the continued performance of the Enable solution.

Scheme PDF updates

Increased options for automatically populated terms items

The selectable options for the Data field terms item type will be increased to include every configured trading partner dimension attribute as well as the name configured for the trading partner.

Increasing the number of signatories

The limit on the number of signatories displayed on a scheme PDF file will be removed. This will allow the client to configure as many workflow roles and signatories for a scheme as they require.

Option to hide discount percentage

A new option entitled Hide discount % on scheme PDF will be added to the platform administration area, which is accessible by Enable team members only. When this option is selected the % Discount, deducted from turnover before calculating earnings section of the scheme PDF will be hidden.

Scaling of Azure app service plans

The app service instances hosted in Azure will be upgraded to a higher performance configuration. This will improve the performance of our UAT / Staging and Live environments.

Scheme approval page performance

We will undertake an investigative review and groundwork to improve the performance of the scheme approval page.

If you have any questions regarding our current or upcoming Enable updates, please contact your Client Services team via the Support Hub at

Not useful
Very useful
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Still have questions?
Raise a ticket or contact our support team.