The Jellyfish release introduces a new feature to the Classifier, Lead Auto-Conversion. This feature can automatically convert incoming Leads as well as removing new Leads that are duplicates. In addition to this, a number of pages have had their look updated, including the Tags page, which now features the ability to edit tags across multiple Team Members at once, and the Logs page, which has been restructured to be a central location for all logs across the app. A new Team Performance page has been introduced to help managers keep tabs on how their team are performing, and make adjustments to relevant tags. Caps can now be defined at custom intervals, allowing for fine control of how many records members can receive. Finally, both the widget and the test tool have had some minor improvements to how they function.

Install Instructions





Lead Auto-Conversion

Lead Auto-Conversion allows the classifier to automatically convert incoming Leads into Accounts, Contacts and Opportunities. Users can define a number of rules to determine exactly which Leads do and do not get converted. This can utilize the classifier's Lead Matching functionality to intelligently convert into matched Accounts and Contacts. Additionally, if matched to incoming Leads, the incoming Lead can be de-duplicated to avoid extra Leads cluttering up the Org.


Team Performance

The new Team Performance page gives an overview of your team member's recent performance. This page will show the hours worked per team member over your chosen time period, as well as metrics showing their performance. Metrics will vary depending on team configuration; for Lead teams you'll be able to see the conversion rate for each team member. For Case and Opportunity teams you'll be able to see the close rate, and for any teams using Time to Action, you'll be able to see the average time to action for each team member.

Additionally, if using Tags for controlling caps and weighting, you can view and manage these from this page, perfect for adjusting people's assignment amounts in response to their performance.


Tags Redesign

The Tags management and assignment pages have been completely redesigned with our new look and feel. The pages are easier to navigate, display relevant information and contain new features such as the ability to assign and unassign tags from multiple users at once.


Settings Redesign

The application settings pages have been updated to our new look and feel, including a restructure of the pages, ensuring that advanced settings such as processing mode and frequency are separated from more commonly changed settings. The new licensed users page includes an export function that allows you to download a CSV file containing information on all licensed users.


Logs Redesign

All of the logs pages have been unified under the Distribution Logs tab, including the Classifier logs pages for Territories and Lead Matching, as well as two new logs pages for Object Sync and Auto-Conversion. These pages have all been updated to the new look and feel and feature comprehensive filtering, to help you find the logs you need quickly.


Classifier Redesign

The Classifier has had a redesign, bringing the pages visually inline with the rest of the application. Some of the pages have been re-organised and a single backfill page has been built which allows you to classify Territories, Lead Matching and Auto-Conversion in one action.


Custom Caps

Caps can be used in Teams or Distributors to limit how many records can be assigned to a user over a given time period. With the Jellyfish release, the time periods are now customisable, with timeframes from 5 minutes to 31 days.


Widget - My Work

The widget will now display up to five records assigned to the current user. If using SLAs, the My Work area will also show how long until the SLA is counted as missed. Additionally, users are able to see all of their work assigned from Distribution Engine by clicking the 'Assigned to Me' link.

Test Tool

Test Tool - Tag tests

The test tool has had a visual upgrade, improving how we display information on caps and tag filters to make it easier to read and determine whether your distributor is ready to be used.


Other Improvements




When adding team members, you can specify whether they are added as active or inactive so that new team members can avoid immediately getting assigned records.

Teams / Distributors

When enabling filters or SLAs the first row is added as a starting point.


In places where distribution hours are shown, for team hours that use a shift, the name of the shift is included.


Defects Resolved




On the first load of the team summary page, the charts are now the correct size.


Certain org-wide encryption settings would cause the creation of a new team to fail without extra verification. This has been resolved.


When load balancing is set to active count/value, the distributor settings correctly show the load balancing level as "team".


Removed the respect availability option for current owner distributors as they are not relevant.


Removed the send email notifications option from queue teams as it is not relevant.


Re-introduced the warning for filters when using the equals operator and a value that contained a colon/semi-colon.


Corrected the tool tip for the lookup owner where clause.


Resolved an issue where the current week of the shift planner was not editable for users in certain time zones.


Resolved an issue that prevented some of the pop-up dialogs from showing when the browser was zoomed in or a small resolution was used.


Corrected the warning that an org had reached their maximum number of classifier territories when it hadn't.


If more than 1000 unique team members exist, the Analytics page would fail to load. This has been fixed but will only list the first 1000 users, and is something we will be improving in the next major release as part of a redesign.


Patch Releases




  • Fixed the test tool where it could fail when a team filter included a condition on a double being equal to null.
  • Resolved an issue when a trigger distributor included a filter, it caused the settings page to fail to save.
  • Resolved an issue on the performance page that meant it could fail to load if a team had no team members.
  • Updated the licensed users page side panel to include the active status of the user and team member.


  • Resolved an issue where the Lightning Widget could fail to load when there are a large number of assignments for the user.
  • Improved handling of aborting distribution jobs that have been queued for a long period of time.


  • Added back in the ability to select team members on the distribution log filters without first selecting a team.
  • When adding the Lightning widget to a page or utility bar, you can now optionally hide the "Assigned to me" list.
  • Reduced the maximum number of items shown in the "Assigned to me" list in the Lightning widget, as it was failing on some orgs that have lots of assignments.
  • Resolved an issue where, if an export failed and the error message was too long, it would cause the export to still show as exporting.
  • Corrected the licensed user count on the licensed users page so that it didn't include inactive Salesforce users.
  • Added the new classifier pages to the Distribution Engine admin permission set, as they were previously missing.
  • Fixed an issue when configuring auto-conversion that would de-select the converted lead status if multiple existed on editing a rule.
  • Support now has some additional options to tweak the throughput of auto-conversion to handle different setups.


  • Added an option to show the last action fields in the data table of the distribution logs page, as per prior versions of DE. Contact Support to enable this option.
  • Increased the timeout when fetching the count of records to backfill in the classifier to avoid failures.
  • Resolved an issue when a field used in post assignment was renamed, the selection drop down wasn't being shown to change it.


  • Added an option in auto-conversion to update a field on both new and existing records. Currently, and by default, it will just update the field on new records.
  • To ensure consistent de-duplication, we now make use of the Lead Matching tie-breaker to determine which Lead is the one to keep when there are multiple records processed that match each other. This relates mainly to using the backfill.
  • Made a change to ensure that failed backfill auto-conversion records aren't automatically picked up in the next backfill, they will only be processed if they meet the criteria.
  • Resolved an issue where the wrong Distribution Engine details record was used during auto-conversion when multiple existed (due to a different issue).
  • Fixed an issue in the test tool where it would incorrectly show that a static tag filter didn't match a member when using "does not include" and they didn't have the tag assigned.


  • Resolved an issue where the lookup owner where condition value was locked if the "in" operator was used.
  • Reduced the frequency of warning emails when there are delayed pending assignments and frequent health checkers are in use.


How did we do?

Impala Upgrade Process

Jellyfish Upgrade Process