Difference between revisions of "EN Connector Release notes"

From EN Salesforce Integration
Jump to: navigation, search
 
Line 1: Line 1:
 
'''Release notes for package 1.6_1'''
 
'''Release notes for package 1.6_1'''
  
Prior to this release, the connector has hardcoded references to the Toronto data centre's URL of 'https://e-activist.com'. With the addition of a the Dallas datacenter (https://us.e-activist.com), the package required updating to allow for the ability to select which data center to use, in the 'pulling' and 'pushing' of data.
+
Prior to this release, the connector had hardcoded references to the Toronto data centre's URL of 'https://e-activist.com'. With the addition of a the Dallas datacenter (https://us.e-activist.com), the package required updating to allow for the ability to select which data center to use, in the 'pulling' and 'pushing' of data.
  
 
Previously, 'Remote Site Settings' where employed but as of this release, the package now leverages Salesforce's native 'Named Credentials' API callouts.
 
Previously, 'Remote Site Settings' where employed but as of this release, the package now leverages Salesforce's native 'Named Credentials' API callouts.

Latest revision as of 08:58, 13 June 2019

Release notes for package 1.6_1

Prior to this release, the connector had hardcoded references to the Toronto data centre's URL of 'https://e-activist.com'. With the addition of a the Dallas datacenter (https://us.e-activist.com), the package required updating to allow for the ability to select which data center to use, in the 'pulling' and 'pushing' of data.

Previously, 'Remote Site Settings' where employed but as of this release, the package now leverages Salesforce's native 'Named Credentials' API callouts.

There is now a new textfield, on the Custom settings: Engaging Network Settings object, called 'Named Credentials; which allows for the specification of data center.

For clients on the Dallas data center, please use ENDC2 in this field.

Note : For clients who are on the Toronto data center, no changes are required.


Release notes for package 1.5.7_3

Minor update to improve debugging.

A customer ran into the following issue https://success.salesforce.com/issues_view?id=a1p30000000T3V2AAK, where a Local field and a field in the package were named the same.

The update to the debugging logs just helped in isolating why a certain error was being thrown. The solution transpired to be to delete the local field.

If currently on 1.5.7, then this upgrade is optional.


Release notes for package 1.5.7

The processing engine has been completely re-written to be more efficient and to add support for 'updating' of CampaignMembers (and other sObjects).

Additionally, as an admin you should no longer see an apex warning if multiple transactions are seen in a batch. This was initially by design but became cumbersome for admins on large days and is much improved.

For the update side of things, the engine has now been reworked in the following way :

The fields Lead > sfdc_lead_is__c, Contact > sfdc_contact_id__c, Account > sfdc_account_id__c, Campaign > sfdc_campaign_id__c, Campaign Member > sfdc_campaign_member_id__c

are now pre-defined 'id' fields for the main sObjects. If these are populated in the ENIR, the code will just use the respective ID to directly update the sObject. In cases where the Contact (or other sObject) has been removed, it would clear out the ID field and write to Error Details. This would then allow the ENIR to be re-processed on the next run.

On updating sObjects outside of the above, if there is a value in the ‘Import Record Field To Update’ then it uses that as the ID field (useful in custom object updating).

In summary, previously the code only relied on the Matching Rules/Deduplication rules for updates - now it uses both. If sfdc_contact_id__c is blank, it will try create a Contact and if a 'matching rule is triggered' - update. If sfdc_contact_id__c is populated - update would happen directly.


Release notes for package 1.5.6

Main items in release are improved 'batch processing' and the initial implementation of Engaging Networks Logs.

The batching work is for both the 'Campaign Member' sync push and Engaging Networks Import Records processing, through Engaging Networks Mapping.

There are now two new configurations added to the Custom settings: Engaging Network Settings object. Please be sure to set defaults for 'Push Batch Size' and 'Pull Batch Size'.

There is also the ability to override the default batch size on the Engaging Networks Mapping page itself.

Upon successful processing of an Engaging Networks Import Records, the Error Details field is now cleared. This makes is easier to see which ENIRs are having issue with being created.


Release notes for package 1.5.4

CSV Parsing issue fix, were a comma was seen as the last character in value


Release notes for package 1.5.3

Pull Query issues seen when complex filter logic was employed. The problem ended up being where field names that included numbers were used in the filter.


Release notes for package 1.5.2

Name prefix fix, which solved a certain SQL query mapping throwing EN_Connector__Pull_Process_Type__c on processing


Release notes for package 1.5.0 / 1

Updates to improve the Engaging Networks Mapping UI. ‘Pull from EN’ and ‘Push to Test’ are now hidden and ‘Pull from SF DB’ labelled to ‘Manually Process Mapping’

Fixed bug when 'Clone' was used on the Engaging Networks Mapping Page. Original mappings lost some of the filters - this is now resolved.

Link to Campaign Member by Lead ID. Previously the code would only look for a contact campaign member record. Now if SFDC Campaign ID and SFDC Lead ID is present, Campaign Member ID will be looked up as well.

Boolean Export Conversion fix : Previously a Null error was thrown when a Boolean field was selected to be exported to CSV

Added 'Export Field Update' mapping to the Push To EN options on Engaging Networks Mapping. Once a record is pushed to Engaging Networks, this rule allows the originating object to have a checkbox or date field updated.

Export Job Improvements to deal with higher numbers of objects. The tool now uses Batching to improve throughput to Engaging Networks.


Release notes for package 1.35.5

Re-packaged as Campaign Member ID and SFDC Campaign ID fields on the Engaging Networks Import Records object where not available to the Engaging Networks Mapping


Release notes for package 1.35.4

Master Contact Detail Issue : when the conversion process attempted to create objects with a Master/Detail relationship it failed but left Engaging Networks Import Records marked as processed.


Release notes for package 1.35.3

Added the ability to 'update' objects. Previously, create was only available but now the tool has been updated to leverage SF 'Duplicate Management' features as an update method

Enhanced the UI of the Engaging Networks Mapping tool to only show what is applicable, if 'Pull' or 'Push' is selected

Enhanced the current filter functionality on the Engaging Networks Mapping tool to allow users to combine multiple filters, using a combination of AND and OR selections. "Starts with" and "Contain" also been added.

Improvements to the External Segment CRM push tool. It now removes the assumption of wanting to push additional campaign and email template to EN and is now more flexible.

CampaignMember id is now written back to the Engaging Networks Import Records object, if SFDC Campaign ID and SFDC Contact ID are populated.

Fix for handling Booleans to checkboxes. Previously Boolean and 'True' was not correctly setting the checkbox.

A bug was found in CSV parsing if a comma was seen in a value field from EN. This has been resolved.

Tweaks to the 'Push to EN' tool, in order to increase load. (Note. The original release notes stated 'to now use SF batching for larger files'. This was incorrect and will be introduced in a subsequent release.)


Release notes for package 1.35.2

Updated a namespace issue on the Push process


Release notes for package 1.35

Fixed a Master Contact Detail Issue where objects failed to be created but left the EN Import Records marked as processed.

Added additional type casting support for fields being pushed to EN

Date fields will be converted to YYY-MM-DD

Numeric fields will be converted to decimal strings

Multi-Value fields will have the salesforce separator of a semi colon replaced with ~ (EN delimiter)


Release notes for package 1.34

CSV Support : In addition to some performance benefits, the big advantage of this enhancement is that it allows the connector to support much larger volumes due to the CSV file size and the move to using batch processing in the connector.

Error Handling – Missing Fields : Now if an export is sent from EN to SF and a column is included that is not mapped into the EN Import record an email is generated which then allows the administrator to map the field or mark it to be ignored

Error Handling – Web Service Error : If there is an error pushing data from SF to EN it used to fail silently. Now the error response from EN is trapped and stored and can be tracked back to the CSV file that caused the problem, making debugging a lot easier

One Off Pull From EN : This allows a user to open up a new VF page and specify a day, date range or time range (within limitations of the API) and pull those records through to SF as a one off

Support for Multiple EN Accounts : This allows SF to be connected to multiple EN Accounts to push and pull data

[CLEAR] Support : There is now a global option and an field by field override that will push the [CLEAR] keyword back to EN from SF if the value in SF is blank