SmartCloud Connect Latest Release Notes and Knowledge Base Updates¶
1905 release notes (notable improvements and changes)¶
General Improvements and New Features¶
1. The Admin function of setting the initial (default) customization to be applied for SmartCloud Connect users by default (also after customization reset) was implemented. Default customization can be bulk-set by the local admin for a specific Org, tenant, or instance.
2. Customization management stability increase: fixed a rare issue that was causing customization settings corruption for some users.
3. SCC deployment Admin authentication in Azure now uses a special secure key instead of Admin login and password, so the recurring 90-day password expiration does not affect deployment in any way.
4. Now, when a single field is prefilled by either two or all of the three existing prefilling mechanisms, there is an established priority defining which prefilled value prevails [listed from higher priority to lower priority]:
Prefilling of default values set by SCC Sync
Default values defined by Salesforce (e.g. default picklist items)
In addition, now any prefilled field value can be modified through SmartCloud Connect by the users.
6. Meeting Scheduler improvement, “focused availability”. Now it is possible to set specific days of the week and specific time spans for building “Book me” (Share my availability) tables, for example to delimit regular business hours. The default working days and office hours are retrieved from the user’s Exchange/Office 365 calendar settings.
7. A special Salesforce view (filter) setting was introduced to the Contacts/Leads autoresolving mechanism in order to make it possible to use the same email address for several Contacts or Leads on autoresolving, when that is required – e.g. when the same email address is assigned to different territories/products within a big Org. The Global setting is SalesforceContactResolveToMultiple.
8. Added a new Global setting managed by Invisible support team, CalendarAvailabilityTerm. It defines the time span in the future over which a user’s calendar availability is parsed; it is set to 365 days by default.
9. Implemented a Global setting SalesforceEmailDeduplicationDepth which allows to define the span in the past over which deduplication is applied on emails sharing – this allows preventing the sync issue “Throttling error. Failed to receive http response. The operation timeout” on syncing a vast number of emails with Salesforce Enhanced Email enabled. By default, it is set to 30 days.
10. SCC Adaptive view improvement: now the Sidebar’s scroll position on the home and search screens is kept after you navigate to another screen and then return.
11. Meeting Scheduler’s Calendar availability (“Book me”) feature improvement: now attendees selection suggestions are also fetched from among Salesforce Users, Leads, and Person Accounts (if they are enabled), besides Contacts.
12. A standard reCAPTCHA anti-bot check was introduced on accessing the Calendar availability time slots reservation webpage to prevent calendar spamming activities.
13. Add-In Refresh feature improvement: now, after the Refresh button is clicked in the Sidebar’s menu, Salesforce metadata used by the Add-In also gets refreshed.
14. “Book me” (Share availability) feature improvement: now internal (in-org) email addresses can be added to the list of attendees in Meeting Scheduler; their availability also gets parsed from Exchange/Office 365 and is then merged so the recipients receive the overall merged availability table, considering other internal attendees’ unoccupied spans besides the organizer’s.
15. To reduce user interface cramming, now the checkboxes for marking records to be linked to a shared item on the Add-In’s home screen and search results screen are only shown when the user hovers mouse over a record.
16. Now ROI study and Health status data can be exported to a .CSV file, which allows monitoring their dynamics over time - these indicators can be used for building efficiency reports and decision-making.
17. Implemented a “Maintenance page” to be displayed during product downtime.
18. The Engagement panel (formerly MagicPixel) feature is to be disabled for Enterprise customers who never use it.
19. [Desktop implementations] Small optimization: now single-use SCC sync encryption machine keys get deleted after use.
20. Introduced a “Magic Anchor” mechanism that allows proper autolinking of emails sent from Salesforce.
1. Now it is possible to link emails shared using the Save button in the Add-In in Read mode to Contacts and Leads in Orgs using Salesforce Enhanced Email, as designed. In addition, several Contacts/Leads can be selected to be linked to a shared email. Also, now re-sharing (saving of an email afresh, linked to other objects) of emails with Leads and Contacts works properly in configurations with Salesforce Enhanced email enabled.
2. Appointments shared in Salesforce no longer get deleted from MS Exchange/Office 365 after they move out of the sliding time window (two weeks in the past, two months in the future from present moment), if the corresponding Global setting ServiceEventDeletionStrategy is enabled.
3. Fixed an issue which caused email duplicates creation in Salesforce under specific circumstances, when sharing a Sent email over sync.
4. Essential Chrome Extension fixes: the SCC Chrome Extension for Gmail is now fully functional – both emails handling and events handling is properly carried out for different use cases.
The update also includes a number of other bugfixes, back end and front end optimizations, minor UX/UI tweaks, etc.
SmartCloud Connect Engagement panel (Magic Pixel revamped)¶
1. Magic Pixel aka Track email opens (now expanded as the Engagement tracking panel) improvement: implemented the possibility for the users to mark specific correspondence threads or email domains to receive instant notifications upon email opening (optionally, a set number of openings) or link clicking by contacts in these threads/domains. In addition, there is an option to temporarily prevent these notifications from appearing. Notifications on email openings/link clicks are displayed as toast popups.
2. [Desktop implementations] now the tracking code is inserted at the end of an email message (and it is not displayed).
[Cloud implementations] the tracking code inserted into emails is no longer displayed as a blinking pixel; it also reserves no space in the message’s body.
3. SCC Classic view’s MagicPixel was now also replaced with Engagement panel.
4. [Desktop implementations] inserting the tracking code into messages no longer causes corruption of email text.
5. The Engagement panel was optimized for extra performance, now it opens and retrieves engagement data faster.
6. Implemented key hover-on tooltips for Engagement panel controls.
7. Fixed an issue that prevented tracking code insertion when SCC sync was disabled or paused.
8. Introduced a counter of new recipient(s) interactions with the sent message (email openings) in the Engagement panel - displaying in the bottom toolbar of the number of notifications which have not been viewed by the user.
9. Increased usability of the view openings statistics table entries’ sort order: now the latest openings data is displayed on the top of the list, older sink to the bottom.
10. Increased Engagement panel items display consistency, by introducing a fixed number of records per section to be shown (10).
11. Now clicking on an Engagement tracking thread’s subject opens the latest email in this thread in inspector mode, as designed.
Knowledge Base Updates¶
- Return on Investment and Health Status Admin panel tabs explained
- Engagement panel explained
- Managing MS Outlook Tasks with SCC
- How to properly add custom objects to SCC handling scope
- How to create a custom Salesforce list view to see closed Opps/Cases
- Troubleshooting article: what to do if SCC icons are greyed-out in MS Outlook
- The articles which deal with troubleshooting matters were moved to the dedicated TROUBLESHOOTING category in KB articles structure
- The article on Initial Search was revised and improved
- Other revised/updated articles: