What is installed

From EN Salesforce Integration
Jump to: navigation, search


EN Activities


En activities.png An optional custom object: For example, if you wanted to track ‘Email opens’, you could use this object to store the record and can be linked to a campaign or contact.

EN Actions


En actions.png An optional custom object: For example, if you wanted to track ‘Petitions’, you could use this object to store the record and can be linked to a campaign and/or contact.

Engaging Networks Import Records


Engaging networks import records.png Once the data is pulled from the Engaging Networks API via the APEX scheduler or through a manual pull, records will be held here until processed.

This a key object in how the connector works and each row of the 'transactional data' CSV file, is created as it's own object.

Engaging Networks Fields

Engaging networks fields.png Used by the staging object in conjunction with the mapping templates. This is for internal processing only and can be ignored for implementations.


Engaging Networks Mapping

Engaging networks mapping.png This is the key tool in creating the mapping rules in Salesforce. The mapping tool searches into the Engaging Networks Import Records table to find unprocessed records, which match the criteria entered as a ‘Pull filter’. The tool then generates the object (Contact/Account/Opportunity etc.) with the specified fields, defined on the mapping.

Engaging Networks Manual Pull

Engaging networks manual pull.png A tool to connect to Engaging Network’s export API web service and pull a specified timeframe of data. This tool is useful in either test phase or importing certain days of data, into the ‘Engaging Networks Import Records’ staging table.

Note that upon going live, the connector would run a scheduled APEX job to import records, daily into the account. Using this tool in conjunction with an already scheduled import would result in duplicate records. It is therefor important to specify the correct day/timeframe when importing into a ‘live account’.

Engaging Networks also imposes certain restrictions on how much data is made available to the export API. These are:

  • 32 days of data is callable
  • Calling ‘Todays’ data is only to be used in ‘test phases’, by using the HH:MM format.
  • As there is also a 2-hour delay in data being made available to this aggregated table, please wait a couple of hours before trying to call a test action that you have just made.

In a live scenario, the scheduled job pulls ‘yesterdays’ data.

Mapping Templates

Mapping templates.png This page holds a ‘configuration’ object, which the Engaging Networks Mapping tools use. The easiest way to explain this is through an example: if you added a custom field to the Opportunity object (like Source) – you would also need to update the Mapping Template, for Opportunity, to add it there as well. (This is covered further later)

You can find Mapping Templates by clicking on the + button, on the main navigation, and locating the Mapping Template item.

Once there, all mappings created under Engaging Networks Mapping will be listed. Click on each, you will see the core configuration of items the build of the mapping rule.

Engaging Networks Logs

Mapping templates.png As of 1.506, the Engaging Networks Logs tool provides more information on each processing jobs. Please note that in order for these logs to be generated, please enable through the Custom settings: Engaging Networks Log Settings object.

Configuration objects

Found under 'Setup > Develop > Custom Settings'.

Custom settings config objects.png

Engaging Network Settings

The object that holds the configuration options, for the EN Connector.

Engaging Networks Import Field Mapping

This is used to map column headings from an import file, with field names on the EN Import Record.

Example : A user in Engaging Networks creates a new field called 'Source tag', on the Default Supporter Record. In order for it to be mapped to the Engaging Network Import Record, EN_Connector__source_tag__c must be created or a mapping on this object, to an existing field on the Engaging Networks Import Record object.

Engaging Network Mappings

Used in listing which objects should show on the Engaging Networks Mapping page. For example, to map data to Contacts - add the sObject 'Contact' to the options.

Engaging networks mapping object correlations.png
Remember to make sure that custom sObjects has the field set 'Engaging Networks Mapping' created.

Custom settings: Engaging Networks Log Settings

Used in configuring logging options.

Engaging Network Jobs

Used in adding and prioritizing which mappings should run, under the scheduled apex job. ( ScheduleObjectPullAndPush )

Tip Under 'Setup > Develop > Custom Settings', it is helpful to add a 'Custom View', to isolate the EN Connector objects

It is helpful to add a 'Custom View', to isolate the EN Connector objects