Skip to main content
Full Circle Insights

Release Notes 1.25

Release Schedule

Name Description Date
Sandbox Upgrade All Response Management installs in Sandbox orgs will receive the update automatically June 11, 2018
Production Upgrade All Response Management installs in production orgs will receive the update automatically June 20, 2018

Customers will receive this release as an automatic push upgrade. Please note that automatic release updates will not effect existing Response Management functionality; opt in and configuration are required by customers before features are enabled. 

 

Release at a Glance

Enhancements Automatically visible to all users Requires administrator setup Contact Customer Success to Enable
Response Prompt Lightning Component   X  
New Opportunity Lightning Component   X  
Account-based First/Last Touch Calculation   X  
Apex Global API Enhancements N/A N/A N/A

Enhancements

Response Prompt Lightning Component

Are your sales teams on Lightning? Now you can use all the functionality of the classic Full Circle Response Prompt for Visualforce to the Lightning Experience. Administrators now have the flexibility to seamlessly add the Response Prompt to various areas of the Lead and Contact Lightning Record Pages. The component allows users to easily add a Lead or Contact to a configured campaign and create an active campaign member response, where the funnel will be tracked.  

How to Configure

Prerequisite: Lightning components require My Domain, and Domain Deployed to Users. For more information go to Salesforce Setup | Domain Management | My Domain.

Edit Contact (or Lead) Lightning Record Page(s)

Lightning Experience

  1. From Setup, enter the object name (Lead or Contact, in this case) in the Quick Find box.
  2. Select Object Manager.
  3. Click the Contact (or Lead) object.
  4. Select Lightning Record Pages.
  5. Edit each page, placing the component named FCRResponseSelector in either the "Details" tab or anywhere in the right sidebar. 
  6. Save the page.

For more details on Lightning Record Pages, see Create and Configure Lightning Experience Record Pages.

New Opportunity Lightning Component

Previously in the Lightning Experience, users creating a new Opportunity from Opportunity, Account, and Contact records were able to bypass certain Full Circle Response Management features, which could impact the accuracy of campaign participation. In the Summer '17 release, Salesforce introduced the ability to override standard actions on objects with Lightning components. This now allows Full Circle to extend key Response Management features from Salesforce Classic, to the Lightning Experience, by using a Custom Action. This new component (named FCROppNew) allows administrators to override the standard "New" Action on the Opportunity object, and the +New Opportunity option on the Opportunity tab, for Lightning Experience and Salesforce Mobile. All the following features of Response Management supported by this button in Salesforce Classic are now available in the Lightning Experience: 

Active/Passive Mode

The component supports the "Active/Passive mode" application configuration setting. Active mode users are restricted from creating an opportunity for a contact that does not have an active response associated to it. Passive mode users are allowed to create opportunities even when the contact does not have an active response associated to it.

Opportunity Gating

The component supports the "Restrict Opportunity Creation" application configuration setting. When this setting is enabled, active mode users must create opportunities from the contact related list or lead conversion. If they do not, they will be presented with an error message.

Opportunity Naming Convention

The component supports the "Opportunity Naming Convention" application configuration setting. When this setting is enabled and an opportunity is created from a contact record, the opportunity name field will be pre-populated with the account name followed by a dash.

Opportunity Field Population From Contact

The component supports the population of fields on the Opportunity being created with values from the Contact that it is being create from. The application configuration setting "Opportunity Creation Query String" is used to accomplish this. Specify API field names for both the opportunity and contact, joined by an "=" sign. For example: Opportunity_API_name1=Contact_API_name1. 

Important Notes:

  • If the field is hidden because it’s not on the page layout, the values specified in the configuration setting are saved with the new record. 
  • If the current user doesn’t have create access to the field, due to field-level security, attempts to save the new record result in an error.

How to Configure

Prerequisite: Lightning components require My Domain, and Domain Deployed to Users. For more information go to Salesforce Setup | Domain Management | My Domain.

Configuration consists of two steps:

  • First, the standard action needs to be overridden.
  • Second, there is a supporting Lightning component that needs to be placed on the Contact Lightning Record Pages in the org. This component is required in order for the override component to function correctly. It informs the other component whether the user is currently on a Contact detail page or some other page within the org.

Step 1: Override the Opportunity "New" Action with Lightning Component

You can override a standard action in both Salesforce Classic and Lightning Experience. While the destination is the same, the navigation paths are different.

Lightning Experience

  1. From Setup, enter the object in the Quick Find box.
  2. Select Object Manager.
  3. Click the name of the object for which you want to override a standard action.
  4. Select Buttons, Links, and Actions.

Salesforce Classic

  1. From Setup, navigate to the object for which you want to override a standard action.
  2. For standard objects, navigate to Build | Customize, and find the object.
  3. For custom objects, navigate to Build | Create | Objects, and find the object.
  4. Click the name of the object.
  5. Scroll to the Buttons, Links, and Actions section.

    Once you’re viewing the object’s Buttons, Links, and Actions list, select Edit for the action you want to override. From here, the steps are the same.
  1. For Override With, select Lightning Component Bundle.
  2. From the drop-down menu, select the Lightning component named FCROppNew
  3. Do not check "Skip record type selection page"
  4. Click Save.

Note: Users won’t see changes to action overrides until they reload Lightning Experience or Salesforce Mobile. On Windows use CTRL+F5. On Mac use Command+R.

Step 2: Edit the Contact Lightning Record Page(s)

Lightning Experience

  1. From Setup, enter object in the Quick Find box.
  2. Select Object Manager.
  3. Click the Contact object.
  4. Select Lightning Record Pages.
  5. Edit each page, placing the component named FCROppNewLocationSupport at the very top of the page. This component has no UI elements and will not be visible on the page, but must be placed on the page in order for the FCROppNew component to function properly.
  6. Save the page.

Step 3: Edit the Account Lightning Record Page(s)

Lightning Experience

  1. Repeat Step 2 (above) for the Account Lightning Record Pages.

Account-based First/Last Touch for Account Attribution Model

This new configuration setting allows you to configure your account-based attribution models so that the first and last touch are calculated using the earliest and most recent responses across all account contacts.

How to Configure

  1. From the Response Management Main Configuration page, click the Campaign Attribution button.
  2. You arrive at the Campaign Influence Main Configuration page.
  3. Find the Configure Models > Manage Models section.
  4. Identify an account-based model where the Model Type column is designated as Default Account Based. 
  5. Navigate to that account based influence model and click "Edit".
  6. Go to Advanced Configuration Options.
  7. Check the box for "Account Based First/Last Touch".
  8. Save the page.

Apex Global API Enhancements

New Methods

The following new global API methods will be available in the FCR_SupportAPI Apex class:

API Method Description
Boolean IsApplicationEnabled() Returns true if the application is currently enabled. Returns false otherwise.

New Interfaces

The IInfluenceDetailExtension interface has been added to the FCI_CampaignInfluenceAPI Apex class:

Interface Member Description
InitializeNewInfluenceDetailObject(FCR_Influence_Detail__c newObject, Integer modelNumber) Called for each new influence detail object - includes the model number
StandardFieldsUpdating(FCR_Influence_Detail__c newObject, Integer modelNumber, DateTime rebuildStartTime) Called the first time an influence detail object is updated for this rebuild and revenue model. Includes model number. Also includes the rebuild start time so that it's possible to determine if the record was updated already by a previous revenue model.
DetailObjectUpsert(String influencetype, List<FCR_Influence_Detail__c> influenceobjects, Map<ID, CampaignMember> allcms, Map<ID, Opportunity> allops, Integer modelNumber) This method is similar to the method on the interface ICampaignAttributionConfiguration, but this one takes the model number as a parameter. If both interfaces are implemented, this one will be called.
  • Was this article helpful?