Gen 2: Nexus Sales Enablement Hub App Installation

Purpose:  This package will allow account managers to initiate a visit request from the Account or Opportunity object within Salesforce, and pass all related account, opportunity and contact information from SFDC to and auto-login the user to complete a visit request.

Note:  If this is a 1^st time installation, please include your Executive Briefing Center contact and a contact during this installation process, to ensure that there’s a common understanding of the fields being mapped on both sides of the interface.  The Briefing Center contact will also be able to identify the “briefing center” terminology to be used when customizing the sidebar link and the “Request a Visit” buttons.

Here’s an example of a Salesforce system with the Interface package installed:

Step 1: Install the Package

You can easily install the "Nexus Sales Enablement Hub" app from the AppExchange by following the provided instructions.

Once getting to the following screen:

• enter the Installation key (ask Team for this key if you do not have it (support@nexuscenter.io)
• select “Install for Admins Only” and click the “Install”/"Upgrade" button.

Step 2: Assign Permissions (Setup - Permission Sets)

List of the permissions (access to standard Objects and the fields):

Read access to all of these fields is required for all users who will be requesting briefings:

Opportunity, Contact, Account objects:

-- all fields you specifically mapped in this package

-- Account owner field, and Id, FirstName, LastName, Email.

-- Primary Contact field on Account

-- Name, Title, Phone, and Email on the Primary Contact

-- On the Opportunity, access to Name, StageName, CloseDate, Amount, AccountId

Read/Write permissions:

Event

Permission Sets:

For your convenience, we have included 4 permission sets in the package

1. Nexus Administrator - provides full access to all features of the UI.

2. Nexus User - provides access to all features of the UI except the field mapping screens and the package configuration screen.

   The Nexus User permission set should be assigned to: 1) all users who will be requesting visits from Salesforce, and 2) all account, opportunity, and contact owners

3. Nexus Api Access - grants API Enabled and and Apex REST Services system permissions. Should be combined with either 1 or 2 above depending on the org security preferences. It really can be either though. Allows making callouts and also has access to REST services. If clients configure the integration from the admin side, the user will also be able to receive requests from the backend.
4. Nexus Developer - combines permissions of the 3 permission sets: Administrator, User and Api Access.

Step 3: Setup Package

Once the package is successfully installed, search for Package Setup in the app launcher.  Or, select setup and then Package Setup.

Click the (1) Edit button to edit an existing connection or click on (2) Add Nexus Connection button to create a new connection. 

You may link to multiple instance of Nexus from Salesforce.

Fill in the Nexus Configuration screen, with the data below, and Save.

The Service endpoint will change depending upon whether the new technology can be successfully linked to Salesforce or whether we have to revert to an older technology.

For testing the interface in your SF sandbox, link to your BETA website(s) by using this information:

Nexus Connection Info:

'Request a Briefing' Button Label: 

This button resides on the visual force page that and is the final action in Salesforce to send all the account, opportunity and contact data associated with this visit request to and transition the users into the website to complete the visit request there. The button is preset to “Request a Briefing” but you can re-label it to any label that makes sense for your program.

Don’t Require Opportunities for Visit:  If your Executive Briefing Program wants to allow account managers to request visits in the center WITHOUT requiring that they identify an opportunity associated with the visit, then check the box.  If an opportunity MUST be associated with each visit request, then leave the box unchecked.

Show Opportunity Search:  When a SF user initiates a visit request for a specific account, all the opportunities associated with that account are listed so that the user can select which one(s) are associated with the visit.  The Show Opportunity Search option is useful if there are so many opportunities on file for an account that it would be difficult to find what you’re looking for.  If this option is turned on, the user can search by opportunity name, stage, or close date, to filter the list of opportunities.

Default Opportunity Stages:  All opportunities associated with an account will be available for selection during the visit request.  This pick list allows you to limit the initial display of available opportunities to those with the specified opportunity stages (e.g. eliminate closed opportunities from the list).  During the opportunity selection process, the account manager will be able to reset the filter to show any and all stage(s), if the Show Opportunity Search option is turned on.

VisitData Amount Field Option:  The Opportunity Amount field is the default amount field included in the display of all the opportunities associated with an account.  This setting lets you change that display field or omit it from the display.  Most likely, you’ll want to leave the default.

(Remember to click Save after all fields are filled in.)

Automatic Updates Settings: These settings let you configure if and how frequently Nexus custom objects (Visit Account, Visit Opportunity, Visit Contact) are synchronized with the standard Salesforce objects they correspond to. This update process is critical to drive accurate date in the Engagement Object and in the Nexus Engagement Hub itself.

Schedule Batch Updates: Schedules the job for batch updates if checked

- Recommended that you check this box

Run Updates Every (hours): Sets the frequency for how often the batch update job runs.

- Recommended that you set to 12 hours so this will sync twice per day.

Step 4: Add Buttons in Account & Opportunity Page Layout

The managed package creates 2 new buttons that are used to initiate a visit request. One is available in the Account object and the other in the Opportunity object.

Go to Setup > Objects & Fields > Object Manager > Account / Opportunity > Page Layouts

Add the ‘Request a Briefing’ Button to the ‘Custom Buttons’ Section of the page layout that your sales team uses.

This needs to be done for both the Opportunity & Account Page Layouts.

Instructions to Edit the ‘Request a Briefing’ Button Label

Step 5: Configurate Salesforce → Field Mapping

*Your Briefing Center Contact and contact will be needed for this step

1. Go to the App Launcher - Nexus/Salesforce Field Mapping page.

   Set up mapping for the following three objects: Accounts, Opportunities, and Contacts.

   • Accounts - Sales Channel (Segment and Region) fields: These fields are hierarchy fields, so they must be mapped to related in fields in Salesforce. AccountSalesChannel-Level1(Segment) is the higher level field and AccountSalesChannel-Level2 (Region) is the sub-field within each Segment.
   • Opportunity - Potential Revenue: The briefing centers typically want to know the total revenue expected from an opportunity and not the revenue quantified by the stage/probability of the opportunity.  For example, if an opportunity is worth $10,000, and the stage/probability is 50%, the EBC will want $10,000 and not $5,000 passed in the interface as the expected revenue for this opportunity.  For that reason, for the screen field identified as “Potential Revenue”, you may need to map the Amount and not the Expected Revenue field (or whatever the equivalent field is in your Salesforce system).
2. For any field that you do not want to be populated from Salesforce, simply select “- No Mapping -“. 
3. Click Save between switching tabs to make sure your mappings are saved. 
4. Send Screenshots of Field Mapping to Contact - If the contact was not on a working session with you to setup field mapping, please take screenshots of each field mapping tab and send to your contact. Thanks!

Based on the configured mapping, the selected Salesforce field values will be saved to the following Engagement Hub fields:

Accounts

Contacts

Opportunities

Step 6: Installation and Initial Configuration is complete!

Before testing the interface, you’ll need to provide Customer Service with the Organization ID of your Salesforce instance.  This needs to be stored on the side for authentication.

Step 7: Test the Interface

To test the interface, navigate to the Accounts tab or Opportunity Tab and choose a customer account. You should see the Request a Briefing button.

When you click it, you will be navigated to the visual force page, allowing you to select the opportunities associated with the visit and the customer contacts (Attendees) associated with the visit. 

Click the ‘Request a Briefing’ button at the bottom of the page and you should be automatically logged into and land on the first page of the request form.

Step through a full request and you should see the Account (Customer) screen, Opportunity screen, and Attendees screen pre-populated with the data selected and fields mapped from Salesforce.

Step 8: Enable data to be sent to Salesforce

If your program would like to have Data sent up to Salesforce to provide better visibility of customer engagements within Salesforce and empower SF reporting, this document provides next steps to enable this next level of integration between and SFDC: link