Plauti Assign release notes

Update Instructions

• In Match Rules, GREATERTHAN / LESSTHAN values are now read as exact numbers, and currency symbols or thousands separators are no longer removed. Existing Match Rules whose values contain a comma or currency symbol (for example 1,000 or $1,000) will stop matching after updating to this version. Review such rules and change the value to a plain number (1000).
• Plauti Assign no longer allows creating an Assignee record without a linked User. If you have integrations that insert Assignee records without a User, adjust those integrations before updating, since such Assignees will now be rejected upon creation. Furthermore, update existing Assignees to have a User linked.
• If you are updating from version 11.19 or earlier, make sure to follow the Update instructions for earlier versions as well! See Upgrading from Version 11.19 or earlier to the latest version‍.

New

• Assignment - Set up Processing Rules to automatically trigger assignment when a record is created with specific fields filled in, or when those fields are updated. This means triggering Assign with a Flow upon record update is not needed anymore.

Improved

• Assignee Summary - Frozen Salesforce users now have a "Frozen SF" status, separate from users who are inactive in Salesforce.
• Assignees - Frozen Salesforce users can no longer be added as assignees.
• Match Groups - Create list views for the Match Group overview. Filter records, choose which columns are visible, and save views for reuse.
• Match Rules - GREATERTHAN and LESSTHAN operators now respect decimals and negative numbers (for example 1.9 is greater than 1.5, and -5 is less than 0) instead of truncating to whole numbers.
• Match Rules - When a GREATERTHAN or LESSTHAN value cannot be read as a number, the routing log now explains which value (rule value, field value, or both) was not numeric.
• Queue Order – Choose the order in which queued records are processed for each object separately. For example, process records based on a custom date/time field instead of the date they were created. When left empty, records are processed by created date and the globally set Sort Order, as before.

Classes added

If you are not using the Plauti Assign permission sets, add the following classes to the applicable Admin permission sets:

• srrDynamicQueryService
• srrFilterBuilder
• srrListViewController
• srrListViewRepository
• srrListViewService
• srrAssignmentOrderComparator
• srrObjectConfigRepository
• srrProcessingRuleController
• srrProcessingRuleEvaluator
• srrProcessingRuleOperatorService

If you are not using the Plauti Assign permission sets, add the following class to the applicable Admin and User permission sets:

• srrProcessingRuleLogicValidator

Other Items added

If you are not using the Plauti Assign permission sets, add the following Object and Fields to the applicable Admin permission sets:
Object:

• srrListView__c

Fields:

• srrListView__c.Description__c
• srrListView__c.FilterCriteria__c
• srrListView__c.FilterLogic__c
• srrListView__c.ObjectType__c
• srrListView__c.SelectedFields__c
• srrListView__c.SortDirection__c
• srrListView__c.SortField__c
• srrListView__c.ViewName__c

Fixed

• Assignees - Assignees with an active status but no linked User were silently excluded from the assignment pool even though in Assign Setup they displayed as "Assignable." These are now shown with a "No User" status, and the queue reason names the cause.
• Assignment - Records are no longer routed to users whose Salesforce login is frozen, in both regular assignment and SLA reassignment.
• Assignment - Frozen users are no longer picked up as the existing owner when assigning to the owner of a matching duplicate record.
• Match Rules - A non-numeric GREATERTHAN or LESSTHAN value no longer aborts matching with an error; instead, the rule simply does not match.
• Reassignment - Reassignment on a missed SLA now writes to the Assignment Field configured on the Match Group instead of always writing to OwnerId. Furthermore, reassignment no longer fails on objects without an OwnerId field, such as Campaign Member.

Update Instructions

• If you are updating from version 11.19 or earlier, make sure to follow the Update instructions for earlier versions as well! See Upgrading from Version 11.19 or earlier to the latest version‍.

New

• Match Groups - Run a Health Check on your Match Groups to find irregularities such as fields used in Match Rules that have since been deleted.
• Permission Sets - Configure a Match Group Admin permission set to let your key users manage Match Group Settings, match rules, assignees, assignee rules, and linked capacity models/SLAs without access to org-wide Assign settings.
• SLA - Configure Hours of Operation for an SLA so that the SLA timer only runs during the specified hours, based on the assignee's time zone.

Improved

• Assignees - Add working hours for all Assignees of a User in one go.
• Assignees - When a User is deactivated in Salesforce, their Assignee records are removed, so that Match Groups only reflect active users. Note that already assigned records do not get unassigned.
• Assignees - When creating a new Assignee, only active users can be selected.
• Assigning - The Routing Log now captures field values for cross-object lookup rules where the matched field is on the related record.
• Assigning - 'Update Other Fields on Assignment' now supports formulas, for example {NumberOfAssignments}+1. Any errors are logged in the Assignment Notes field.
• Dynamic Assignees - Add Dynamic Assignees to Match Groups based on their Permission Set or Permission Set Group. This facilitates the change Salesforce is making, shifting from profiles to permission sets.
• Dynamic Assignees - Frozen users are now excluded when resolving and counting users for dynamic assignment (inactive users were already excluded).
• Dynamic Assignees - If for some reason the hourly scheduled job for syncing dynamic assignees has stopped running or does not exist anymore, reschedule it with the Schedule Assignee Sync Job option in Assign Setup > Jobs & Maintenance. The job will start again within the hour.
• General - If your org's data storage is near or over its limit, a banner will warn you about this on Plauti’s Setup pages. This way it’s clear right away that any saving failures in the app are caused by a full org.
• Match Groups - Paused Match Groups now stay active. Matched records stay queued there until the pause ends. This makes pausing different from deactivating a Match Group, where matched records are diverted instead.
• Match Rules - Search for fields in the match rule configuration dropdown by label name or API name.
• Match Rules - The EQUALS operator now compares numeric fields by value, so a record value of 1.0 correctly matches a rule value of 1. Text fields are unaffected and continue to match exactly.
• Match Rules - When configuring Match Rules, cross-object fields are now clearly indicated as such so you know you can select more fields there.
• Setup Home - The Assign Setup Home page now displays more information about your Plauti Assign configuration, such as the Global Pause Assignment status including duration, and the number of active Match Groups.

Classes added

If you are not using the Plauti Assign permission sets, add the following classes to the applicable Admin profiles:

• srrFieldDescribeService
• srrILicenseRepository
• srrLicenseRepository
• srrMatchRuleHealthCheckController
• srrPackageLicenseDTO
• srrUserPackageLicenseDTO

If you are not using the Plauti Assign permission sets, add the following classes to the applicable Admin and User profiles:

• srrAccessService
• srrFormulaEvaluator
• srrMatchRuleFieldValidator

Other Items added

If you are not using the Plauti Assign permission sets, add the following fields to the applicable Admin profiles:

• MatchGroup__c.Invalid_Fields__c
• MatchGroup__c.Last_Health_Check__c
• SLA__c.Hours_Of_Operation_End__c
• SLA__c.Hours_Of_Operation_Start__c

If you are not using the Plauti Assign permission sets, add the following fields to the applicable Admin and User profiles:

• MatchLog__c.Assignment_Notes__c

Fixed

• Assigning - Load Balanced Assignment now respects the configured capacity threshold again.
• Dynamic Assignees - Reapplying the Assignee Rules now automatically re-grants licenses to eligible users again, given that licenses are available.
• Dynamic Assignees - Synchronization no longer stops when a user's Plauti Assign license cannot be released. Assignee updates now complete as usual. Furthermore the Administrator is now notified about the affected user.
• Dynamic Assignees - Users who already hold a license are no longer blocked from a new Match Group when your Org has run out of available licenses for Assign.
• Error Handling - Routing and Configuration errors are now displayed in the Routing Audit Log. Furthermore, when an error notification email cannot be sent, this will not break matching anymore.
• General - Lookup fields that are polymorphic, e.g. the content can refer to a Group or a User, are now handled correctly again when creating or editing records.
• Match Groups - Creating and editing Match Groups now works correctly again in Education Cloud.
• Match Groups - Custom fields are now visible and editable again.
• Match Groups - Setting names on the Match Group Settings tab are now always displayed properly right away.
• Metrics Dashboard - Reports no longer count Match Groups that overflowed to another Match Group as matching.

Update Instructions

• If you are updating from version 11.19 or earlier, make sure to follow the Update instructions for earlier versions as well! See Upgrading from Version 11.19 or earlier to the latest version‍.

Improved

• API - All of Plauti Assign’s triggers and Apex Classes have been updated to API version 66.0.
• Assign Setup - Quickly switch between Setup pages of all of Plauti’s Apps, and find out more about the ones you aren't using yet.
• Assignee Summary - When viewing ‘By User’, open the Assignee Record right from the Assignee Summary instead of first opening the Match Group.
• Dynamic Assignees - From now on, the settings of Dynamic Assignees will not be overwritten anymore with the default Assignee Settings the next time the Dynamic Assignee Rules and Settings are applied.
• General - Various small user interface improvements.
• Match Groups - When cloning a Match Group, links to SLAs and Capacity Models are no longer copied along. This provides more configuration control, and prevents unintended SLA or capacity inheritance. After cloning, manually add SLAs and Capacity Models to the new Match Group if needed.
• SLAs and Capacity Models - Cloning an SLA or Capacity Model is possible again. After cloning, the new SLA or Capacity Model is not yet linked to any Match Group.

Classes added

If you are not using the Plauti Assign permission sets, add the following classes to the applicable Admin profiles:

• srrMatchGroupEvaluationRepository

Other Items added

If you are not using the Plauti Assign permission sets, add the following Object and Fields to the applicable Admin profiles:
Object:

• srrMatchGroupCandidate__c
  Fields:
• Configuration_Values__c
• Hash__c
• JSONBlob__c

Fixed

• Assignee Rules - Currency fields can be fully used again in Assignee Rules.
• Pause Assignment - When a Match Group is paused, incoming records are now assigned to the Queue User again, instead of staying with the creator of the record, until regular assignment is resumed.
• SLAs and Capacity Models - Boolean fields (checkboxes) set to EQUAL TO = FALSE in SLA or Capacity Model criteria would result in an error.

Update Instructions

• For all versions:
  In Salesforce Setup:
  On the Plauti Assign AssigneeRule (leadassist__AssigneeRule__c) object, add the following picklist value to the 'Operator' field:
  INCLUDES
  On the Plauti Assign MatchLog (leadassist__MatchLog__c) object, add the following picklist value to the 'Outcome' field:
  OVERFLOW
• If you are updating from version 11.19 or earlier, make sure to follow the Update instructions for earlier versions as well! See Upgrading from Version 11.19 or earlier to the latest version‍.

New

• General - URLs of pages in Plauti Assign now reflect the current state in more detail, making it easier to return to specific pages. Copy the URL of a page and share or bookmark it.
• Routing Log - The new Routing Log provides a centralized view of all assignment activities across your organization. View the Routing Log overview from the Assign Routing Log tab, or access routing history on each Match Group. Click a record name to view extensive log information.
  This first iteration starts with the basics; in following releases more features will be added.
  Note that the Routing Log tab only displays routing information from the time of update onward. Earlier info is still available on the MatchLogs tab.

Improved

• Assignees - Update working hours across multiple Match Groups in bulk. This is particularly useful if your users are Assignees in several Match Groups.
• Assignees - On the Assignee Summary tab, activate or deactivate Assignees across multiple Match Groups in one go.
• Assignees - The last Assignee features, such as availability statuses "Out of Office" and "Calendar Busy", and the Working Hours select list to quickly set a different working hour schedule for an Assignee, have been moved to the Assignee Summary tab.
• Dynamic Assignee Rules - A new ‘Includes’ operator is available for matching users based on values within multi-select picklist fields. Note that when inverted, so “NOT Includes”, it does not find empty values.
  To use this operator, first add it to the 'Operator' field on the Plauti Assign AssigneeRule object. See the Update Instructions above.
• SLA Reassignment - Prevent records from being reassigned to a user who previously missed the SLA for the record, improving accountability and response times. Skip only the initial Assignee or all previous Assignees.
• SLA Reassignment - Set a limit on how many times a record is reassigned when an SLA is missed. Assign records that reached the reassignment limit to a specified ‘SLA User’, or apply the Routing Plugin to decide the next course of action; see below.
• SLA-based Actions - The Routing Plugin can now react when a record reaches its SLA reassignment limit. Use the ‘ASSIGNMENTSLAMAXREASSIGNMENT’ plugin action for example to assign a record to a different Match Group after a certain number of reassignments. Read more here.

Items added

If you are not using the Plauti Assign permission sets, add access to the following Tab to the applicable Admin profiles:

• Assign Routing Log

Fixed

• Dynamic Assignee Rules - Boolean fields are handled correctly again when configuring dynamic assignee rules.
• Match Rules - Text Areas (255 characters) can be used again when configuring Match Rules.

Update Instructions

If you are updating from version 11.19 or earlier, make sure to follow the Post-Update instructions as well! See Upgrading from Version 11.19 or earlier to the latest version‍.

Fixed

• Capacity Models – In some cases, newly added criteria in Capacity Models were displayed in an unexpected order.

Update Instructions

If you are updating from version 11.19 or earlier, make sure to follow the Post-Update instructions as well! See Upgrading from Version 11.19 or earlier to the latest version‍.

Improved

• Licenses - See your license use (currently in use and total available) on the Home page of Assign Setup.
• Setup - All settings have now been moved to the Assign Setup tab, and the old Setup and Status tab is no longer supported.
  Can’t find the Assign Setup tab? Edit your Navigation Bar to add it or move it into view.
• Setup - Creating rules such as Match Rules and Dynamic Assignee Rules, and their rule logic, has been improved.

Bugfixes

• Capacity Models - In some cases, a model with multiple rules could be saved without rule logic, rendering the model invalid.

Update Instructions

If you are updating from version 11.19 or earlier, make sure to follow the Post-Update instructions as well! See Upgrading from Version 11.19 or earlier to the latest version‍.

New

• Assignment - Temporarily pause the assignment of records by one or more MatchGroups with the new Pause Assignment feature. During an assignment pause, records that match a paused MatchGroup will temporarily be put on hold or forwarded to the next group, until the end date is reached. Use this feature for example during company holidays.
  Schedule a pause to start and stop at a future date, or start it right away. Start and end Assignment Pause per MatchGroup, or for all MatchGroups in one go. Read more here.

Improved

• Assignee Rules - If an Assignee Rule finds more unlicensed users than you have seats available, Plauti Assign fills up all available seats. Previously, the remaining users were still added, but as unlicensed Assignees. From now on, users who cannot get a license are left out of the Match Group. When more licenses become available, the users are added as Assignees the next time the Assignee Rules are applied (manually or automatically).
• Assignees - Get a clear overview of your Assignees' configurations with the new Assignee design. Edit the Assignee Settings and Working Hours all in one place.
• Assign Setup - Settings that previously needed to be set up via Salesforce Setup > Custom Metadata Type, can now be configured directly in Plauti Assign, on the Assign Setup tab.
  Can’t find the Assign Setup tab? Edit your Navigation Bar to add it or move it into view.
• Out of Office - Round Robin assignment now takes the end date of Out-of-Office (OOO) settings into consideration, as well as the user’s time zone. This way a user can be assigned records as soon as they are available again.

Classes added

If you are not using the Plauti Assign permission sets, add the following classes to the applicable Admin profiles:

• srrAssignmentSuspender
• srrGenericStorageRepository
• srrInAppNotification
• srrInAppNotificationController
• srrInAppNotificationRepository
• srrInAppNotificationScheduler
• srrInAppNotificationService
• srrMutexService

Other items added

If you are not using the Plauti Assign permission sets, add access to the following Object to the applicable Admin profiles:

• Plauti Assign Generic Storage (srrGenericStorage__c)

Update Instructions

If you are updating from version 11.19 or earlier, make sure to follow the Post-Update instructions as well! See Upgrading from Version 11.19 or earlier to the latest version‍.

New

• Plauti Restore - Undo Merges and other field and record changes with the new Plauti Restore solution. Keep track of changes: merges, inserts, updates and deletions, on Objects and Fields you define. Restore changes including related data to revert accidental modifications. Restore from the main Changes overview, or from a custom record tab. Read more here, or watch the video.

Improved

• Assign Setup - The layout of the different Plauti Assign configuration pages has been improved with an intuitive user interface. Find the Match Groups, Capacity Models, and other configuration sections all together on the new Assign Setup tab. For now the configuration sections are visible in the old and new spots, but in a later version the Assign Setup tab will be the single Assign configuration home.

Other

• Flow Actions - From Salesforce’s Winter ‘26 release onwards, flow apex actions in record-triggered flows cannot be used anymore in an immediate path (synchronous path or non-scheduled path). To prevent your flows with Plauti apex actions from failing, change the Transaction Control settings of your existing record-triggered flows to 'Always continue in current transaction’.
  Note that screen flows and auto-launched flows are not affected.
  Read more about updating your flows here.

Classes added

If you are not using the Plauti Assign permission sets, add the following classes to the applicable Admin profiles:

• srrAssigneeController
• srrCapacityModelController
• srrMatchGroupController
• srrMatchLogController
• srrServiceLevelAgreementController
• srrMatchRuleController
• srrSettings
• srrSetupController

Other items added

If you are not using the Plauti Assign permission sets, add access to the following Tab to the applicable Admin profiles:

• AssignSetup

Update Instructions

If you are updating from version 11.19 or earlier, make sure to follow the Post-Update instructions as well! See Upgrading from Version 11.19 or earlier to the latest version‍.

New

• Export Data - A new Data Flow is available: Export Data. Next to importing data into your Salesforce Org, you can now export data from any Object as well. Export a CSV file with data from the entire object or a subset of records, from selected fields including parent fields. Run the Export Data Flow in Plauti Cloud, or in the new Plauti Desktop or Plauti Server apps that run on your local machine instead of in the cloud. Read more here.
• General - Labels have been updated to reflect the new naming. Find the matchgroups in Assign MatchGroups, the matchlogs in Assign MatchLogs, etc. Read more about the new naming in this blog, and find a list of all new names in SRR and Plauti Assign Old and New Names

Improved

• Assignment - A plugin option has been added for overwriting the list of assignees available for assignment with a custom assignee list. This would for example enable future availability assignment based on your own business rules. Don’t hesitate to contact your account manager for more information!
• Licenses - If an Assignee Rule adds more unlicensed users than you have seats available, Plauti Assign will now fill up all available seats, and notify the Administrator about the users that could not be assigned a license.

Fixed

• MatchGroup - When cloning a MatchGroup, the Object settings in the “This MatchGroup Assigns…” section are now copied along again.

Update Instructions

If you are updating from version 11.19 or earlier, make sure to follow the Post-Update instructions as well! See Upgrading to Version 11.20 of Plauti Assign‍.

Improved

• A number of performance improvements were made.

Update Instructions

If you are updating from version 11.19 or earlier, make sure to follow the Post-Update instructions as well! See Upgrading to Version 11.20 of Plauti Assign‍.

New

• Assignment - Route records based on the proficiency of users in specific skills, to ensure that each record is assigned to a user who has appropriate expertise to handle the record. Update and manage User Skills dynamically, so that routing rules remain effective as a user’s skills evolve. Read more here.
• Assignment - Use Overflow Logic to manage cases where all members of a MatchGroup are unavailable, or when specific MatchRules inhibit assignment. Overflow Logic will automatically move records to the next suitable MatchGroup, ensuring records are consistently assigned even when the initial rotation encounters limits. Read more here.
• MatchGroups - Assignees can now be added to MatchGroups fully automatically. With the AssigneeRules introduced in the previous version, and Assignee Synchronization enabled, a MatchGroup’s Assignees are updated every hour. Read more here.

Improved

• MatchGroups - Assignees that did not get a Dynamic Assignment status yet after updating to the previous version will now get status 'Manual'. Of course you can always change it to 'Dynamic'. Read more here.

Classes added

If you are not using the SRR permission sets, add the following classes to the applicable profiles:

• srrAssigneeSyncBatchJob
• srrJobScheduler
• srrSkillsController

Other items added

If you are not using the SRR permission sets, add the following items to the applicable profiles:
Objects:

• Skill__c
• UserSkill__c
  Fields:
• AssigneeSettings__c.Send_MobileAssign_Notifications__c
• AssigneeSettings__c.Send_SMS_Notifications__c
• MatchGroup__c.Assignee_Synchronization__c
• MatchGroup__c.Overflow__c
• UserSkill__c.Skill__c
• UserSkill__c.User__c
  Tabs:
• UserSkill__c
  LWC components:
• srrSetupSkills

Fixed

• General - When using other Objects than the five default Objects in Plauti Assign (SRR), an error occurred.

New

Plauti is rebranding! Super Round Robin has been renamed to Plauti Assign, and can be found under that name in the Salesforce App Launcher.
For now both apps can still be used, but later this year only the new Plauti Assign app will be available.So add it to your favorites! Read More.

Items added

• Add the new Plauti Assign app to your list of favorite Salesforce apps to use instead of the SuperRoundRobin app.
• If you are not using the SRR Admin permission set, assign the following app to the applicable profiles or permission sets for users that need Admin access:
  Plauti Assign (leadassist__plauti_assign)
  if you currently have the Super Round Robin (leadassist__SRR) assigned there.

Update Instructions

• Add new picklist values Distance and Plugin to the Operational Mode field on the MatchGroup object. These values will be used to set the new operational modes in MatchGroups. Read more in Upgrading to Version 11.20 of Plauti Assign‍.

New

• Assignment - Assign records based on location instead of in a round-robin fashion, with the new operational mode "Distance”. When latitude and longitude of records and assignees are filled in, a record will be assigned to the closest assignee available. Read more in Operational Mode: Distance.
• Matching and Assigning - Define more extensive matching and assignment rules with the new operational mode “Plugin”. Via an Apex Class, implement your own logic for records to be matched with a MatchGroup and assigned to an Assignee. Read more in Operational Mode: Plugin.
• MatchGroups - Set up AssigneeRules to dynamically and automatically add Assignees to a MatchGroup. Add multiple Assignees to a MatchGroup with one click, based on specific criteria. Assignees that do not match the set AssigneeRules can still be added manually. Read more in AssigneeRules‍.
• Reports - Keep track of how you’re doing on the new Super Round Robin dashboard, with reports such as “SLAs Met: Average Time per Assignee”, or “Record Distribution per MatchGroup per Week”. Read more in Logs and Reports.

Improved

• MatchGroups - Cloning a MatchGroup in order to create a similar one has been improved. MatchGroup features such as MatchRules and AssigneeRules are now cloned as well, meaning you only need to make minor adjustments to set up the new MatchGroup.

Classes Added

If you are not using the SRR permission sets, add the following classes to the applicable profiles:

• CaseAssignmentQueueable
• MatchGroupOperationalModeConfig
• QueueableAssignment
• srrAssigneeRepository
• srrAssigneeService
• SRRException
• srrPlugin
• srrPluginInterface
• srrPluginModel

Other Items Added

If you are not using the SRR Admin and SRR Users permission sets, add the following objects to the applicable profiles:

• AssigneeRuleField
• AssigneeRules
• AssigneeSettings
• Assignee

Fixed

• Capping - Assigning from a queue sometimes resulted in assignments that exceeded users' capacities.
• Capping - When multiple MatchGroups shared a Capacity Model, users that were in two or more of these MatchGroups could get records assigned over their capacity.
• MatchGroups - Custom MatchRule Logic that accidentally contained an extra space character could cause records not to be routed, even though they matched the MatchRules.
• MatchGroups - To set Custom MatchRule Logic for a MatchGroup, there must be at least three MatchRules. If one matchrule is removed, the MatchRule Logic will automatically revert to “OR". Previously, this was not always reflected in the interface, which could cause confusion.

Improved

• General - Next to email and SMS notifications, Assignees can now also receive mobile and desktop push notifications when they get a record assigned. Read more here‍.

Fields Added

If you are not using the SRR Admin and SRR Users permission sets, add the following fields to the applicable profiles:
Read and Write access required for fields

• Assignee__c.Send_DesktopAssign_Notifications__c
• Assignee__c.Send_MobileAssign_Notifications__c
  Read access required for fields
• MatchLog__c.DesktopAssignNotification_Sent__c
• MatchLog__c.MobileAssignNotification_Sent__c