Component types
Acoustic Campaign's Salesforce CRMi Package adds the following Component types:
|
Apex Classes |
Visualforce Pages |
Custom Objects |
|
Custom Fields |
Validation Rules |
Tabs |
|
Buttons\Links |
|
Static Resources (JS\CSS) |
View components
Components can be reviewed during and before installation by the Salesforce Admin using the package link.
- Click on View Components
-
Installed Packages, use Setup > Quick Find/Search to look for "Installed Packages."
- Click on the Package Name to View Components and additional details like:
- Version Number (current)
- Modified By and date (when the current version was installed)
- First Installed Version Number
- Installed By and date (first install)
List of past version notes
<td">1.18<td">Summer 2013<td">Send Silverpop Email Personalization breaks the send screens. Mailing cannot be sent.</td"></td"></td">
|
Package version |
Released |
Issues addressed or updates made |
Package link |
|
2.2 |
March 2022 |
Component and object label names changed from Silverpop to Acoustic. Namespace Prefix is still "Silverpop." Contact Insight components updated to use API version 52. |
Package |
|
2.1 |
Jan 2022 |
Salesforce API upgrade for Apex and Visualforce components. |
|
|
1.30 |
Spring 2020 |
Send Acoustic Campaign Email Button to work for Salesforce user who does not have the View Setup and Role Configuration permission in their role. |
|
|
1.29 |
Spring 2019 |
The send Silverpop Email button is unavailable in the campaign object and Person account. |
Outdated – open CRMi Support case if needed.
|
|
1.27 |
Winter 2017 |
Lightning Experience Compatibility, Blank screen is displayed while sending mail from the Lead or Contact |
|
|
1.25 |
Spring 2016 |
Updated Globalization to include French, German, Simplified Chinese, Japanese, Spanish, and Brazilian Portuguese. |
|
|
1.24 |
Summer 2015 |
Read timed-out error with Large Campaigns. |
|
|
1.23 |
Spring 2015 |
Updated XmlApiUrl URL functionality to require format https://api(pod number).silverpop.com/XMLAPI |
|
|
1.21 |
Fall 2013 |
A wrong Subject line was used when using Sending Silverpop Email in Salesforce. |
|
|
1.19 |
Summer 2013 |
Sync Silverpop Templates null exception if the template is associated with a query or contact list. |
|
|
1.17 |
Summer 2013 |
Ability to organize Silverpop Email Templates in Salesforce Folders and honor permissions of the folders in Send Silverpop Email dialog. |
|
|
1.16 |
Summer 2012 |
Send Silverpop Email button intermittently shows an error for Campaigns with 1,000 plus members. |
Lightning Page Dynamic Forms Limitations
Page Layouts are edited in the Salesforce Classic UI even though they can be used in Lightning Experience.
Some Salesforce users may want to Edit the Classic Lead and Contact Page Layouts in Lightning Experience and upgrade them to Dynamic Forms.
Some components in the Acoustic Campaign Salesforce CRMi packages are not compatible with Salesforce Dynamic Forms for Lightning Pages.
One is the Contact Insight Visualforce page.
The screenshot below shows the Available for Lightning Experience, Experience Builder sites, and the mobile app option is unchecked.
Acoustic’s developers are currently addressing this issue as an enhancement request.
because Dynamic Forms are not available or a requirement for all standard Salesforce objects.
Please review Dynamic Forms Limitations.
The beginning steps to upgrade a Page layout to a Dynamic Form is shown below.
In Lightning App Builder alone, the Contact Insight Visualforce page displays fine. When selecting the highlighted Upgrade Now section for Dynamic Forms, an issue will occur for incompatible components.
Select any area in the Detail section and click the Upgrade Now button.
Click Next.
Select the Classic Page Layout to upgrade, and click finish.
After clicking finish, the Contact Insight section no longer shows any data. This is because the component doesn’t meet the following rule.
If this is not desired, it’s best to click Back or Undo rather than Save.
It's best to Create a new Page Layout, copy your existing Layout, and test the upgrade to Dynamic Forms.