Group Assignment Resolved Defects

To view Release Notes, see Group Assignment Release Notes

VERSION 2206.11

BASE VERSION 2112.3

(CL-1511) Users were unable to migrate groups due to the error ‘Too many SOQL aggregate queries: 301’

BASE VERSION 2110.3

(CL-1353) Group Assignment migrations were incorrectly sending emails about successful migrations when the migration had not been successfully completed.

BASE VERSION 2102.10

(CL-1197) Some users were unable to access TargetX Builder if a custom object called Cohort__c had been created.
(CL-1227) When attempting to edit Group Assignments, some users would get a Heap Size too Large error.

BASE VERSION 2012.9

(CL-1151) Group Assignment was unable to use objects with an API name longer than 40 characters.

BASE VERSION 2011.1

(CL-785) Users attempting to migrate Group Assignment changes from Sandbox to Production received the error Apex Heap Size Error on Migration.

BASE VERSION 2010.2

(CL-916) Special Characters in Group Assignments were not displaying properly.

BASE VERSION 2003.4

(CL-551) Group Assignment criteria for number fields that contain 'blank' as criteria would cause an Invalid Decimal error when users Saved.

BASE VERSION 2002.4

(CL-503) Users were unable to publish or migrate Group Assignments.
(CL-728) Group Assignment Round Robin assignments were not running on newly created Community User Contact records.

BASE VERSION 17.40013

(RC-674, RC-684) Applicants received SOQL query errors when trying to submit an application.
(RC-681) Migrating Group Assignments was causing an Apex CPU Timeout error.

BASE VERSION 17.10002

Corrected an issue where groups created by Group Assignment weren't showing Assigned Staff.
Issue corrected where deleting assigned groups from the 'Members' section was throwing errors.

BASE VERSION 17.20029

Corrected an issue where users got an Apex CPU Timeout related to Base package with new group assignments.
An issue was occurring with the Group Assignment Builder when attempting to edit previously built assignments, that resulted in an "oops... something went wrong" error. This issue has been fixed and the error no longer occurs.
Corrected an issue that was causing users to receive a Too Many SOQL Queries error. TargetX Source to Master (Profile Builder) is causing too many SOQL Queries in conjunction with other items in the system.