Skip to main content
Full Circle Insights

Release Notes 1.21

Version 1.21 of Full Circle Response Management contains a number of new features, improvements and fixes. View highlights below in the Release at a Glance section.
 

Release Schedule

Name Description Date
Sandbox Upgrade All Response Management installs in Sandboxes will receive the update automatically* 09/13/2016
Production Upgrade All Response Management installs in production orgs will receive the update automatically* 09/15/2016

*Most users will receive this release as a push-upgrade. Please note that automatic release updates will not effect existing Response Management functionality; opt in and configuration are required before features are enabled. 

Contact your Customer Success team member or log a case in the Customer Success Community

  • If you wish to exclude your organization from automatic release updates.
  • To receive the installation link, so you can perform installation yourself. If you choose this installation option, be sure to select the profiles that should receive access to the new features. 
  • For assistance with migration from the unmanaged package settings, including:
    • Migrating unmanaged Response Prompt Reanimation code to the Response Prompt Reactivation scenario.
    • Migrating unmanaged Rescoring code to the Score Reactivation scenario.
    • Migrating unmanaged Full Circle Sync Field Clear package.

Release at a Glance

Feature Type Automatically visible to all users Requires administrator setup Contact Customer Success to enable
Reactivation Scenarios New Feature X   X
Field Synchronization Enhancements New Feature X   Recommended for companies using the 'Full Circle Sync Field Clear' Package
Lead/Contact Date and Time Status New Feature   X  
Campaign Influence New Fields New Feature   X  
CreateAssociation parameter: treatasrptr New Feature X    
Increment Admin Update Counter New Feature X    
Campaign Influence Timeframe Improvement X    
Campaign Influence Database Rebuild Improvement X    
New Permission Sets Improvement X    
Active/Passive Mode Configuration Enhancements Improvement X    
Async Request Retry Improvement X    
Deferred Update Item Delete Button Improvement   X  
First Owner Assigned Set for Lead Conversion Fix X    

New Features

Reactivation Scenarios

Reactivation scenarios simplify the configuration of features that have, until now, been delivered in a number of unmanaged packages. Users who have been utilizing features like Reanimation and Re-Scoring, and administering the relevant settings using custom settings and workflows will now be able to migrate away from these and use a simpler wizard interface to manage these features and settings. 

Reactivation is the ability to call to a previously inactive campaign response that has been dispositioned and make it the active and primary campaign response ("Tipping point" campaign).

Reactivation scenarios:

  • When triggered, reactivation looks for an inactive response and makes it the active/tipping point response.
  • Manage the identification of an active response when other events (such as a score increment) indicate that an active response is required to track a new funnel engagement.
  • Enable a recent response to become active, and may also insert a default response if a recent response is not identified. 

Reasons for reactivation:

There are a variety of reasons to utilize the reactivation scenario functionality and you would decide what to enable based on your business process.

A couple of examples include: A prospect was in nurture and within a selected time period a sales rep conducts some outreach and reactivates the prospect. You want the latest campaign to get the credit. Or a scoring threshold is met, based on non campaign related activities and you want the new score to push the prospect into a qualified status.

Three types of members that you can reactivate include: never engaged, non-responses (not applicable for scoring), dispositioned.

Reactivation scenario setting and configuration access has been added to the Configuration section of the Main Configuration page of Response Management.  

This initial release provides configuration options for the four reactivation scenarios listed below. From the Edit pick list of each, you can select the appropriate criteria, based on your organization's business needs.

Response Prompt Reactivation

Response Prompt Reactivation allows the insertion of a campaign from the lead or contact Response Prompt pick list (Visualforce page) to optionally reactivate a recent response instead of inserting the new or selected response.

Reactivation reopens an earlier campaign response previously dispositioned as inactive instead of adding a new response prompt campaign.

Example: If a prospect (lead or contact) re-engages after disqualification, Response Prompt Reactivation reactivates a previously disqualified marketing-sourced response, in order to make this campaign member record the active response.   If this scenario is Disabled, the original marketing-sourced response will remain disqualified and the application will allow creation of a new active response associated with the response prompt campaign (i.e. sales outreach) selected by the sales rep from the pick list. 

Score Reactivation

Score Reactivation detects increased score changes which may not be associated with a new campaign response. 

Used in combination with lead and contact workflow rules, this reactivation scenario can reactivate a recent response or insert a default campaign if the workflows detect a scoring event that should drive a new funnel engagement.  

This reactivation scenario supports:

  • Time delay for reactivation
  • Reactivation of a recent response
  • Insertion of a single default campaign response

Score reactivation is common with predictive scoring models where score changes are not directly associated with campaign actions.

Example: If your score threshold for qualified responses is 100, and a lead responds to a campaign (webinar) with a score of 90, the score wouldn't qualify the lead. Subsequently, if the score increases to 100, based on activities that are not associated with a new campaign response, then the webinar's score will increase and it will trigger the active response.  If this scenario is Disabled, no campaign response will be related to the score above threshold.. 

Process Builder Reactivation

Process Builder Reactivation can be triggered with the Process Builder configuration settings or Apex code. The functionality is flexible and allows you to re-activate responses based on complex criteria. 

This reactivation scenario supports:

  • Leads, contacts and tasks
  • Reactivation of a recent response
  • Insertion of a single default campaign response
  • User role defined default campaign responses

Example: Your company uses call tracking software which creates activity records when sales reps make calls. This feature can automatically add an active campaign response to the lead or contact record when certain activity records are added to Salesforce to automate this campaign association.  When triggered, this functionality will search for a recent eligible response and make it the active response, or optionally insert a default response. 

Active Status Reactivation

Active Status Reactivation allows users who are running in Passive or Hybrid Mode to capture engagements when sales reps manually move a lead or contact from inactive to active. This is important because passive users normally do not effectively track sales outbound activities in Passive Mode.

This reactivation scenario will work for organizations running in Passive Mode. This trigger detects when the lead or contact status is updated from an inactive to active value, and there is no active response. 

This reactivation scenario supports:

  • Time delay for reactivation
  • Reactivation of a recent response
  • Insertion of a single default campaign response
  • User role defined default campaign responses

Example: Your Salesforce org is running in Passive Mode and a sales rep moves a lead from nurture to working. The Active Status Reactivation is triggered, which searches the campaign history.  Because you have been operating in Passive Mode, there are no associated campaign responses, therefore a suitable campaign is not found. Active Status Reactivation inserts a default campaign based on the running user’s (Owner's) role.

Who does it benefit?  

Users who are currently utilizing the reactivation scenario unmanaged packages, custom code or workflow rules can now use a simple wizard interface to enable and manage reactivation features and settings. 

What problem does this new feature solve? 

Reactivation scenarios replace unmanaged packages, and in many cases, custom code used for many users to address unique processes that were not previously detected by the core Response Management package. If you are a new user, you can be deployed with less customization. If you are an existing user you can migrate to this functionality and automate your campaign tracking.

Access to a single place to review configuration makes it easier for you to understand existing functionality or to modify reactivation scenarios as your business changes.

Key considerations  

Reactivation scenarios are highly configurable and you should carefully review how each works before making a choice regarding which settings to enable. 

One change to note is that all reactivation scenarios use a single campaign member field called Reactivation Date, whereas the unmanaged Rescoring and Response Reanimation packages each had a unique audit field set.

A campaign member can only be reactivated once, so once this date/time field is set on the campaign member it applies to all reactivation scenarios.  The configuration will let you define unique date/time fields if you want to have a unique audit trail for each reactivation scenario.

Contact your Customer Success team member or log a case in our Community:

  • For support when evaluating whether or not a reactivation scenario is right for your organization
  • If you are currently using unmanaged packages (Response Reactivation, Rescore Trigger)
Enablement Instructions 

Unmanaged package code migration is required for the following, and you should contact your Customer Success team member or log a case in the Customer Success Community for assistance:

  • Response Prompt Reanimation code to the Response Prompt Reactivation scenario
  • Migrating unmanaged Rescoring code to the Score Reactivation scenario

Field enablement is required for the following:

New Campaign Member Field:

Reactivation Date: This is the date/time the response was reactivated. It is not set when inserting a default campaign. Once set, this response cannot be reactivated by other reactivation scenarios.

To make this field visible to users:

  • Modify Set-Field Level Security
  • Add the field to the Campaign Member Analytics page layout

New Campaign Fields: 

Default Responded Member Status: If this field is populated, reactivation scenarios may update a campaign member to a status configured as a response. Populate with member status that is on this campaign and configured with 'Responded' checkbox.

Exclude From Reactivation: When checked this campaign is not-eligible for reactivation.

To make these fields visible to users:

  • Modify Set-Field Level Security
  • Add the fields to Campaign Page Layouts 

Field Synchronization Enhancements

New lead and contact settings have been added to the Field Synchronization Configuration page.  This page allows you to synchronize custom fields between leads and contacts, and their associated campaign member (Response) records, or the campaign member record and the campaign influence detail record.

You can access the new settings by clicking the Sync Fields section of the Main Configuration page of Response Management. 

The following settings (red dot) have been added to the Field Synchronization Configuration page:

 

Applies to both Lead and Contact field settings

 

 

Clear After Sync on Create
  • Works in conjunction with Sync on Create (green dot - existing setting).
  • If both of these settings are checked, the Source field will be cleared after the data is synced to the response.
  • A common use-case is to synchronize UTM fields from the related lead or contact, and to clear them after the synchronization is complete.
  • Previously part of the unmanaged package Full Circle Sync Field Clear - used to clear fields off the lead or contact after synchronization and was commonly used to snapshot UTM data up to the response that came in next.
Applies to Contact field settings only
 Sync on Convert
 
  • Some users want to synchronize data up to the response when a lead is converted to a contact.
  • This setting applies to leads with active responses converted to contacts.
  • When checked, the value of the source field on the contact will be updated to the active response after lead conversion.
  • Use this setting to capture data you want to snapshot from the contact, post lead conversion. Consider lead to contact field mapping.
  • A contact with a formula field exposing account information can be used to sync information about the account at the time of lead conversion.
  • Previously configured with workflow rules.
Sync on Op-Create
  • Some users want to synchronize data up to the response when an opportunity was created either during lead conversion or from the contact record.
  • This setting synchronizes data from the contact source field to the active response when an opportunity is created either during lead conversion with an opportunity or from the related contact record when an opportunity is created from a contact record.
  • Previously configured with workflow rules.
Who does it benefit?  
  • Users administering and monitoring the Full Circle Response Management application
  • Analytics teams that need to synchronize lead or contact fields up to the campaign member
What problem does this new feature solve?

This new functionality allows you to capture data unique to campaign responses that is otherwise not captured or in some cases overwritten over time in Salesforce. 

Key considerations

Prior to upgrading, you should contact your Customer Success team member or log a case in our Community to review configuration updates, including:

Uninstalling the Full Circle Sync Field Clear package

  • If you are currently using the Full Circle Sync Field Clear package you will need to uninstall the unmanaged package before upgrading to this functionality.
  • To see if you have this package installed, navigate  to Setup | Installed Packages and look for Full Circle Sync Field Clear by Full Circle Insights.

Deleting Workflows

  • Prior to deleting workflows, users with workflow rules setting fields on lead conversion or when an opportunity is created should review configuration updates.
Enablement Instructions

This feature does not require enablement. Sync functionality must be configured within the application.

Lead/Contact Date and Time Status Fields  

There are two new lead/contact date and time status field settings:

Status Last Set field:

Creates an audit for when the lead status and contact status fields are changed. When they change, the system sets a date and time value on the lead or contact Status Last Set field.

Status Age field: 

A formula field that displays the number of days since the lead status was changed. 

Who does it benefit?  

Users who want visibility on the lead/contact status changes related to date and time values.

What problem does this new feature solve? 

These settings were previously deployed with unmanaged package fields and workflow rules.  By adding these fields and functionality to the managed package, you can remove unmanaged package fields and eliminate two workflow rules.

Key considerations

Users with existing unmanaged package fields should migrate data over to the managed package fields before deleting the unmanaged fields and workflow rules. Contact your Customer Success team member or log a case in our Community, to review configuration updates and what workflows can be deleted.

Enablement Instructions  

Status Last Set: Date and time when status was last updated.

Status Age: Number of days since the lead status was changed.

To make these fields visible to users:

  • Modify Set-Field Level Security
  • Add the fields to Campaign Page Layouts 

If you are using existing fields (previously created) deployed by the Full Circle Team:

  • Migrate values from the existing custom Status Last Set field using the Data Loader.
  • Adjust any views or reports referencing the original custom fields.
  • Delete lead and contact workflows and field updates to use the original fields.
  • Delete custom Status Last Set and Status Age fields from leads and contacts.

Campaign Influence Member Status Field 

A new Member Status field has been added to the Campaign Influence Detail object. The Member Status field will be populated during the the Campaign Influence database rebuild and is related to the response at the time of the rebuild. 

Who does it benefit?  

Analysts and Marketers who want to report on segment data by the campaign member status in Campaign Influence reports.

What problem does this improvement solve? 

This information was previously unavailable in Campaign Influence data.

Key considerations  

The Member Status field reflects the campaign member status when the database was last refreshed and may not be the current member status value.

Enablement Instructions
  • Navigate to Setup | Create | Objects |Campaign Influence Detail.

To make the field visible to users:

  • Modify Set-Field Level Security

Update the Campaign Influence Detail Custom Report type to include this field:

  • Navigate to Set up |Build | Create | Report Types.
  • Locate the report type that has the letters CRT in the report type label.    
  • Edit Layout and add the field to the available fields for this report type.
  • If you are unsure which custom report types to update, contact your Customer Success team member or log a case in the Customer Success Community for assistance.

CreateAssociation Parameter: treatasrptr 

The Superpower command CreateAssociation has a new parameter available in the command called treatasrptr. This parameter will treat the campaign member inserted as if it's a response prompt campaign and will also be able to trigger the new Response Prompt Reactivation scenario. The existing treatasrp command will not trigger the new Response Prompt reactivation scenarios.

Example syntax:

CreateAssociation Responded treatasrptr 70136000000Ahn8

Translation: Command[CreateAssociation] [MemberStatus] treatasrptr [Campaign id]

Treatasrp and treatasrptr treat responses inserted as response prompt campaigns in the sense that:

  • They are always considered qualified
  • They bypass Nurture timeout
  • They will insert repeats if repeats are allowed on the campaign

Treatasrptr will trigger the response prompt reactivation scenario login as:

  • The campaign member inserted must belong to a campaign that is configured as a response prompt campaign
  • The response prompt configuration must have the setting Trigger Reactivation checked

Who does it benefit?  

Users who wish to insert members using the lead or contact FCCRM Superpower field and trigger the Response Prompt Reactivation scenario.

What problem does this improvement solve? 

This parameter provides support for the new Response Prompt Reactivation scenario.

Key considerations  

Users utilizing treatasrp should update existing Superpower commands to treatasrptr once they have upgraded to the new Response Prompt Reactivation Scenario. It is Ok to use this command even if a Response Prompt Reactivation scenario is not enabled.

Enablement Instructions

This feature does not require enablement.

Increment Admin Update Counter  

A new setting called Increment admin update counter on selected non-DML changes has been added to the Advanced Configuration section of the Main Configuration page of Response Management.

 This setting supports specific use-cases, and in this release supports one use-case. 

Who does it benefit?  

Organizations that want Response Management to increment the Admin Response Control field in cases where a field update to a select Response Management field is initiated by a user or a database operation. Incrementing this field can allow organizations to bypass validation rules.

What problem does this improvement solve? 

Normally the Admin Update Counter field on an object is only incremented during database operations initiated by the Response Management application.

When this option is checked, the counter will also be incremented during selected field changes by Response Management during triggers resulting from database operations initiated manually or from other applications. This setting initially supports updates to the Response Management managed Contact Status Field.

This setting allows organizations to increment the Admin Update Counter in the following scenario:

If a contact has an Opportunity-Active Response, and an Active Response, the Contact Status will reflect the engagement level with the Active Response (such as Open or Working).  If the sales rep updates the Contact Status to a non-active status (such as Recycle) the application will update the contact status back to the Opportunity-Active Status (such as Active Opportunity - System Use).

During this contact status update the application does NOT increment the Admin Update Counter field because the update was initiated by a user and not by Response Management. Companies with validation rules preventing users from setting the Contact Status to the Opportunity-Active status will not be able to bypass the validation rule.

When the setting Increment admin update counter on selected non-DML changes is checked, this scenario will update the Admin Update Counter field so that the validation rule will not fire.

Key considerations  

The scenario's supported may expand over time. If you are using this setting, be sure to review future release notes for additional supported scenarios.

Enablement Instructions

This feature does not require enablement.

Field Synchronization Enhancements

New lead and contact settings have been added to the Field Synchronization Configuration page.  This page allows you to synchronize custom fields between leads and contacts, and their associated campaign member (Response) records, or the campaign member record and the campaign influence detail record.

You can access the new settings by clicking the Sync Fields section of the Main Configuration page of Response Management. 

The following settings (red dot) have been added to the Field Synchronization Configuration page:

 

Applies to both Lead and Contact field settings

 

 

Clear After Sync on Create
  • Works in conjunction with Sync on Create (green dot - existing setting).
  • If both of these settings are checked, the Source field will be cleared after the data is synced to the response.
  • A common use-case is to synchronize UTM fields from the related lead or contact, and to clear them after the synchronization is complete.
  • Previously part of the unmanaged package Full Circle Sync Field Clear - used to clear fields off the lead or contact after synchronization and was commonly used to snapshot UTM data up to the response that came in next.
Applies to Contact field settings only
 Sync on Convert
 
  • Some users want to synchronize data up to the response when a lead is converted to a contact.
  • This setting applies to leads with active responses converted to contacts.
  • When checked, the value of the source field on the contact will be updated to the active response after lead conversion.
  • Use this setting to capture data you want to snapshot from the contact, post lead conversion. Consider lead to contact field mapping.
  • A contact with a formula field exposing account information can be used to sync information about the account at the time of lead conversion.
  • Previously configured with workflow rules.
Sync on Op-Create
  • Some users want to synchronize data up to the response when an opportunity was created either during lead conversion or from the contact record.
  • This setting synchronizes data from the contact source field to the active response when an opportunity is created either during lead conversion with an opportunity or from the related contact record when an opportunity is created from a contact record.
  • Previously configured with workflow rules.
Who does it benefit?  
  • Users administering and monitoring the Full Circle Response Management application
  • Analytics teams that need to synchronize lead or contact fields up to the campaign member
What problem does this new feature solve?

This new functionality allows you to eliminate workflow rules and simplify your deployment. 

Key considerations

Prior to upgrading, you should contact your Customer Success team member or log a case in our Community to review configuration updates, including:

Uninstalling the Full Circle Sync Field Clear package

  • If you are currently using the Full Circle Sync Field Clear package you will need to uninstall the unmanaged package before upgrading to this functionality.
  • To see if you have this package installed, navigate  to Setup | Installed Packages and look for Full Circle Sync Field Clear by Full Circle Insights.

Deleting Workflows

  • Prior to deleting workflows, users with workflow rules setting fields on lead conversion or when an opportunity is created should review configuration updates.
Enablement Instructions

This feature does not require enablement. Sync functionality must be configured within the application.

Lead/Contact Date and Time Status Fields  

There are two new lead/contact date and time status field settings:

Status Last Set field:

Creates an audit for when the lead status and contact status fields are changed. When they change, the system sets a date andtime value on the lead or contact Status Last Set field.

Status Age field: 

A formula field that displays the number of days since the lead status was changed. 

Who does it benefit?  

Users who want visibility on the lead/contact status changes related to date and time values.

What problem does this new feature solve? 

These settings were previously deployed with unmanaged package fields and workflow rules.  By adding these fields and functionality to the managed package you can remove unmanaged package fields and eliminate two workflow rules.

Key considerations

Users with existing unmanaged package fields should migrate data over to the managed package fields before deleting the unmanaged fields and workflow rules. Contact your Customer Success team member or log a case in our Community, to review configuration updates and what workflows can be deleted.

Enablement Instructions  

Status Last Set: Date and time when status was last updated.

Status Age: Number of days since the lead status was changed.

To make these fields visible to users:

  • Modify Set-Field Level Security
  • Add the fields to Campaign Page Layouts 

If you are using existing fields (previously created) deployed by the Full Circle Team:

  • Migrate values from the existing custom Status Last Set field using the Data Loader.
  • Adjust any views or reports referencing the original custom fields.
  • Delete lead and contact workflows and field updates to use the original fields.
  • Delete custom Status Last Set and Status Age fields from leads and contacts.

Campaign Influence Member Status Field 

A new Member Status field has been added to the Campaign Influence Detail object. The Member Status field will be populated during the the Campaign Influence database rebuild and is related to the response at the time of the rebuild. 

Who does it benefit?  

Analysts and Marketers who want to report on segment data by the campaign member status in Campaign Influence reports.

What problem does this improvement solve? 

This information was previously unavailable in Campaign Influence data.

Key considerations  

The Member Status field reflects the campaign member status when the database was last refreshed and may not be the current member status value.

Enablement Instructions
  • Navigate to Setup | Create | Objects |Campaign Influence Detail.

To make the field visible to users:

  • Modify Set-Field Level Security

Update the Campaign influence Detail Custom Report type to include this field:

  • Navigate to Set up |Build | Create | Report Types.
  • Locate the report type that has the letters CRT in the report type label.    
  • Edit Layout and add the field to the available fields for this report type.
  • If you are unsure which custom report types to update, contact your Customer Success team member or log a case in the Customer Success Community for assistance.

CreateAssociation Parameter: treatasrptr 

The Superpower command CreateAssociation has a new parameter available in the command called treatasrptr. This parameter will treat the campaign member inserted as if it's a response prompt campaign and will also be able to trigger the new Response Prompt Reactivation scenario. The existing treatasrp command will not trigger the new Response Prompt reactivation scenarios.

Example syntax:

CreateAssociation Responded treatasrptr 70136000000Ahn8

Translation: Command[CreateAssociation] [MemberStatus] treatasrptr [Campaign id]

Treatasrp and treatasrptr treat responses inserted as response prompt campaigns in the sense that:

  • They are always considered qualified
  • They bypass Nurture timeout
  • They will insert repeats if repeats are allowed on the campaign

Treatasrptr will trigger the response prompt reactivation scenario login as:

  • The campaign member inserted must belong to a campaign that is configured as a response prompt campaign
  • The response prompt configuration must have the setting Trigger Reactivation checked.

Who does it benefit?  

Users who wish to insert members using the lead or contact FCCRM Superpower field and trigger the Response Prompt Reactivation scenario.

What problem does this improvement solve? 

This parameter provides support for the new Response Prompt Reactivation scenario.

Key considerations  

Users utilizing treatasrp should update existing Superpower commands to treatasrptr once they have upgraded to the new Response Prompt Reactivation Scenario. It is Ok to use this command even if a Response Prompt Reactivation scenario is not enabled.

Enablement Instructions

This feature does not require enablement.

Increment Admin Update Counter  

A new setting called Increment admin update counter on selected non-DML changes has been added to the Advanced Configuration section of the Main Configuration page of Response Management.

 This setting supports specific use-cases, and in this release supports one use-case. 

Who does it benefit?  

Organizations that want Response Management to increment the Admin Response Control field in cases where a field update to a select Response Management field is initiated by a user or a database operation. Incrementing this field can allow organizations to bypass validation rules.

What problem does this improvement solve? 

Normally the Admin Update Counter field on an object is only incremented during database operations initiated by the Response Management application.

When this option is checked, the counter will also be incremented during selected field changes by Response Management during triggers resulting from database operations initiated manually or from other applications. This setting initially supports updates to the Response Management managed Contact Status Field.

This setting allows organizations to increment the Admin Update Counter in the following scenario:

If a contact has an Opportunity-Active Response, and an Active Response, the Contact Status will reflect the engagement level with the Active Response (such as Open or Working).  If the sales rep updates the Contact Status to a non-active status (such as Recycle) the application will update the contact status back to the Opportunity-Active Status (such as Active Opportunity - System Use).

During this contact status update the application does NOT increment the Admin Update Counter field because the update was initiated by a user and not by Response Management. Companies with validation rules preventing users from setting the Contact Status to the Opportunity-Active status will not be able to bypass the validation rule.

When the setting Increment admin update counter on selected non-DML changes is checked, this scenario will update the Admin Update Counter field so that the validation rule will not fire.

Key considerations  

The scenario's supported may expand over time. If you are using this setting, be sure to review future release notes for additional supported scenarios.

Enablement Instructions

This feature does not require enablement.

Improvements

Campaign Influence Timeframe

A timeframe enhancement has been added to the Campaign (Influence) Attribution section of the Main Configuration page of Response Management. 

A new Influence Time Frame pick list has been introduced to Campaign Influence Default Account and Opportunity Based models that allow you to select Before only or During only the open and closed date of an opportunity.  Previous to this release, influence timeframes always considered campaigns influential during the time the opportunity was open, and once closed, until the opportunity closed date.

Access the pick list from Campaign Influence Main Configuration page | Configure Models | Manage ModelsEdit | Model Name. Select | Influence Time Frame  pick list value.


Before and During Opportunity (set as default timeframe and represents the same value that was available before this release)

  • This value indicates campaigns are influential prior to opportunity create, for the duration that the opportunity is open, and if closed, until the opportunity closed date.

Before Opportunity Only

  • This value will only consider campaigns influential where the response date is prior to the opportunity created date.

During Opportunity Only

  • This value will only consider campaigns influential where the response date is after to the opportunity created date, for the duration that the opportunity is open, and if closed, until the opportunity closed date.
Who does it benefit?  

Analysts and Marketers that want to run influence models with these timeframe choices.

What problem does this improvement solve? 

Calculating influence before opportunity only was not possible prior to this release. Some marketing organizations want to run influence as a Demand Gen model and this choice allows the distribution of revenue to be applied to this particular sub-set of responses.

Key considerations  

Changing timeframes for an existing model will change the output. When the influence model runs, the whole database is rebuilt. Users will need to wait for the influence database to rebuild to see configuration changes.

Enablement Instructions

This improvement does not require enablement. The default setting on upgrade will be Before and During Opportunity which is consistent with the prior model default behavior. 

Campaign Influence Database Rebuild

New functionality has been added to the Data Processing section of the Campaign Influence Main Configuration page that  includes a new weekly database rebuild timeframe option and the ability to abort an ongoing database rebuild, in order to modify influence models or other configuration settings.

Weekly Database Rebuilds

From Data Processing |Update Frequency section of the Campaign Influence Main Configuration page (scroll to bottom of page) you have the option to select database rebuilds to run Daily, Weekly or On Demand.

New pick list:

Daily rebuilds is the current default and this choice prompts you for the time to initiate the database rebuild.

For Weekly rebuilds you can set the day and time.

Database Abort

When the Campaign Influence database is rebuilding, you cannot modify existing models and will be presented with a message indicating the status of the database rebuild.

If you need to modify a model or abort the database rebuild for some other reason, click the Advanced Configuration button. 

An Abort Database Rebuild button will display. Note, this button is hidden when the database is not rebuilding.

Clicking on this button will abort the database rebuild and influence models will be editable.

After editing the model you can start a new database rebuild. Navigate to Campaign Influence Main Configuration page | scroll down to Data Processing | Manage Database Rebuilds section | click Rebuild Campaign Influence Data Now button.

Who does it benefit?  

Users responsible for configuring the Full Circle Campaign Influence models.

What problem does this improvement solve? 

Organizations with large databases and a high volume of scheduled Apex jobs may have database rebuilds that take a long time. These organizations may prefer a weekly database rebuild to reduce the amount of scheduled jobs running.  The Abort Database Rebuild feature allows you to make quick modifications of models without waiting for the database rebuild to be completed.

Key considerations  

The Campaign Influence database rebuild will reflect data from the most recent rebuild. If analysis is done on the output infrequently, a weekly rebuild may be a good configuration choice. Real time influence data is always visible from the Deal Explorer.

Aborting the database rebuild will restart the database rebuild and the time to rebuild the database is dependent on the number and complexity of models running, as well as the database size.

Enablement Instructions

This improvement does not require enablement. The default setting on upgrade will be Daily or OnDemand which is consistent with the prior model default behavior.

New Permission Sets

Two new permission sets are available to help you manage user access.

Full Circle Campaign Influence Configuration

  • This permission set allows users to access to the Full Circle Campaign Influence tab in order to configure attribution models. The permission set incudes tab visibility for the Full Circle Campaign Influence tab, Visual force page access for the underlying configuration pages, and Apex class access to the Response Management Apex classes.
  • Assign this permission set to the select set of users that need to configure influence models.

Full Circle Response Management

  • This permission set allows users to access all of the Response Management Fields, Objects, Visualforce pages and Apex classes in order to use the application and reporting features. It does NOT grant access to the Full Circle Campaign Influence Tab. This permission set does NOT grant additional administrative or system permissions.
  • Organizations using permission sets to grant application access should assign this permission set to existing and new users.
Who does it benefit?  

System administrators who want to manage Response Management user access with permission sets.

What problem does this improvement solve? 

The Full Circle Response Management permission set will be updated by Full Circle Insights as new components are edited or modified, which makes application upgrades simpler. For organizations getting push upgrades, permission set assignment will automatically add visibility to new fields and access to any new Apex or Visualforce components.

Key considerations  

You must remember to add permission sets to new users. In general, we recommend this permission set be assigned to any users using leads, contacts, accounts, campaigns and opportunities. If you are using permission sets to grant access to the application, you may wish to create automation to assign the permission set to new users.

Enablement Instructions

This improvement does not require enablement. 

  • Assign the Full Circle Response Management permission set to all users accessing the application.

TIP: Create automation rules to automatically assign the permission set for new users.

Active/Passive Mode Configuration Enhancements

A new Organization Mode Configuration section has been added to the General Configuration section of the Main Configuration page of Response Management. 

This new section makes it easier to configure and maintain Active, Passive, Hybrid Mode and User Override settings. 

  


Previous to this release, organizations that had any Active users would require that all users default to Active and that all Passive profiles be overridden.

With this setting, an organization running in Active mode can define the default setting for all profiles as Passive and not have to update application configuration unless the new profile should be Active.

An organization will run in Passive Mode when the Global Passive Mode setting is checked.

An organization will run in Active mode when the Global Passive Mode setting is unchecked, Active is selected in the Org-Wide Default for Undefined Profiles and Users, and no Profiles or Users have been selected for overrides. 

An organization will run in Hybrid Mode when you select Active or Passive as the Org-Wide Default, and then add Profile/User and Override in the opposite mode.

For example, in the settings below, all new profiles and users will run in Active mode, with the exception of the user added in the Profile and User Override section. He will run in Passive mode.  Please note that a Passive Org Wide Default and Active Profile and User Overrides can be set. Determine your business and reporting needs before setting any of the modes. 

Who does it benefit?

Salesforce administrators who are creating new users in Salesforce.

What problem does this improvement solve? 

For organizations running in Hybrid mode - using a default mode of Passive allows the creation of new profiles in Passive mode without requiring an update to the Full Circle General Configuration page.

Key considerations  

These settings are hierarchy settings, which means that a user configuration will take priority over a profile setting. Upgrading will not change the default settings but you have an opportunity to simplify your configuration and minimize configuration updates for newly created profiles.

Enablement Instructions

This improvement does not require enablement, but if you are running in Hybrid mode you may want to simplify your configuration. Contact your Customer Success team member or log a case in the Customer Success Community for guidance.

Async Request Retry

Asynchronous updates are stored by the Response Management Async system in an object called Async Request. New functionality adds a second retry for failed Async updates that are using the CreateAssociation command, before flagging the record as an error. Async Request records that do not process are visible in your Check Report Dashboard in the failed Async Request component.

What problem does this improvement solve? 

This improvement makes the Async System more robust for organizations using the CreateAssociation command in the lead or contact FCCRM Superpower field.

Enablement Instructions

This improvement does not require enablement.

Deferred Update Item Delete Button

 A Delete button option has been added to the Deferred Update Item list view.

Who does it benefit?  

Salesforce administrators and Marketing Operations.

What problem does this improvement solve? 

Users that need to delete Deferred Update Item records, can do so from a list view instead of using the Data Loader.

Navigate to the list view by going to Setup | Installed Packages | Manage by Full Circle Insights Response Management | Event Logs button | View Update Errors button.

Key considerations

Before deleting these records make sure they do not need to be reprocessed. You can do so by adjusting the list view to see the intended update.

Enablement Instructions

To make this button visible to users:

  • Navigate to Setup | Create | ObjectsDeferred Update Items Search Layouts.
  • Click Edit | Deferred Update Items List View.

  • Locate Standard Buttons | Uncheck New, Accept and Change Owner.
  • Locate Custom Buttons | Available Buttons Column Add Delete to the Selected Buttons Column.
  • Click Save.

Fixes

First Owner Assigned Set for Lead Conversion

When a Queue owned lead with an active response in the default lead status value for a new response is converted to a contact (without an opportunity) - if the contact status mapping is the default contact status value for a new response - the First Owner Assigned field on the active response will be set to the contact owner.

Who does it benefit? 

Sales and Marketing Ops reporting on Campaign Member user metrics.

What problem does this Fix solve? 

The first owner Assigned field is a User Lookup field set when an active response is owned by a user and the Response Status is the default for a new Active Response (such as Open). 

This field will be updated if the user is changed and the response status is still that default value. There was a use case where a Queue owned lead was converted to a contact (without creating an opportunity) and the default value would persist. At the point of lead conversion, the owner would be a user (since contacts cannot be owned by Queues), but the First Owner Assigned field was not being set.

This release fixes this scenario so that the First Owner Assigned will be set to the contact owner.

Enablement Instructions

This fix does not require enablement.

Installation and Enablement Instructions

Following are a combined list of installation and enablement instructions also listed within individual feature descriptions of this document.

Installation

Most users will receive this release as a push-upgrade. Please note that automatic release updates will not effect existing Response Management functionality; opt in and configuration are required before features are enabled. 

Contact your Customer Success team member or log a case in the Customer Success Community

  • If you wish to exclude your organization from automatic release updates.
  • To receive the installation link, so you can perform installation yourself. If you choose this installation option, be sure to select the profiles that should receive access to the new features. 
  • For assistance with migration from the unmanaged package settings, including:
    • Migrating unmanaged Response Prompt Reanimation code to the Response Prompt Reactivation scenario.
    • Migrating unmanaged Rescoring code to the Score Reactivation scenario.
    • Migrating unmanaged Full Circle Sync Field Clear package.
Enablement

Reactivation Scenarios

New Campaign Member Field:

Reactivation Date: This is the date/time the response was reactivated. It is not set when inserting a default campaign. Once set, this response cannot be reactivated by other reactivation scenarios.

To make this field visible to users:

  • Modify Set-Field Level Security
  • Add the field to the Campaign Member Analytics page layout

New Campaign Fields: 

Default Responded Member Status: If this field is populated, reactivation scenarios may update a campaign member to a status configured as a response. Populate with member status that is on this campaign and configured with 'Responded' checkbox.

Exclude From Reactivation: When checked this campaign is not-eligible for reactivation.

Lead/Contact Date and Time Fields

To make these fields visible to users:

  • Modify Set-Field Level Security
  • Add the fields to Campaign Page Layouts 

Status Last Set: Date and time when status was last updated.

Status Age: Number of days since the lead status was changed.

To make these fields visible to users:

  • Modify Set-Field Level Security
  • Add the fields to Campaign Page Layouts 

If you are using existing fields (previously created) deployed by the Full Circle Team:

  • Migrate values from the existing custom Status Last Set field using the Data Loader.
  • Adjust any views or reports referencing the original custom fields.
  • Delete lead and contact workflows and field updates to use the original fields.
  • Delete custom Status Last Set and Status Age fields from leads and contacts.

Campaign Influence Member Status Field

  • Navigate to Setup | Create | Objects |Campaign Influence Detail.

To make the field visible to users:

  • Modify Set-Field Level Security

Update the Campaign influence Detail Custom Report type to include this field:

  • Navigate to Set up |Build | Create | Report Types.
  • Locate the report type that has the letters CRT in the report type label.    
  • Edit Layout and add the field to the available fields for this report type.
  • If you are unsure which custom report types to update, contact your Customer Success team member or log a case in the Customer Success Community for assistance.

Deferred Update Items List View Delete Button

To make this button visible to users:

  • Navigate to Setup | Create | ObjectsDeferred Update Items Search Layouts.
  • Click Edit | Deferred Update Items List View.

  • Locate Standard Buttons | Uncheck New, Accept and Change Owner.
  • Locate Custom Buttons | Available Buttons Column Add Delete to the Selected Buttons Column.
  • Click Save.