Bison
Enhancements. Area Name Description Performance Auto-archive feature Some customers run a process where large volumes of records are left residing in Distribution Engine queues which, due to the filt…

Enhancements
Area | Name | Description |
Performance | Auto-archive feature | Some customers run a process where large volumes of records are left residing in Distribution Engine queues which, due to the filters set, are never assigned. Functionally this is perfectly valid. However, it has been reported by Salesforce that this approach causes a heavy burden on the Salesforce database. For customers this means that the queries to retrieve records to assign can be slow, and in the worst case cause the Distribution Engine job to fail due to time-out. The solution is to auto-archive these records after they have been in the queue for a specified period of time without being assigned (e.g. 1 month). Archiving means moving them to an archive queue and stamping the records with their original queue. If these records are updated for any reason they will automatically be moved back to their original queue to give them a chance to be assigned out. |
Algorithms | Retain sticky on widget toggle off | Previously, sticky assignment considered that a team member who is toggled offline in the widget was not available and therefore the assignment could go elsewhere. This is now optional and the sticky assignment can still be made to team members who are available according to their hours / OoO but currently toggled offline. |
Algorithms | Opt out of team wide caps | Team wide caps were previously applied to all distributors. It is now possible to opt out of team-wide caps for certain distributors. For example, a distributor for hot leads could always assign regardless of team members reaching their daily limits. |
Algorithms | Sticky assignment + auto-reassign | Previously, auto-reassign could not be used in conjunction with sticky assignment (the records would continually stick back to the original team member). This has now been changed to break the sticky assignment on auto-reassign to allow assignment to another team member. |
Data | Link to contacts from log | A new lookup field has been added to the distribution log object. This allows reports to be generated to show the assignment history along with the associated contact information. |
Data | DE fields added to Account and Contact | Fields for Is Distributed, Last Distributed, Is Reassigned and Last Reassigned have now been added to Account and Contact. These were previously only available on Lead, Case and Opportunity. |
UI | Inline page added to Account and Contact | The Distribution History and test inline page is now also available for Account and Contact page layouts. It was previously only available for Lead, Case and Opportunity |
UI | Hide frequency when using Queueable | The Queueable processing method runs in a continuous loop. Frequency has no effect on this method - the rate at which it runs is controlled by Salesforce. The frequency is therefore not shown in the UI when this method is used. |
UI | Team limits - maximum number of distributor and team member limits applied | It was previously possible to break the application by adding unlimited numbers of distributors and team members. To provide better guidance for larger orgs, these limits are now enforced in the UI. A maximum of 30 distributors and 500 team members can now be added to a team. |
UI | Licensed user page enhancements | Some customers had difficulties with releasing licences for users that had left the company. It is now possible to click on a user and see their Distribution Engine licence and permission set usage, and also with a single click release all their Distribution Engine associations - managed package licence, permission sets and teams. |
UI | Alert reason added to inline page | In the distribution history inline page it is now possible to see the reason a record went into alert (e.g. status not equal to contacted after 30 minutes) |
UI | Team list enhancements | Enhancements to show / hide disabled teams, activate / deactivate teams using multi select. The table now also shows the number of team members and distributors for each team. |
UI | New team - default to user timezone | When creating a new team the timezone was previously defaulted to GMT. This has now been changed to default to the timezone of the user creating the team. |
UI | Increased history for tags | History of tag removal and assignment has been added. This can help troubleshooting. |
UI | Scheduler shutdown | For orgs where processing takes a long time it can sometimes be difficult to shut down the Distribution Engine because the job is showing as in-progress. This behavior has been changed, so that now when the scheduler is turned off while DE is currently running, it will wait and automatically shut down when the job has completed. So users will not need to keep retrying. |
UI | Inactive Salesforce user vs de-activated team member icons | Team members are now more clearly marked to show whether a user was de-activated in Salesforce, or disabled as a team member in Distribution Engine. |
Defects
Area | Name | Description |
UI | Console distribution counts excludes errors | Where assignment errors occurred these were previously being included in the daily distribution count. This how now been fixed and only the error column will include assignment error counts. |
UI | Generate tags from picklist error | For orgs with > 1000 objects the picklist could not be shown. This has now been fixed |
Permissions | Author apex permission set | In order to start and stop distribution engine, the author apex system permission is required. It was previously not possible for users who had this permission granted via a permission set to start and stop DE (only those with the setting on their profile). This has now been corrected. |
Algorithm | Sticky canceled where user OoO | Previously the sticky match was cleared when a user was OoO - even if no other user could be found. This has been changed to only clear the sticky if another user was found to assign to |
Algorithm | Assignment count reset for queue teams | The assignment counts were not correctly reset for queue - queue teams. This is now fixed to correctly respect hourly, daily, weekly caps. |
How did we do?
Armadillo
Chameleon