Current loctn: salesforce > npsp v3 upg > pkg eval > pkg eval sendit cmp monitoring for sf 2.85

Salesforce NPSP V3 Upgrade Package Evaluation - Campaign Monitoring for Salesforce 2.85

Purpose

This document provides information pertaining to whether the Campaign Monitoring for Salesforce 2.85 package published by Beaufort 12 Ltd must be uninstalled, or have a special configuration established during:

1. Upgrade from Non-Profit Starter Pack (NPSP) V2 to NPSP V3

   Package configuration needs for use of the Salesforce Account Model Conversion (AMC) utility are also evaluated/documented here.

2. Transfer of data from Production instance to a sandbox used for testing data manipulations required as part of a upgrade or conversion to NPSP V3

   Data transfers of this type may be required if:

   1. A developer or developer pro sandbox is being used for testing NPSP V3 upgrade/conversion processes

      The use of these sandboxes can avoid the expense of a full sandbox in some situations.

   2. A sandbox test of NPSP V3 upgrade/conversion has revealed problems that require a revised test that in turn requires reloading of the sandbox with test data.

      Even though a full sandbox will include data contents, the typical full sandbox 29-day refresh cycle may result in a need to reload the sandbox if a single upgrade/conversion test doesn't suffice.

Red-colored text is used to represent critical information items that may interfere with needed operations in very important ways.

Blue-colored text is used to represent useful information which nonetheless is somewhat less than critical in importance.

Green-colored text is used to represent useful information which indicates an absence of problems or special configuation/data handling needs.

Use agreement

Information provided here is copyrighted by Larry Bednar and licensed under the GNU Free Documentation License. A copy of the text of this license may be found at http://www.gnu.org/licenses/fdl.html

The main points of the GNU license indicate that users are allowed to distribute the orginal licensed product, or distribute modified versions if the following conditions have been fulfilled:

• Distributed versions must indicate if changes have been made, and the date of the changes
• Source code must be provided with distributed versions of the product or made readily accessible through other means
• The distributed product must also be licensed under the GNU Lesser General Public License or the GNU Public License
• A copy of the the applied GNU license must be provided with the distributed product.

If a more detailed understanding is needed, please follow the links provided above to review the actual text of the GNU licenses.

If you distribute modified copies of these items, it is both polite and useful (but not required) to provide some additional information:

• The author(s) of any changes, with contact information
• Modified versions of accompanying documentation that reflect your changes

Package Details

[(LB) - The version of this package that I examined was unmanaged.]

Publisher: Beaufort 12 Ltd

Package Name: Campaign Monitoring for Salesforce

Package Version: 2.85

Description: Track email opens, clicks, bounces, social statistics and more all within Salesforce.

(A catalogue of package components is provided in this file: pkg_components_sendIT_cmp_monitor_2_85.xls)

Package components include:

1. Apex Classes
2. Apex Triggers

   Key objects on which triggers are defined:

   1. Account (1 trigger)
   2. Contact (1 trigger)
   3. Lead (1 trigger)
   4. Subscriber List (1 trigger)
3. Apps
4. Buttons or Links
5. Custom Fields

   [If an uninstall is required, these fields and associated data will likely be removed. Export of those data and updates after a reinstall may be required.]

   Custom fields defined on objects that are not provided as part of package:

   1. 14 defined on Campaigns
   2. 2 defined on Campaign Members
   3. 1 defined on User
6. Custom Objects

   [If custom objects are provided with the package, this may mean that a required uninstall action would also require export of records from these objects prior to the uninstall and reloading of that data when the package is later reinstalled.]

   1. Automatic Subscription
   2. Custom Field Mapping
   3. Email Tracking Statistics
   4. Subscriber List
7. Custom Report Types
8. Dashboard Folders
9. Dashboards
10. List Views
11. Page Layouts
12. Remote Sites
13. Report Folders
14. Reports
15. Static Resources
16. Tabs
17. Visualforce Components
18. Visualforce Pages

NPSP V3 Install and ACM Usage Configuration

The AMC utility is stated to require that no additional automation should execute during AMC operation.

Any package automation (Apex triggers, workflow rules, or validation rules) that execute in these situations may cause problems:

1. Creation of Account records
2. Update of Contact records
3. Update of Opportunity records
4. Update of Task records

(The list of package components provided above uses blue-colored text for components types that might present problems.)

Publisher Input

[(LB) - The publisher was contacted for information about problems encountered with NPSP V3 install and/or use of the AMC utility while this package is installed. They indicate that it may be wise to establish the disable all actions setting for their package prior to data transfer. The publishers directions ( How Do I Disable Actions) are provided at this url:

http://support.beaufort12.com/customer/portal/articles/1711362-how-do-i-disable-actions

User Input

[(LB) - No discussions on Power of Us Hub or elsewhere were sought for information about problems encountered during NPSP V3 installation or related data processing. Package components did not appear to suggest problems.]

Final Evaluation for NPSP V3 Install and AMC Operation

Regarding configuration of this package during NPSP V3 installation and use of the AMC utility...

Key Information: The package may be left installed. However, the Campaign Monitor Settings value for disable all actions should be established during data transfer. The publishers directions ( How Do I Disable Actions) are provided at this url:

http://support.beaufort12.com/customer/portal/articles/1711362-how-do-i-disable-actions

Sandbox Data Loading

Package automation that creates records in response to record insertions may create records that are not derived from the data source.

This may be important if users intend to use the sandbox for a complete review and validation of post-conversion functionality. Especially if users will expect to see an exact and accurate representation of records from the source database (usually the production instance) within the sandbox

This may not be important if the sandbox is used only to verify correct conversion of data to a new account model (such as the new NPSP V3 household account model), and if the sandbox will not be expected to contain an overall faithful representation of data from the source database. If package automation does not create new records within key objects being handled by the AMC utility, data transfers undertaken solely to create an NPSP V3 data processing test environment, data transferred to the sandbox should be acceptable for the intended uses.

The AMC utility works with records in these objects:

1. Accounts

   If the database is being converted from one-2-one or bucket to the new household account model, new Account records will be created to represent NPSP Household records already present in the instance.

2. Contacts

   Contacts linkages to Accounts may be updated.

3. Opportunities

   Linkage of Opportunities to Accounts may be updated.

4. Tasks

   Linkage of Tasks to Accounts may be updated.

Publisher Input

[(LB) - The publisher was contacted for information about problems encountered data loading with this package installed. They indicate that They indicate that it may be wise to establish the disable all actions setting for their package prior to data transfer. The publishers directions ( How Do I Disable Actions) are provided at this url:

http://support.beaufort12.com/customer/portal/articles/1711362-how-do-i-disable-actions]

User Input

[(LB) - No discussions on Power of Us Hub or elsewhere were sought for information about problems encountered during data loading.]

Final Evaluation for Sandbox Data Loading

Regarding configuration of this package during data loading...

[[LB - Key Information: The package may be left installed. However, the "Campaign Monitor Settings" value for "disable all actions" should be established during data transfer. The publishers directions ("How Do I Disable Actions"://support.beaufort12.com/customer/portal/articles/1711362-how-do-i-disable-actions) are provided at this url:

http://support.beaufort12.com/customer/portal/articles/1711362-how-do-i-disable-actions]]

Last modified: 14:27:07 14-Mar-2015