Skip to main content
Full Circle Insights

Release Notes 1.04

Overview

This document highlights new features and functionality that is part of the 1.4 release of the Full Circle CRM Response Management System.
Complete functionality is available in the system administration guide. Be sure to review the Installation and updates section at the end of
this document.

Minor Functional Updates

The following are process updates:

  • Nurture Timeout field on Leads and Contacts is cleared when the record is Opened (when a lead/contact goes from inactive to active status value) (FCRM_FCR_Nurture_Timeout__c)
  • Response Prompt text is increased to 35 characters in length. This is the value you see in the dropdown picklist in the response information section of the Lead and Contact page.
  • Reassign leads ‘stuck’ in the reassignment queue. For organizations using a processing Queue (as defined in the assignment configuration page processing queue radio button) – those that are still in that queue eight hours after create will trigger assignment automatically. This is managed as a future call so it will require some activity in the organization to trigger this functionality so the timing of eight hours may not be exact. This update does not apply to organizations that do not have a configured processing queue.
  • Updated look for response intelligence charts. Charts now have a white background.
  • Updated default response prompt text for when a sales campaign is required to update the status from red to black. This update was made because the red text was similar to Salesforce validation errors and was confusing to end-users.

Support for Multiple Campaign Influence Models

Overview

Full Circle CRM now provides support for up to thee Influence Models including support for three distinct influence models, or the same influence
model configured in three ways or a combination of two models with one configured in two ways (for those models, such as our default
opportunity model, that support multiple configurations).
Information for building and installing custom influence models is available in the Full Circle CRM Campaign Influence Plug-in SDK documentation.
Configuration
Influence model configuration is located in the Campaign Influence section of the Full Circle CRM application.

  • Go to Setup > App Setup > Installed Packages
  • Click on the Manage Package link next the Full Circle CRM Response Management Package
  • Click on the Campaign Influence button

In the Campaign Influence Models section of the page – you will now see support for three models, as well as defining if the model is the first,
second or the third influence model.
IMPORTANT NOTE: Each model needs to be configured separately. After each model is configured be sure to save the main page by clicking
the Save and return to main button, then click back into the page to configure the next model.
User-added image

The selection of the model order will determine which fields the model output is updated to within Salesforce.

Models definition and related fields
Model Name Campaign Member
Fields
Campaign Fields
Influence Model 1 Closed Op Revenue Model
Lost Op Revenue Model
Open Op Revenue Model
Influence Revenue
Influence Lost
Influence Pipeline
Influence Model 2 Closed Op Revenue Model 2
Lost Op Revenue Model 2
Open Op Revenue Model 2
Influence Revenue (model 2)
Influence Lost (model 2)
Influence Pipeline (model 2)
Influence Model 3 Closed Op Revenue Model 3
Lost Op Revenue Model 3
Open Op Revenue Model 3
Influence Revenue (model 3)
Influence Lost (model 3)
Influence Pipeline (model 3)

Field Level Visibility and Page Layout Updates

If you are using all three Influence Models you will want to insure that the correct profiles have field level visibility to the new influence fields so
that they are accessible in reports. You may also wish to place them on the Campaign Member and Campaign page layouts as needed. See
the fields referenced for model 2 and 3 in the table above.

Campaign Fields

Influence Lost (API Name: FCRM_FCR_LostOpRevenueModel1__c, Field Type: Currency) For the influence model configured as Active
(model 1) shows influenced amount from responses in this campaign related to closed-lost opportunities
Influence Lost (model 2) (API Name: FCRM_FCR_LostOpRevenueModel3__c, Field Type: Currency) For the influence model configured as
Secondary (Model 2) shows influenced amount from responses in this campaign related to closed-lost opportunities
Influence Lost (model 3) (API Name: FCRM_FCR_LostOpRevenueModel3__c, Field Type: Currency) For the influence model configured as
Tertiary (model 3) shows influenced amount from responses in this campaign related to closed-lost opportunities
Influence Pipeline (API Name: FCRM_FCR_OpenOpRevenueModel1__c, Field Type: Currency) For the influence model configured as Active
(model 1) shows influenced amount from responses in this campaign related to open opportunities
Influence Pipeline (model 2) (API Name: FCRM_FCR_OpenOpRevenueModel2__c, Field Type: Currency) For the influence model configured
as Secondary (Model 2) shows influenced amount from responses in this campaign related to open opportunities
Influence Pipeline (model 3) (API Name: FCRM_FCR_OpenOpRevenueModel3__c, Field Type: Currency) For the influence model configured
as Tertiary (model 3) shows influenced amount from responses in this campaign related to open opportunities
Influence Revenue (API Name: FCRM_FCR_ClosedOpRevenueModel1__c, Field Type: Currency) For the influence model configured as Active
(model 1) shows influenced amount from responses in this campaign related to closed/won opportunities
Influence Revenue (model 2) (API Name: FCRM_FCR_ClosedOpRevenueModel2__c, Field Type: Currency) For the influence model configured
as Secondary (Model 2) shows influenced amount from responses in this campaign related to closed/won opportunities
Influence Revenue (model 3) (API Name: FCRM_FCR_ClosedOpRevenueModel3__c, Field Type: Currency) For the influence model configured
as Tertiary (model 3) shows influenced amount from responses in this campaign related to closed/won opportunities

Campaign Member Fields

Closed Op Revenue Model (API Name: FCRM_FCR_ClosedOpRevenueModel1__c, Field Type: Currency) Closed won opportunity revenue for
primary campaign influence model.
Closed Op Revenue Model 2 (API Name: FCRM_FCR_ClosedOpRevenueModel2__c, Field Type: Currency) Closed opportunity revenue for
secondary campaign influence model
Closed Op Revenue Model 3 (API Name: FCRM_FCR_ClosedOpRevenueModel3__c, Field Type: Currency) Closed opportunity revenue for
tertiary campaign influence model
Lost Op Revenue Model (API Name: FCRM_FCR_LostOpRevenueModel1__c, Field Type: Currency) Lost opportunity revenue for primary
campaign influence model.
Lost Op Revenue Model 2 (API Name: FCRM_FCR_LostOpRevenueModel2__c, Field Type: Currency) Lost opportunity revenue for secondary
campaign influence model.
Lost Op Revenue Model 3 (API Name: FCRM_FCR_LostOpRevenueModel3__c, Field Type: Currency) Lost opportunity revenue for tertiary
campaign influence model.
Open Op Revenue Model (API Name: FCRM_FCR_OpenOpRevenueModel1__c, Field Type: Currency) Open opportunity pipeline for primary
campaign influence model.
Open Op Revenue Model 2 (API Name: FCRM_FCR_OpenOpRevenueModel2__c, Field Type: Currency) Open opportunity revenue for
secondary campaign influence model.
Open Op Revenue Model 3 (API Name: FCRM_FCR_OpenOpRevenueModel3__c, Field Type: Currency) Open opportunity revenue for
tertiary campaign influence model.

Campaign Influence Model Updates

New Date Filter Options

Added the option to filter # of days for influence either by opportunity create date or by opportunity close date. If the option of None is selected
no filters apply to the opportunity.
User-added image

Considerations:

In either case influence is calculated through Opportunity close, if the configuration is set to Opportunity create date – the historic data will not
shift (will always = X days back) but the total influence will append over time with any responses that occur between the create and close date.
If the configuration is set to Opportunity close date – as the opportunity close date is pushed out – earlier responses will be omitted from the
influence model.

New Date Filter Exception

The earliest first touch campaign response is no longer subject to the date filter – it will always be weighed for influence if the weighting is greater
than zero.
Considerations:

  • Responses that are not part of the Full Circle CRM system will not be accounted. This may be the case where there was a partial data
  • migration.
  • In the case where multiple responses associated with the first touch campaign are outside of the specified date range, only the first
  • response will be weighted.

Adjustment of additional contact role response history evaluation

It was found that when there were multiple contact roles on an opportunity that were not the originating contact or primary contact – the influence
model only evaluated one additional contact role. The selection of the contact role was random. The influence model will now weighs all responses
for all contact roles associated to the opportunity within the configured evaluation parameters.

Status Configuration Updates

Handling of the Status Mapping in the application has been revised to manage more use-cases.

Response Status on Conversion With and Without an Opportunity

Two new configuration items have been added to set the default status of the response during conversion based on whether or not the rep created
an opportunity independent of the lead status selected during lead conversion. After upgrade you will need to go into the Status configuration page
and update/save the page.
User-added image


Record Type Overrides for Setting Default Lead and Contact Status Values

The application now has the ability to define some status default values for leads and contacts based on record type. The default is to use the main
configuration for all record types. This new functionality is to allow organizations to support distinct business processes that require different
management of the lead & contact status fields.
The Lead Status field references the Standard Lead Status Field (API Name: Status) and the Contact Status field references the Full Circle CRM
Contact Status Field (API Name: FCRM_FCR_Contact_Status__c)

Lead Status Configuration by Record Type

On Contacts you can set the following by record type:

  • Initial Contact Status – on Create for a Contact in an Active Org – this will define the Contact Status value set by the system.
  • Lead Status after Response – When there is an active response – this will define the Lead Status update.

Contact Status Configuration by Record Type

On Contacts you can set the following by record type:

  • Initial Contact Status – on Create for a Contact in an Active Org – this will define the Contact Status value set by the system.
  • Contact Status after Response – When there is an active response – this will define the Lead Status update.
  • Contact Status When Converted with No Opportunity – When a contact is converted without an opportunity set this contact status.
  • Contact Status When Converted With Opportunity – When a lead is converted with an opportunity set this contact status.
  • Contact Status After Opportunity Close – Status update for originating contact when the related opportunity is closed.

Creating a record type specific override

To configure go to Setup > App Setup > Installed Packages

  • By Full Circle CRM Response Management click on the Configure link
  • Click on Status Mapping
  • In the bottom section – status Mapping Overrides click the Override button
  • The application will detect existing record types. There is a radio button at the top for Leads and Contact record types. A panel is available for each record type. Configure and save the changes for each record type requiring a deviation from the default settings – else leave the value as use default.
  • Remember to save the main configuration page to save your changes. Reviewing Record Type Status Overrides
  • After the overrides are configured you can see by column which values are not the default values – only the override values will display – if a column is blank that means the default value is referenced.

Ability to Specify From Address for Notifications

It is now possible to configure and org-wide email address as the default From User for Full Circle CRM generated notifications.
First configure an org-wide email address. View the Salesforce help document on how to do this:
https://help.salesforce.com/htviewhelpdoc?id=orgwide_email.htm&language=en_US

NOTE: The org-wide email must be configured to allow all profiles to use this email address. Configure Full Circle CRM to reference the org-wide
email address

  • Go to Setup > App Setup > Installed Packages
  • Click on the Manage Package link next the Full Circle CRM Response Management Package
  • Click on the Notifications button
  • In Notification source address select the org-wide email address you want to use, and click the update notification source address button

User-added image


Background and Future Operations Specified User via Email Service

The Response Management application performs a variety of background and asynchronous tasks. The decision on what operation to perform
often takes place during a trigger – and, that trigger, can be launched by any user in the system. As a result, some of these operations will by
default appear to come from random users (because a batch operation or asynchronous operation run in the context of the user that launched
the operation). That can lead to confusion in the audit fields where users seem to be performing operations that they shouldn't be allowed to
perform (while in fact, it's our application doing so under their user context).
To avoid this potential confusion, you can have the background and asynchronous Response Management Application operations run under the
context of a user that you define. To do so, you must do the following:

  1. Define an Email service using Setup-Develop-Email Services
  2. You may give the Email service any name you wish.
  3. For the Apex class, specify FCRM.FCR_InboundEmailHandler
  4. Accept Attachments to None
  5. Uncheck "Advanced Security Settings"
  6. Leave Accept Email From Blank
  7. Uncheck convert text attachments to binary attachments
  8. Check the Active checkbox
  9. For the Failure Response settings, set all of the actions to "Discard Message"
  10. Uncheck enable error routing & leave email address blank

Next, create a single new Email Address for this service.

  1. Specify any Email address you wish
  2. Check the "Active" checkbox
  3. Select the context user that you wish to run the Response Management application background and asynchronous operations.
  4. Clear the Accept Email From box.

User-added image
You can confirm that your Email service is configured correctly on the main configuration page of the Response Management Application.

The application will automatically use the Email address and service that you have defined.

When you use Email services with our application, the frequency of background operations is reduced in order to reduce the possibility of
exceeding your organizations Email limits. As a result, certain background operations may take longer than otherwise.
Should you exceed Email limits, or other failures occur in the email service, the application will fallback to the default operation and perform
the background or asynchronous operation in another user context.

Deal Explorer – BETA

Overview

The Deal Explorer is a new functional area, currently in Beta, of the Full Circle CRM Application. It is used by Sales and Marketing teams to
review what Campaign responses and activities impacted an opportunity. The Deal Explorer can be used for reviewing Open, Won and Lost
Opportunities.
A couple of important notes:

  • The Deal Explorer references the Opportunity close date in how it renders Campaign response and Activity information – so you’ll want to be sure that the close date is accurate.
  • The Deal Explorer requires configuration and the addition of the Deal Explorer button to the opportunity layouts where you want the functionality available. See the Deal Explorer Implementation Section in this document for detailed information

Deal Explorer Tour

Accessing the Deal Explorer

You get to the Deal Explorer from the Opportunity page layout. Select the Deal Explorer button at the top of the page. The button will only be
visible if your System Administrator has enabled it for the page layout you are viewing:

User-added image

Top Panel
The top panel displays default data about the Opportunity. This section can be configured to display different fields. See the configuration
section of this document. Below is a screenshot of the default fields displayed.
User-added image

The Originating Contact is the Contact record that originated the Opportunity – the Originating Contact may or may not remain a contact role
on the opportunity by the time the Opportunity is closed.
Fields with null values in the top section are not displayed.
The Return to Opportunity Button returns you to the Opportunity page layout.

Explorer Panel & Tabs

The next section contains three tabs, which display different data:

Profile Listing Tab

This tab displays all Campaign responses and activities related to contact roles within the configured parameters.
The Type column displays Campaign for all Campaign Responses and will display the Event or Task value for the standard ‘Type’ Field on those
objects. In cases where the ‘Type’ field is not set, the system will display either ‘Event’ for events or ‘Task’ for tasks. The Columns are sortable.

User-added image

Campaign Influence Tab

This is real-time processing of whatever influence models you have active in the system based on this opportunity only. Please see the Data
Considerations Section for more information.

User-added image

Visualization Tab

This section will display how the Campaign Responses and Activities fell into the progression of the opportunity – from Pre-opportunity to
Opportunity Close. Please see the Data Considerations Section for more information.

User-added image

Deal Explorer Data Considerations

This section is a bit in the weeds but it’s important to understand how the Deal Explorer evaluates and displays data:

Contact Role Dependencies

The Deal Explorer looks at Campaign responses and Activities related to Contact Roles on the Opportunity. As Contact Roles on the opportunity
are added or removed, the data will adjust. Note also that the Originating Contact Campaign Responses and Activities will not be evaluated if
they are not also a Contact Role on the Opportunity.

Campaign Response Display

Campaign responses included are those that have been processed by the Full Circle CRM System as indicated by having a Response Date
(FCRM_FCR_Response_Date__c) populated on the Campaign Member record. Data displayed will be impacted by how far back you set the date
parameter in configuration for display responses, how long you’ve been using the application and, if you are new to Full Circle CRM, whether or
not your organization has migrated historic data within the configured date range in configuration.

Activity Display

Activity display is based on the Due Date – this is a Date field and defaults in display to the earlier stage for that date. For example, if an activity
is created on the same day an opportunity is created – the activity will display in the pre-opportunity timeframe because we are unable to determine
the time relative to opportunity create. Same for opportunity stage progression done on the same date – the Activity will be associated to the earliest
stage achieved that date.
Only activities with a related contact will be displayed. Activities related to the opportunity that are not also related to a contact on the opportunity
are not included.

Influence Metrics Display

Influence metrics will not match the influence metrics the application pushes up the responses during the batch process

  • Influence metrics are run real-time (those pushed to the response are a batch process and will not reflect the latest data until the batch is run or manually updated)
  • Influence metrics only evaluate that specific opportunity (those pushed to the response evaluate any relevant opportunities that the response has influenced)
  • Display is available for all three models but will only display for models active in the system

Deal Explorer Implementation

Implementation consists of three steps – Configuration, setting profile permissions and adding the Deal Explorer button to the Opportunity page layout.

Configuration

The Deal Explorer is configured from the Data Explorer button in Configuration:

  • Go to Setup > App Setup > Installed Packages
  • Click on the Manage Package link next the Full Circle CRM Response Management Package
  • Click on the Data Explorer button
Event Exclusions

On the left you can select event types to exclude from the Deal Explorer display – these are defined by the standard event ‘Type’ field. You can use
‘Event’ to filter out any events where the ‘Type’ field value is not set.
User-added image


Task Exclusions

On the right you can select task types to exclude from the Deal Explorer display – these are defined by the standard task ‘Type’ field. You can use
‘Task’ to filter out any Tasks where the ‘Type’ field value is not set.

User-added image

Days from Opportunity Create

Only responses and activities that take within this number of days prior to the opportunity create date, or between opportunity create and close, will
be displayed. Leave blank for no date limits.

Top Panel Display Via Field Sets

You can configure what opportunity fields are set on the left and right columns of the top panel of the Deal Explorer with the use of Standard
Salesforce Field Sets.
Salesforce help reference for field sets:
https://help.salesforce.com/htviewhelpdoc?id=fields_about_field_sets.htm&language=en_US

To Create Opportunity Field Sets go to
Setup > App Setup > Opportunities > Field Sets
Create field sets for each column you want to replace. Ideally name them by left or right panel so they are easy to reference later

User-added image

After the field sets are configured you can select them in the configuration page. If a value of None is displayed in the field set picklist value – the
default Deal Explorer fields will display.

User-added image
Be sure to Save the page after configuration by clicking on the Save and return to main Button.

Profile Permissions

Insure profiles accessing the deal explorer have permission to the Deal Explorer VisualForce page (FCRM_FCR_VFDealExplorer)
For Non-Administrative users remove permission to the following VisualForce pages: FCRM.FCR_VFDataExplorerConfig

Enable Deal Explorer Button

Add the Deal Explorer button to the Opportunity page layouts from which your users will access the Deal Explorer.
Setup > App Setup > Opportunities > Page Layouts Edit the page layout
In the Buttons section select the Deal Explorer button and drag it to the Custom Buttons section, Save.

User-added image

Global Passive Org Active Response Timeframe Functionality

Overview

In Global Passive Orgs – this functionality allows users to set the default status value of a Lead or Contact on creation. It also will sync a new
Campaign Response that meets the score threshold as active to the Lead or Contact within a given timeframe.

Before and After

  • Prior to this functionality all Leads & Contacts had a status value reset to the default status value even if a rep selected a different value before saving the record.
  • Prior to this functionality a rep could go and update the Lead or Contact status to an Active status – but any Campaign Associations created would be set to Resolved - Already Engaged if at score threshold.

This functionality was designed to support the following

  • Allow reps to define the default status value when creating a Lead or Contact
  • Within a defined timeframe, enabling the system to set the first Campaign Member that is associated to those Leads or Contacts, and within the score threshold as the Active responses in order to have complete response metrics.

NOTE: Status configuration is defined on the Full Circle CRM Status Configuration page.

  • Active status is the status value defined as active in the Status Mapping
  • Default Lead and Contact Status on Create values are configured on this page as well

Possible Use Cases

There may be a trigger associating a Campaign post-save based on Lead or Contact criteria, or there may be a manual association to a Campaign.
Prior to this functionality those campaigns would be set to ‘Resolved - Already Engaged’, but with this functionality they would be set to active
and the Campaign Member Response Status field will match the Lead or Contact Status.

Scoring Considerations

If you want to leverage this functionality you will want to insure that the score threshold is met in order to associate the incoming response properly

  • This is not a concern in an org that has a threshold of 0
  • Campaigns associated through the response prompt UI are always assumed to be at score threshold
  • You may want workflows to set the threshold score for Leads and Contacts created by sales reps
  • You may want to leverage Campaign-bases scoring if you are using a campaign trigger to insure those Campaigns come in at threshold.

Functional Parameters

The following parameters apply to this functionality.

Global Passive Mode Only

The following functionality is only applied to organizations running in Global Passive Mode. This is a setting located in the General Configuration
Section of the application. In global passive mode there are no ‘Active Users’ which means that no users are required to have an active response
in order to update a lead/contact status from active to inactive, or to create an opportunity.

User-added image

Repeat Response User Created Records Excluded

Records created by a repeat response user are exempt from this functionality. Typically the Repeat Response User is also the Marketing
Automation user. Repeat Response users are defined in the Full Circle CRM Response Processing Configuration Section.

Profiles and Users Overrides

In the Response Processing Configuration Page you can define users and profiles exempt from this functionality.

  • They will not be able to create a lead/contact with a status value different than the one defined as default on create. They can still update the status to an active status after that initial save.
  • There will be no timeframe applicable to inbound responses which will set them to active and sync the Response Status to the Lead or Contact Status
  • Active Response Timeframe
    An Active Response Timeframe greater that 0 (in minutes) must be defined for this functionality to be active. Timeframe is a global setting and applies to all except repeat response users and user/profiles exempted through timeframe overrides.

Configuration

To configure this functionality:

  • Go to Setup > App Setup > Installed Packages
  • Click on the Manage Package link next the Full Circle CRM Response Management Package
  • Click on the Response Processing button

In the Active Response Timeframe and Overrides Section

  • Set the Active Response Timeframe – this is in minutes. A value of 0 will disable this functionality
  • Define any users or profiles you may want exempt from this functionality in the Timeframe Overrides section
  • Be sure to Save the page by clicking the Save and return to main button.

User-added image

Localization Support for Response Prompts

Response prompts reference the picklist to do campaign association that is displayed on the lead or contact page layout in the Response
Information section of the page.  user Locale setting, and secondarily bases on the user Language setting. Localization requires the
association of Labels to each response prompt and then the customization of the Taxonomy file to support the Language or new Labels.

The text for the response prompts can now be localized. Language display is fist set based on the user Locale setting, and secondarily
bases on the user Language setting. Localization requires the association of Labels to each response prompt and then the customization
of the Taxonomy file to support the Language or new Labels.

User-added image

Creating Response Prompt Labels

  • Go to Setup > App Setup > Installed Packages
  • Click on the Manage Package link next the Full Circle CRM Response Management Package
  • Click on the Response Prompts button

In the Taxonomy Labels text fields define the taxonomy labels – these will be used as you modify the taxonomy file
Be sure to click the Save and return to main button to save your changes.

User-added image

Update the Taxonomy File

Edit and update the taxonomy file to support the language. Detailed information on updating the Taxonomy file can be found in the Full Circle
CRM Taxonomy guide.
Salesforce Help file for language support and Language codes:
https://help.salesforce.com/HTViewHelpDoc?id=faq_getstart_what_languages_does.htm&language =en_US&release=180.7

Upload and Associate the Taxonomy File

Upload the Taxonomy guide as a static resource or update the existing taxonomy resource.

  • Go to Setup > App Setup > Develop > Static Resources
  • Either Edit the existing Taxonomy file and save, or create a new one.

For new Taxonomy files:

  • Go to Setup > App Setup > Installed Packages
  • Click on the Manage Package link next the Full Circle CRM Response Management Package
  • Click on the General Configuration button
  • Select the Taxonomy file from the Taxonomy Definition drop down
  • Click on the Save and return to main button

New API Functions

The following API Functions are now available. Reference the API Extensibility Guide for full details

  • IsPassive – Determines if a specified lead or contact is processed in active or passive mode.
  • IsNonResponseByRecordType – Determines if a specified lead or contact is not a response based on record type.
  • GetCurrencyConversionMap – Retrieves a map of currency conversion values.
  • TreatNextCamapignAssociationsAsResponsePrompts – When creating a CampaignMember programmatically causes the new CampaignMember to be treated as a response prompt campaign.
  • IsLeadOrContactStatusActive – Determines if a specified status is active.
  • PerformResponseSync – Performs a sync operation from a lead or contact to the active response.

Installation & Deployment

Install the new release over the existing application – this will upgrade the application. After installation make the following changes:

Application Updates

In Status Configuration set the value for the following two new fields.

  • Response Status after conversion with opportunity
  • Response Status after conversion without opportunity

Note, this value will be pre-populated during the installation – if the values are correct, just save the page to activate them.

End User Profile Updates

Insure profiles accessing the deal explorer have permission to the Deal Explorer Visualforce page (FCRM_FCR_VFDealExplorer)

For Non-Administrative users remove permission to the following Visualforce pages: FCRM.FCR_VFDataExplorerConfig
FCRM.FCR_VFOverrideDefaultStatusMappings
Optional: Set the following Object to Read Only: Deferred Update Items

Administration User Profile Updates

Insure administrative profiles accessing the configuration section have permission to the following VisualForce pages

  • The Deal Explorer Configuration Visualforce page (FCRM_FCR_VFDataExplorerConfig
  • The Status Mapping Overrides Configuration Page (FCRM_FCR_VFOverrideDefaultStatusMapping)

Optional Configuration

  • Set up Email service configuration – instructions are available later in this document.
  • Setup Notification source address
  • Put the Campaign Influence fields for model 2 and 3 on the Campaign Member and Campaign page layouts
  • Enable the Deal Explorer button on opportunity page layouts (See Deal Explorer section for more information)

Business Process Updates

This version of the application will clear the Lead and Contact Nurture Timeout fields (FCRM_FCR_Nurture_Timeout__c) when the Lead/Contact
is re-opened. Prior to this release, your organization may have workflows to clear these fields. If so, you can disable them.
Note: do not disable workflows clearing those fields for reasons other than the lead or contact being re-opened.

  • Was this article helpful?