Last modified: 14:19:32 14-Mar-2015
This document provides information pertaining to whether the
Drip Campaign Module
package published
by (unknown)
must be uninstalled, or have a special
configuration established during:
Package configuration needs for use of the Salesforce Account Model Conversion
(AMC) utility are also evaluated/documented here.
Productioninstance to a
sandboxused for testing data manipulations required as part of a upgrade or conversion to NPSP V3
Data transfers of this type may be required if:
developeror
developer prosandbox 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.
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.
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:
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:
[(LB) - The version of this package that I examined was unmanaged.]
Publisher: (unknown) [LB - I encountered this package, it was indicated to be installed by Dave Manelski, formerly of ONE/Northwest (later named Groundwire), now of Salesforce. So I'd guess that development of this package was originally undertaken as a ONE/Northwest effort.]
Package Name: Drip Campaign Module
Package Version: 0.2
Description: (none provided)
(A catalogue of package components is provided in this file: pkg_components_drip_cmp_module_0_2.xls)
Package components include:
Key objects on which triggers are defined:
[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.]
All defined on objects provided with package
[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.]
[May be helpful to list custom objects provided with package.]
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:
(The list of package components provided above uses blue-colored text for components types that might present problems.)
[(LB) - The publisher was not contacted about problems encountered with NPSP V3 install and/or use of the AMC utility while this package is installed. Package components did not appear to suggest problems.]
[(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.]
[(LB) - From code examination... The Campaign trigger provided
by this package, executes only on insert
of a new Campaign record. If the
record type
of the campaign is drip campaign
the trigger automation
adds standard campaign member status
values to be used for Campaign Member
records linked to the Campaign.]
Regarding configuration of this package during NPSP V3 installation and use of the AMC utility...
[LB - My educated guess is that leaving this package
installed during use of the Account Model Conversion
utility will cause
no problems. There appears to be no automation that would execute during use
of the AMC utility.]
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:
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.
Contacts linkages to Accounts may be updated.
Linkage of Opportunities to Accounts may be updated.
Linkage of Tasks to Accounts may be updated.
[(LB) - The publisher was not contacted about problems encountered during data loading with this package installed. Package components did not appear to suggest problems.]
[(LB) - No discussions on Power of Us Hub or elsewhere were sought for information about problems encountered during data loading.]
[(LB) - From the code examination detailed above, it seems that the Campaign trigger would execute during record insertions. However, the nature of the automation executed would be unlikely to cause significant problems during data loadings using moderate batch sizes. (Larger batch sizes might result in problems due to record locks, etc as the trigger automation executes during data loading operations?)]
Regarding configuration of this package during data loading...
[LB - My educated guess is that leaving this package installed and configured in a normal fashion will not interfere with Production->Sandbox data transfer.]
Last modified: 14:19:32 14-Mar-2015