Sales Enablement Release Notes | V 7.0.0 October 26, 2026
It's also required for two Engagement Hub 3.16 features: Enhanced Nexus-to-Salesforce Engagement Synchronization and Salesforce Custom Account and Opportunity ID Support.
Before you start
- Who can use it: Salesforce admins upgrade and configure the package. Salesforce users see the date and time improvements automatically.
- Action required: Upgrade the Nexus Sales Enablement Hub package in Salesforce to version 7.0 REST integration is optional, and your current SOAP integration keeps working until you choose to switch.
- Where to find it: In Salesforce, Nexus Package Setup > Nexus Configuration
Heads up: When you turn on Enable REST Integration, the package uses REST connections only. It doesn't fall back to SOAP. Set up and check your Nexus REST connections before turning on REST integration, or Request an Engagement and other Nexus actions in Salesforce will stop working.
What's included in version 7.0?
- REST API integration: the main Salesforce-to-Nexus actions can use REST APIs instead of the older SOAP services.
- Multiple Nexus REST connections: connect one Salesforce org to more than one Nexus instance using REST.
- Custom Opportunity ID support: keep using your own Opportunity identifier while Nexus still receives the standard Salesforce record ID.
- Engagements without an Account or Opportunity: Salesforce can now receive Engagements from Nexus that have neither.
- Dates and times in each user's locale and time zone on the Engagement header.
- Correct times for time zones with partial-hour offsets, such as UTC+05:30 and UTC+05:45.
How do I upgrade to version 7.0?
Your Salesforce admin installs the version 7.0 upgrade of the Nexus Sales Enablement Hub package in your Salesforce org. Your existing SOAP connections and settings are kept, so the integration keeps working the same way after the upgrade.
After upgrading, decide whether to switch to REST integration (see below). The date and time improvements and the standard Opportunity ID work automatically, with no setup.
How do I switch to REST integration?
Set up at least one Nexus REST connection in Nexus Package Setup, then turn on Enable REST Integration.
- Upgrade the package to version 7.0.
- In Salesforce, open Nexus Package Setup > Nexus Configuration.
- Under Nexus REST Connections, set up a connection for each Nexus instance you use.
- Check that the Nexus instance and client details are correct for each connection.
- Turn on Enable REST Integration.
[SCREENSHOT: Nexus Package Setup > Nexus Configuration showing Nexus REST Connections, Nexus SOAP Connections, and Enable REST Integration]
With REST integration on, these actions use REST:
- Request an Engagement / Request a Briefing
- Adding or removing a Visit Account, Visit Opportunity, or Visit Attendee
- Opening Nexus Engagement Hub from Salesforce, including sign-in and requester validation
Your SOAP connections aren't removed or converted. If you turn off REST integration, the package goes back to using SOAP.
How does version 7.0 work with more than one Nexus instance?
Admins can set up several Nexus REST connections. When a user requests an Engagement or opens Nexus from Salesforce, the package picks the right Nexus instance automatically, or asks the user to choose.
- If there's one applicable Nexus connection, it's selected automatically.
- If there are several, the user selects the Nexus Instance before continuing.
- REST and SOAP connections are never offered together in the same selection.
- Each Engagement remembers its Nexus instance, so later Account, Opportunity, and Attendee updates, and links from those records, go back to the right Nexus instance.
[SCREENSHOT: Nexus Instance selection when requesting an Engagement]
How do custom Opportunity IDs work in version 7.0?
The package now sends Nexus two separate Opportunity identifiers: the standard Salesforce Opportunity ID, and your own custom Opportunity identifier.
- OpportunityId always contains the standard Salesforce Opportunity record ID. It's filled in automatically and can't be changed in field mapping.
- OpportunityNumber uses your existing field mapping, so you can map it to your organization's own Opportunity identifier.
This applies to Request an Engagement, Opportunity updates, and Automatic Opportunity Attribution. Account identification works the same as before. The standard Salesforce Account ID is still kept separately from your configurable Account identifier.
To map your custom Opportunity identifier, use Nexus/Salesforce Field Mapping > Opportunity Fields. No mapping is needed for the standard OpportunityId.
To use custom IDs in Nexus, see Salesforce Custom Account and Opportunity ID Support.
Can Salesforce receive Engagements without an Account or Opportunity?
Yes. With version 7.0, Salesforce accepts an eligible Engagement from Nexus even when it has no Account or Opportunity. Before version 7.0, the package rejected these Engagements.
- If there's no Account, no Visit Account relationship is created. If there's no Opportunity, no Visit Opportunity relationship is created.
- Other Engagement information syncs as usual, and Engagements that do have Accounts or Opportunities work the same as before.
- There's no Salesforce setting for this. The matching setting is turned on in Nexus. See Enhanced Nexus-to-Salesforce Engagement Synchronization.
Why do Engagement dates and times look different after the upgrade?
The Engagement header in Salesforce now shows dates and times in each user's own Salesforce Locale and Time Zone. It no longer uses a fixed DD/MM/YYYY format.
- Users in different regions see the same date in their own regional format.
- Users in different time zones see the same time converted to their own time zone.
- Only the display changes. The stored value and the value received from Nexus don't change.
[SCREENSHOT: Engagement header showing a date and time in the user's locale]
What changed for time zones with partial-hour offsets?
Version 7.0 fixes Engagement start and end times for time zones whose UTC offset includes minutes, such as UTC+05:30 (India) and UTC+05:45 (Nepal). Before version 7.0, these offsets were rounded to the hour, which could make an Engagement time off by 30 or 45 minutes.
Times now keep minute-level accuracy, and the date stays correct when a conversion crosses midnight. Time zones with whole-hour offsets aren't affected, and no setup is needed.
What should I know about version 7.0?
- Upgrading to version 7.0 doesn't switch you to REST. Your SOAP integration keeps working until you turn on REST integration.
- Once REST integration is on, the package doesn't fall back to SOAP if a REST connection is missing or not working.
- The Salesforce Custom Account and Opportunity ID and Enhanced Engagement Synchronization features also need your Nexus environment on Engagement Hub 3.16 or later, with the matching Nexus settings turned on.
Frequently asked questions
When is version 7.0 available?
The Nexus managed package for Salesforce version 7.0 is expected in Q1 2027. We'll let you know as soon as it's available.
Do we have to switch to REST integration?
No. REST integration is optional. Your SOAP integration keeps working after the upgrade until you choose to turn on REST.
Will upgrading change our existing integration?
No. Your SOAP connections and configuration are kept. The only automatic changes are the date and time improvements and the standard Opportunity ID being sent to Nexus.
Why did Request an Engagement stop working after we turned on REST integration?
With REST integration on, the package only uses REST connections and doesn't fall back to SOAP. Check that a Nexus REST connection is set up with the correct instance details in Nexus Package Setup > Nexus Configuration, or turn off REST integration to go back to SOAP.
Do we need to map the standard Salesforce Opportunity ID?
No. The package fills in the standard Opportunity ID automatically. Only map OpportunityNumber if you want to send your own custom Opportunity identifier.
Do we need version 7.0 to use the new Salesforce features in Engagement Hub 3.16?
Yes. Enhanced Nexus-to-Salesforce Engagement Synchronization and Salesforce Custom Account and Opportunity ID Support both need version 7.0.
Need help? See How do I contact Nexus Support?.