- Resolved an issue where default deployed objects did not have the correct buttons and text rendered.
- Resolved an issue where errors were encountered when sending out batch completion notification emails.
- Resolved an issue where users would not be able to select a target field if the target object had a large amount of fields.
- Resolved an issue where parent filters were not updating matching records correctly.
- Resolved an issue where preview rollups only showed results for one record if the preview record contained a duplicate name.
- Resolved an issue where retry rollups would submit jobs for “Unspecified Object.”
- Resolved an issue where the manage realtime button would display for non-triggerable source objects on the Rollup Run page.
- Resolved an issue where a rollup would not be removed from a rollup group if it was not on the first paginated page of available rollups.
- Resolved an issue where a “type cannot be cast to class” error would sometimes occur for rollups with formula source fields.
- Resolved an issue where saving a rollup schedule would cause an error if the estimated time did not contain “hour” or “minute”.
- Resolved an issue where New Line and Double New Line delimiters were able to be selected for target fields that did not support New Lines.
- Resolved an issue with job pagination not working on the schedule management page.
- Resolved an issue where clicking “Enable Realtime” on a Foreign Key rollup would direct the user to the incorrect object.
- Resolved an issue that prevented filters to be saved within namespaces containing “__r”.
- Resolved an issue where filters were unable to be saved for existing filters.
- Resolved an issue when saving a job that had no matching parent records to run for.
- Resolved an issue where selecting all rollups within a group to be active caused incorrect data to be formatted on the rollups.
- Resolved an issue where saving a rollup schedule would not display an error message if the schedule was invalid.
- Resolved an issue where the estimated run time for a rollup would not be displayed if there were no matching records for the rollup to run on.
- Resolved an issue where changing the source object on a rollup would not update the source field correctly on the all settings page.
- Resolved an issue where users were unable to create target fields if they first entered an incorrect field label and then changed it to a correct label.
- Adjusted permissions and security settings to avoid users running into the known issue:
- “SObject row was retrieved via SOQL without querying the requested field: rh2__RH_job__c.rh2__ParentFilter__c”
-
Resolved an issue where clicking save repeatedly on a rollup would cause multiple rollups to get created.
-
Resolved an issue that prevented rollups from saving when trying to select certain polymorphic foreign key source fields.
-
Resolved an issue where a foreign key multi-currency rollup would not retrieve a selected date field from the correct object and would fail to process.
-
Resolved an issue where the system audit fields for a rollup were incorrectly labeled.
- Resolved an issue where previewing a rollup with the same target and source object would result in an error.
- Resolved an issue where lead target rollups and scheduled rollups would sometimes encounter an ‘Unexpected token 2’ error when processing.
- Resolved issues where the save button for a rollup would not render at the correct configuration step.
- Resolved an issue where cloning a rollup for source objects not on the first paginated page resulted in errors when trying to change the source field or save the cloned rollup.
- Resolved an issue where previewing rollups for objects without list views would produce an error.
- Resolved an issue where manual runs with multiple sorts set would not rollup the correct value.
- Resolved an issue in Government Cloud sandboxes where queue records would not get scheduled to run immediately.
- Resolved an issue where the help text for a target field would stretch out the Select Target field page.
- Resolved an issue when trying to deploy triggers for objects that end with ‘Exception’.
- Resolved an issue where saving inline edit text with a different case would not save the changes.
- Resolved an issue in multi-currency environments where running a rollup would cause an error for target objects that did not have the ‘CurrencyIsoCode’ field available.
- Resolved an issue where the record scope monitor would cause errors for objects with very long names.