Difference between revisions of "Salesforce:Build History"

From Melissa Data Wiki
Jump to navigation Jump to search
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[Clean Suite for CRM:Salesforce|← Clean Suite for CRM:Salesforce]]
[[Clean Suite for CRM:Salesforce|← Clean Suite for CRM:Salesforce]]
{{CustomTOC}}
{{CustomTOC}}
Please see the Melissa Product Release Notes for updated Build History moving forward:
*https://releasenotes.melissa.com/enterprise/clean-suite-crm-salesforce/
==Build 3.2.2.136==
''Released February 2023''
''Formerly Build 2.136''
<p class="sectionhead">Added</p>
*Clean Suite Batch Processing page - New visual interface for batch processing added to the Clean Suite app. Users can now start batch jobs from an easy to use and intuitive interface.
*Clean Suite Batch Processing - Added "ProcessAll" logic to Clean Suite Batch jobs. Now users can process only records that have not been previously processed. This will allow users with no/minimum SOQL experience to only process the records they want to
<p class="sectionhead">Changed</p>
*Base Engine - All engine based classes have been updated to SFAPI v56 - This change adds compatibility with new salesforce objects released
<p class="sectionhead">Deprecated</p>
*None
<p class="sectionhead">Removed</p>
*Clean Suite Package - Removed sf_chattr_apps pre-requisite - This package was needed in older versions of lightning for compatibility with our on-page Express Entry Lightning component. Package is no longer required so removed from pre-requisite package requirements. This change allows users a more streamlined and easy installation process
<p class="sectionhead">Fixed</p>
*Clean Suite Engine - Fixed bug where Visualforce exceptions were being thrown in a Lightning context.
*Clean Suite Batch - Fixed bug where empty records could be passed causing an exception to be thrown and entire job would cancel
*Global Email Batch - Fixed bug where only partial datasets were being passed for validation. Now all records passed to batch process should validate fully
*Global Address Batch - Fixed duplicate bug where certain results were being duplicated causing multiple upserts to the same record. This fix will increase Global Addr Batch performance.
*Personator Result Object - Fixed metadata length for fields overflows
*Global Email Result Object - Fixed bug allowing overflows of Global Email result fields. This rarely occurred on extremely long mailing addresses associated with certain domain names. Now all fields will truncate record values longer than 255 characters
<p class="sectionhead">Security</p>
*None
==Build 2.115==
''Released December 2021''
*Added suite dropdown selector to Express Entry lightning component. Previously all suites were returned as individual results. Now they will return in a dropdown box when present in the result. Users have the option to include the suite in the address field or map it separately.
*Added County + Geodata to Express Entry lightning component. Users can enable and disable the display of these columns on the panel.
*Added functionality to auto-disable actions and outputs from the settings menu that users do not subscribe to. This will prevent users from receiving empty responses back from the webserver.
==Build 2.112==
''Released October 2021''
*Fixed bug with query limit overflow in CleanSuite batch mode. Batch calls should now only make 3-4 queries per batch.
*Increased Field Size of <code>MD_personatorResult__c.CompanyName__c</code> and <code>MD_personatorResult__c.AddressDeliveryInstallation__c</code>.
*Added additional unit tests to increase code coverage
==Build 2.109==
''Released August 2021''
*Added Businesscoder Output mapping support for Phone field
*Added Businesscoder Output mapping support for CurrentCompanyName field
*Added Businesscoder Output result support for CurrentCompanyName field
*Added GlobalAddressVerification Input support for AddressLine2 field
*Fixed bug preventing PostalCode output being blocked in some cases for GlobalAddressVerification batch processing
*Fixed bug preventing GlobalEmail batch processing being blocked
==Build 2.104==
''Released July 2021''
*Added support for clean suite batch processing.  This feature will be expanded in the future to allow access for batch processing using all of our supported webservices including: Personator, Global Address, Global Email, Global Phone, and more…
==Build 2.103==
''Released June 2021''
*Fixed bug in Businesscoder mappings that was causing NAICS code outputs to overwrite eachother. Mapping these fields should now be working as expected.
==Build 2.102==
''Released April 2021''
*Fixed a bug that prevented Global Address Batch mode from updating results.
==Build 2.101==
''Released March 2021''
<p class="sectionhead">Personator</p>
:*Implemented "update settings" panel for Lightning calls. If "apply filters to clean suite calls" is checked, the engine will now apply a pattern to result codes and prevent updates to fields that do not match the pattern. For example, if an Address pattern is set to <code>AS0[123]</code> and the result code does not match this pattern, the address fields will not be updated. This change brings the expected behavior in line with documentation.
<p class="sectionhead">Administration Panel</p>
:*Implemented "Apply filters to clean suite calls" checkbox, to allow users to keep existing behavior or use filter logic.
<p class="sectionhead">Global Email</p>
:*Added <code>DeliverabilityConfidenceScore</code> to email output mapping.
<p class="sectionhead">Global Phone</p>
:*Added <code>County</code> and <code>CountryOfOrigin</code> to phone input mapping. These fields allow further control over formatting of phone numbers depending on the origin.
==Build 2.99==
==Build 2.99==
''Released February 2021''
''Released February 2021''

Latest revision as of 01:02, 8 March 2023

← Clean Suite for CRM:Salesforce


Please see the Melissa Product Release Notes for updated Build History moving forward:

Build 3.2.2.136

Released February 2023

Formerly Build 2.136

Added

  • Clean Suite Batch Processing page - New visual interface for batch processing added to the Clean Suite app. Users can now start batch jobs from an easy to use and intuitive interface.
  • Clean Suite Batch Processing - Added "ProcessAll" logic to Clean Suite Batch jobs. Now users can process only records that have not been previously processed. This will allow users with no/minimum SOQL experience to only process the records they want to

Changed

  • Base Engine - All engine based classes have been updated to SFAPI v56 - This change adds compatibility with new salesforce objects released

Deprecated

  • None

Removed

  • Clean Suite Package - Removed sf_chattr_apps pre-requisite - This package was needed in older versions of lightning for compatibility with our on-page Express Entry Lightning component. Package is no longer required so removed from pre-requisite package requirements. This change allows users a more streamlined and easy installation process

Fixed

  • Clean Suite Engine - Fixed bug where Visualforce exceptions were being thrown in a Lightning context.
  • Clean Suite Batch - Fixed bug where empty records could be passed causing an exception to be thrown and entire job would cancel
  • Global Email Batch - Fixed bug where only partial datasets were being passed for validation. Now all records passed to batch process should validate fully
  • Global Address Batch - Fixed duplicate bug where certain results were being duplicated causing multiple upserts to the same record. This fix will increase Global Addr Batch performance.
  • Personator Result Object - Fixed metadata length for fields overflows
  • Global Email Result Object - Fixed bug allowing overflows of Global Email result fields. This rarely occurred on extremely long mailing addresses associated with certain domain names. Now all fields will truncate record values longer than 255 characters

Security

  • None


Build 2.115

Released December 2021

  • Added suite dropdown selector to Express Entry lightning component. Previously all suites were returned as individual results. Now they will return in a dropdown box when present in the result. Users have the option to include the suite in the address field or map it separately.
  • Added County + Geodata to Express Entry lightning component. Users can enable and disable the display of these columns on the panel.
  • Added functionality to auto-disable actions and outputs from the settings menu that users do not subscribe to. This will prevent users from receiving empty responses back from the webserver.


Build 2.112

Released October 2021

  • Fixed bug with query limit overflow in CleanSuite batch mode. Batch calls should now only make 3-4 queries per batch.
  • Increased Field Size of MD_personatorResult__c.CompanyName__c and MD_personatorResult__c.AddressDeliveryInstallation__c.
  • Added additional unit tests to increase code coverage


Build 2.109

Released August 2021

  • Added Businesscoder Output mapping support for Phone field
  • Added Businesscoder Output mapping support for CurrentCompanyName field
  • Added Businesscoder Output result support for CurrentCompanyName field
  • Added GlobalAddressVerification Input support for AddressLine2 field
  • Fixed bug preventing PostalCode output being blocked in some cases for GlobalAddressVerification batch processing
  • Fixed bug preventing GlobalEmail batch processing being blocked


Build 2.104

Released July 2021

  • Added support for clean suite batch processing. This feature will be expanded in the future to allow access for batch processing using all of our supported webservices including: Personator, Global Address, Global Email, Global Phone, and more…


Build 2.103

Released June 2021

  • Fixed bug in Businesscoder mappings that was causing NAICS code outputs to overwrite eachother. Mapping these fields should now be working as expected.


Build 2.102

Released April 2021

  • Fixed a bug that prevented Global Address Batch mode from updating results.


Build 2.101

Released March 2021

Personator

  • Implemented "update settings" panel for Lightning calls. If "apply filters to clean suite calls" is checked, the engine will now apply a pattern to result codes and prevent updates to fields that do not match the pattern. For example, if an Address pattern is set to AS0[123] and the result code does not match this pattern, the address fields will not be updated. This change brings the expected behavior in line with documentation.

Administration Panel

  • Implemented "Apply filters to clean suite calls" checkbox, to allow users to keep existing behavior or use filter logic.

Global Email

  • Added DeliverabilityConfidenceScore to email output mapping.

Global Phone

  • Added County and CountryOfOrigin to phone input mapping. These fields allow further control over formatting of phone numbers depending on the origin.


Build 2.99

Released February 2021

  • Fixed bug that would cause Global Phone Results to not populate for new installs.
  • Upgraded Global Email component to use V4 webservice. Previously was running V3. V4 webservice adds additional response fields as well as improved verification speed and accuracy.


Build 2.98

Released January 2021

  • Fixed issue for credit based users using GlobalPhoneWSExt throwing error when using multiple mappings.
  • Fixes for security risks and vulnerabilities.


Build 2.94

Released May 2020

  • Fixed permission issues for Clean Suite response objects. New installations would have to manually grant access to some of these objects. Now it is part of our Clean Suite rule package.


Build 2.93

Released May 2020

  • Change DML rule handling for upsert commands. Now the engine will try to upsert. If that fails due to a DML violation the engine will now use an insert with DML allowsave. This change should be mostly transparent and have no effect on 99% of our customers. This change will only take effect if you are using DML rules such as Match rules and Duplicate rules.
  • Fix for MD_PropertyV4WSExt bug where records with no FIPS were throwing an exception and forcing abort of result update. Records should now update as expected
  • Fix for salesforce classic bug causing overflow of personator responses into matchup batch results


Build 2.90

Released February 2020

  • Fixed loading error in VisualForce Express Entry


Build 2.89.0

Released November 2019

Compatibility Summary

Clean Suite for Salesforce is fully compatible with Lightning and Salesforce Classic interfaces.

Clean Suite for Salesforce Component

Changes
  • Added Lightning Locker Service compatibility to Express Entry lightning component


Build 2.6.3

Released December 2015

  • Added ExpressEntry mobile support for Salesforce.
  • Allow user to process with geocoding up to street level, previously only appended lat/long geopoints (rooftop) was turned on.
  • Allow user to map in more fields to update directly to Salesforce records (demographics, census and county).
  • Workaround for 50k record limit when displaying result code stats.


Build 1.5

Released March 2015

  • Adds batch processing for Global Address Verification and Personator.
  • Notification messages now appear indiciating if a record was validated/standardized to help make sense of the result codes.
  • Improved Express Entry support.
    • Previous versions only supported Contact, Lead and Account Objects. Now Express Entry works within any Salesforce field/form.
Personator
  • Demographics
  • Long address format (Ct -> Court, etc.)


Build 1.3

Released October 2014

  • Adds support for additional Salesforce objects (leads & accounts) plus any custom object.
  • Adds support for Global Express Entry – providing address auto completion for over 240 countries & territories.


Build 1.0

Released September 2014

  • Initial Release