roundcause upgrade guide · to start creating a new account. 8. on the . select account record...

ROUNDCAUSE UPGRADE GUIDE

Table of Contents Summer '15 Release Upgrade Guide - NGO Connect and Advancement Connect .......................... 4

Bios Summer '15 Release from Spring '15 Release .................................................................. 5

Giving Summer '15 Release from Spring '15 Release .............................................................13

Events Summer '15 Release from Spring '15 Release ............................................................18

Volunteers Summer '15 Release from Spring '15 Release .....................................................19

Connect Summer '15 Release from Spring '15 Release .........................................................20

Education Summer '15 Release from Spring '15 Release ......................................................22

Spring Release Upgrade Guide - NGO Connect and Advancement Connect ..................................23

Bios Spring 15 Release from Winter 15 Release .....................................................................24

Giving Spring 15 Release from Winter 15 Release ..................................................................28

Connect Spring 15 Release from Winter 15 Release ..............................................................33

Volunteers Spring 15 Relase from Winter 15 Release ............................................................36

Events Spring 15 Release from Winter 15 Release .................................................................40

NGO Connect Winter Release Upgrade Guide ....................................................................................41

NGO Connect: Package Versions and Structure ......................................................................42

Bios Winter Release from Bios 2.16 ..........................................................................................43

Giving Winter Release from Giving 2.15 ...................................................................................48

Connect Winter Release from Connect 2.17 ............................................................................54

Advancement Connect Winter Release Upgrade Guide ....................................................................56

Advancement Connect: Package Versions and Structure ......................................................57

Education Winter Release ..........................................................................................................58

Package Upgrades and Custom Settings .............................................................................................62

Removing Deprecated Custom Setting fields ..........................................................................63

rC Bios Upgrade Guide ...........................................................................................................................65

Upgrading from Bios 2.10 to Bios 2.11 .....................................................................................66

rC Giving Upgrade Guide .......................................................................................................................67

Upgrading to Giving 2.16 ............................................................................................................68

rC Connect Upgrade Guide ....................................................................................................................71

Upgrading from Connect 2.11 to Connect 2.12 .......................................................................72

Upgrading to Connect 2.17 ........................................................................................................73

Summer '15 Release Upgrade Guide - NGO

Connect and Advancement Connect

roundCause Upgrade Guide

Bios Summer '15 Release from Spring '15 Release

Customizing the Address Information Fields in Accounts You can choose the fields that appear in the Address Information for Account section of the Account Entry page. This enables you to customize the address information provided in new accounts so it matches the needs of your organization.

1. Click your name in the upper right corner of the window and select Setup.

2. From the Build section in the left panel of the Setup page, click Create > Objects. In the Custom Objects section of the page, click AccountAddress.


This takes you to the Account Address (Managed) page, where you can customize how account address information is collected and stored.

3. Scroll down to the Field Sets section and click Edit next to the Account_ManageContacts field set.

The Account_ManageContacts field set opens. Available fields are listed in the top section.

4. To add a field to your page, click it in the top section and drag it into the In the Field Set window.


5. When you have finished adding the fields you want included, click Save.

To verify that the fields you selected now appear in the Address Information for Account section:

6. From your main menu, click Accounts.

7. Click New to start creating a new account.

8. On the Select Account Record Type page, choose a record type (Household or Organization) and click Continue.

The next page to open shows contact information for the account, including address information.


9. Review the Address Information for Account section to confirm that the correct fields appear.

Access to Visual Relationships

The "Visualize" button is no longer available on the Manage Relationships component for Accounts and Contacts.

• The button is removed automatically during the Summer '15 Release upgrade • The button is not present in new installations of the Summer '15 Release or later

The button was removed based on customer feedback to reduce prominence of the feature for new and existing customers. We've received tons of feedback that is getting evaluated for development in the future. Access to the Visualize functionality can be enabled through custom buttons and the quick configuration steps below. If access to the functionality is not desired then no need to do anything.

Follow the steps below to create the Visualize (Visual Relationships) button on Account and Contact:

1. Go to Setup | Accounts | Buttons, Links, and Actions.

2. Click New Button or Link.

3. For the Label field, type "Visual Relationships".


4. Tab into the Name field, or type "Visual_Relationships".

5. Choose Display Type of "Detail Page Button".

6. Choose Behavior of "Display in new window".

7. Select "Visualforce Page" from the Content Source drop-down.

8. From the Content picklist, choose a Content Source:

For Accounts, choose Account_VisualRelationships [rC_Bios__Account_VisualRelationships].

For Contacts, choose Contact_VisualRelationships [rC_Bios__Contact_VisualRelationships].

9. Click Save.

10. Click OK on the popup.

11. Add the button(s) to the desired Account and Contact page layouts.

Pilot Program Access for Feature Activation Activation of Pilot features require a pilot activation request. This is done on a feature by feature basis for the specific org requested.

The Pilot request must be made through the Foundation via the following steps:

1. Grant Salesforce Foundation Support access to an Admin user 2. Create a Case from the org where Pilot access is required by clicking 'Help & Training' and

following Case creation prompts 3. Provide the name of the pilot (e.g "Native Addresses", "Simplified Household Creation"), Org

ID where feature should be activated, Business Justification

Activation will happen through Foundation Support updating hidden pilot feature settings in your org. The pilot feature can be additionally controlled by an admin in the org - this is described in the next step.

Native Addresses Pilot - Installation and Activation


The Native Addresses Pilot allows for entry of Account and Contact Address information directly from the Account and Contact records. This will sync down to the advanced management tools already available in Bios, and any updates made in the address management screens will sync up to Account and Contact as they did in the past.

The Native Addresses Pilot is turned off by default because it is in Pilot, and is a significant update to address management. The feature requires that Address Sync between Account and Preferred Contact is turned off (note that this is the default for new installations) and Household Addressing features are turned off (this is still beng regression tested). This feature can be turned on in custom settings by completing the steps below.

Activate the Native Addresses Pilot and Disable conflicting features

1. Navigate to Setup > Customize > Accounts. 2. Enable Read and Write access to the standard address fields (these fields are locked during

setup for some implementations). 3. Navigate to Setup > Customize > Contacts. 4. Enable Read and Write access to the standard address fields (these fields are locked during

setup for some implementations). 5. Navigate to Setup > Develop > Custom Settings. 6. Configure these settings as follows:

• in Account Setting, Disable Upsert Addresses? = unchecked • in Contact Setting, Disable Upsert Addresses? = unchecked • in Account Address Setting, Disable Sync Up? = checked • in Account Address Setting, Disable Apply Household Address? = checked • in Account Address Setting, Disable Apply To All Contact? = checked • in Contact Address Setting, Disable Sync UP? = checked

More details about the functionality and use cases are in the Product Manual.


Native Phone and Email Pilot - Installation and Activation

The Native Phone and Email feature allows users or applications to enter phone and email data into the standard Salesforce email and phone fields. Prior to this update, Bios controlled the fields using the specific type of phone or email fields (Home, Work, etc) along with the "Preferred" picklist. This feature allows data entry in the email or phone fields; entries in these fields then sync down to the communication type marked "Preferred" in the picklist.

The Native Phone and Email feature is turned off by default. The feature can be turned on in custom settings by completing the steps below.

1. Navigate to Setup > Customize > Contacts. 2. Enable Read and Write access to the standard Phone and Email fields (these fields are

locked during setup for some implementations). 3. Add the fields to the page layout for Contact in use. 4. Navigate to Setup > Develop > Custom Settings. 5. Configure these settings as follows:

• in Contact Setting, Disable Import Preferred Phone? = unchecked • in Contact Setting, Disable Import Preferred Email? = unchecked



Simplified Household Creation Pilot

The Simplified Household Creation feature allows users or applications to create a Contact record and have the Account record created automatically. If no account is specified during Contact creation, an Account will be automatically created based on Account Name rules in custom settings with Contact Address and Preferred Contact information getting copied over as well.

This feature works best with the Native Addresses Pilot enabled. Additional details are in the Product Manual for Simplified Household Creation. These two features activated together ensure logical and easy creation of Address records for your Accounts and Contacts.

The Simplified Household Creation feature is turned off by default. The feature can be turned on in custom settings by completing the steps below.

1. Navigate to Setup > Develop > Custom Settings. 2. Configure this setting as follows:

• in Contact Setting, Disable Insert Accounts? = unchecked



Giving Summer '15 Release from Spring '15 Release

Credit Object Fields are Available on the Opportunity_Manage_ListCredits Field Set

1. Open the Salesforce Setup menu.

2. Click Create.

3. Click Objects.

4. Click the Credit object label.

1. Scroll to the Field Sets section and click Edit next to the Opportunity_Manage_ListCredits field set.


1. Drag and drop fields you want listed into the field set.

2. Click Save.

Adding or Editing a Custom Expiration Date Automatically Updates the Giving Summary and Related Fields

1. Edit the Custom Expiration Date.


2. Click Save.

This will initiate an Update Summaries job, and will update the date fields on the Summary as needed based on your org's configuration and custom settings. These fields will then update other relevant fields (such as those on the Account record).

All Non-One Time Payments from Donation Forms will be marked as Sustainer? = TRUE

This represents a bug fix and not nothing must be done to implement the change. However, it will render workarounds irrelevant and would change the current behavior of gifts that originate from a Donation Form.

Previously, only Monthly payments were marked as Sustainer? = TRUE on the Batch Upload record created from our Donation Form. As of the Summer '15 release, all non-One Time payments will be marked as Sustainer? = TRUE when saved to Batch Upload.

Changes to Exposure of New Refund and Refund All Buttons in Giving Wizard

This update requires the Payment Processor setting to list which payment processors are being used in your org. and which require a Transaction ID to process a refund. iATS, Paypal, Litle and Authorize.net all require a Transaction ID in order to process a refund on the original transaction.

Sage and Heartland do not require a Transaction ID to process a refund.


The update represents how different payment processors handle refunds. Many processors require a Transaction ID from the original transaction in order to process the refund. If the payment processor used on a transaction requires a Transaction ID, and that ID is missing, then the New Refund and Refund All buttons will not be displayed. A more detailed break down of expected behavior follows;

1. If all transactions are associated with a payment processor that requires a Transaction ID, and the Transaction ID is not present: neither the New Refund nor the Refund All buttons will be visible.

2. If all transactions are associated with a payment processor that requires a Transaction ID, and the Transaction ID is present, then both buttons are visible and available.

3. If some transactions are associated with a payment processor that do require a Transaction ID and some are associated with a payment processor that do not require a Transaction ID, then only the New Refund button will be visible and accessible.

4. If none of the transactions are associated with a payment processor that requires a Transaction ID, then the New Refund and Refund All buttons will be visible and available.

REQUIRED CONFIGURATION: Create Payment Processor Setting records

If you are using any payment processor other than Sage or Heartland, you MUST complete these steps.

Navigate to Set Up > Develop > Custom Settings. Select the Giving (or rC_Giving) view, and click Manage next to Payment Processor Setting. Click New.

1. Enter the Processor Name. Note that this should be one of the following values:

- Authorize.net

- iATS

- PayPal


- Litle

- Cybersource

2. Check the "Is Transaction Id Required?" box. Click Save.

Repeat this step for any additional Payment Processors you are using. If you have multiple merchant accounts with the same Payment Processor, yo need only one record per Payment Processor.

Default Giving Type Engine field on Opportunity Setting is blank

This field on the Opportunity Setting custom setting is no longer where the Giving Type Engine should be set. Please refer to documentation about the Opportunity Record Type Setting Custom Setting where you may set a default Giving Type Engine for each Giving Record Type.


Events Summer '15 Release from Spring '15 Release

Creation of Campaign Members No Longer Required After the First Page of Events Forms When using the "legacy" Events form (which is native to the Events package), the Campaign Member record no longer must be created after the first page. This means that users may create forms using this tool without demographic fields on the first page.

There is no configuration required to take advantage of this improvement.

Events Package Email Workflows are Disabled by Default

The Summer '15 release of Events included a new custom setting called Email Setting. This setting controls the email workflows that are included in the Events package:

• Email Confirmation: Waitlist Upgraded To Registration • Email Confirmation: Registration Confirmed For Session • Email Confirmation: Registration Confirmed • Email Confirmation: Registration Canceled • Email Confirmation: Added To Waitlist

The Email Setting allows users to activate these email workflows, and must be configured before these workflows are used.


Volunteers Summer '15 Release from Spring '15 Release

Email Field is No Longer Required on the Applicant__c object This requires no configuration from users.

With the Summer '15 release of the Volunteers package, the Email field is no longer required by default on the Applicant__c object.

When a new Application Form is created, the Email field will no longer be added to the form automatically (this feature is controlled by custom settings).

When the "Group Signup?" component is added to an Application Form and fields are created for each group member, the Email field will no longer be included.

When setting an Applicant's status = Approved (which creates a new Contact record or matches to an existing contact record), the Email field is not required.

Applicant Address Info Inserts a New Contact Address Record This requires no configuration from users.

When an Applicant record is created with Address information from an Application Form, and the Applicant Status = Approved, a Contact record is either created or matched to an existing contact record.

The Address information attached to this Applicant record will now create a Contact Address record. If this is a new Contact, it will be marked as a Preferred Address. If the Contact already existed, it will not be marked as a Preferred Address.


Connect Summer '15 Release from Spring '15 Release

Refunds Restricted Based on Retention of Transaction ID

Configuration

This behavior requires the setup of the Payment Processor Setting custom setting.

Please add each payment processor you will use in your org. to this setting and indicate whether or not they require a transaction ID to process a refund.

As of the Spring '15 release, the payment processors in NGOC that require a transaction ID are; Authorize.net, iATS, Litle, Cybersource and Paypal.

Sage and Heartland do NOT require a transaction ID.

New Behavior

Refunds are restricted when a Transaction ID is not retained by a payment processor, if that particular payment processor requires a Transaction ID.

The New Refund and Refund All buttons within the NP Giving Wizard are hidden or shown based on the presence of a Transaction ID associated with the payment method used for transactions.

If all transactions were processed using a payment processor that requires the Transaction ID to process refunds--and the Transaction ID was not retained--the New Refund and Refund All buttons will be hidden. If a transaction ID is not required by the payment processor to process refunds, these buttons will be visible.

If the gift does not have an associated payment processor, the buttons will be visible.


If two different payment processors were used across multiple transactions, the buttons will be visible. However, if a user attempts to create a refund using a payment processor that does require a transaction ID for refunds, the user will see an error message.

Add Batch Upload tab back into your org.

Starting with the Spring '15 release, the Batch Upload tab was not included as part of the Connect Managed Package. This requires users to manually add the tab back into their orgs. The functionality is unchanged, there is just this admin function to complete before users can continue using the tab.

1. Navigate to the Create section of the Setup menu.

2. Click on Tabs.

3. Click the New button and follow the prompts to add the Batch Upload tab back into your org.


Education Summer '15 Release from Spring '15 Release

Communication Method Improvements This requires no configuration from users.

With the Summer '15 release of the Education package, improvements to constituents' communication methods will allow for improved handling of preferred communication methods, start and end date validation, duplicate record management, and proper rolling up and down of data between the contact record and communication methods. The improvements allow for the granular communication method tracking that advancement institutions need to truly understand their constituents and ensure that constituent touches are done in the most appropriate channel.

Preferred Behavior

Please note that the preferred email/phone for each email/phone type rolls up to the contact record. These may be edited directly on the contact record, creating a new preferred record for that email/phone type; or setting the entered email/phone address to "preferred" for that type if a communication method currently exists for the entered value. They may also be edited on the communication method object record. In this case, if a record that is currently not "preferred" is marked "preferred", the system will automatically set the originally preferred record to not preferred and roll up the new "preferred" email/phone to the respective email/phone field on the contact record.

Date Validation

When creating a new communication method, no matter the record type, be sure to enter a start date that falls prior to the end date, as a validation will disallow the record to be saved until this condition is met if the "Start End Dates Valid" custom setting is set to true.

Duplicate Record Management

When creating a new communication method, please be sure that the combination of email or phone value and type is unique. Duplicate communication methods will not be allowed if the custom setting "Disable Check Duplicate?" is set to false.

Data Rolling Up and Down

Please note that any changes made to the existing communication method object records, once saved, will roll up to the contact record. Likewise, if any existing contact record information is edited, a new communication method will be created if it doesn't already exist.


Spring Release Upgrade Guide - NGO Connect and

Advancement Connect


Bios Spring 15 Release from Winter 15 Release

Spring Release - Bios package

Employment Relationships Tracking

Note on potentially impactful validation rule - in 'Relationship Settings' Custom Settings in the rC_Bios namespace, the field "Disable PrimaryValidation?" determines whether Employment Relationship record must have at least one per Account marked as Primary.

• If set to False (default), each Household Account that has at least one Employment Relationship will be required to have one relationship record marked as Primary? = True

• If set to True, Household Accounts do not need to have any records marked as Primary? = True

• The Primary designation helps Matching Gift functionality properly assign a Matching Ratio to incoming Giving records for Matching Amount calculations associated to the Account.

• When enabled this validation will affect existing Employment Relationships - this can be resolved through a data update or by users manually selecting a Primary relationship during edits

1. Go to Setup | Develop | Custom Settings 2. Click the Manage link next to 'Relationship Setting' in the rC_Bios namespace 3. Click Edit 4. Mark the setting 'Disable PrimaryValidation?' based on org preference 5. Click Save

Functionality

• Relationships functionality is updated with better support for Employment use cases. • New fields include: Industry, Occupation, Earnings, Level - included on the display for

Employment Relationships by default • New fields come with default values but need to be configured for record types

Configuration


New Picklists (picklist values are not added by default)

1. Go to Setup | Create | Objects | Relationship 2. Scroll to Record Types 3. Click "Account - Contact" in the Related List 4. Click the Edit link next to "Industry" 5. Choose the desired values. Highlight all Available Values and move to Selected Values for the

packaged defaults. 6. Click Save 7. Repeat steps 4 through 6 for "Occupation", "Earnings", and "Level"

Do the above steps for other record types that are used for Employment Relationships - "Account - Account" is commonly used additionally.

Employment Relationships Fieldset (new fields are added by default)

1. Go to Setup | Create | Objects | Relationship 2. Scroll to Field Sets 3. Click the Edit link next to "ManageRelationships_CategoryEmployment" 4. Add or Remove fields (by dragging and dropping) from the "In the Field Set" section 5. Click Save

Preferences Rules Engine for Contact and Account Functionality

• Dynamic Preference creation • Preferences created based on rules defined for Contact or Account data • Preferences marked as Not Active if rule no longer validates to true • Manual override of Preferences available on a record by record basis • Controlled by scheduled job or manual Developer Console job

Configuration

Record Type Assignment

1. Go to Setup | Manage Users | Profiles 2. Locate the profile that needs to create Preference Rules and click on the profile name 3. Go to Custom Record Object Settings | Preference Rule Criteria 4. Click Edit 5. Activate/Assign the "Account" and "Contact" record types 6. Save

Activate the new Custom Setting fields

1. Go to Setup | Develop | Custom Settings 2. Click "Manage" next to Account Setting in the rC_Bios namespace 3. Click Edit then Save to activate defaults 4. Click "Manage" next to Contact Setting in the rC_Bios namespace 5. Click Edit then Save to activate defaults


Preference Codes - Configure Preference Codes

Create Preference Rule

1. Go to Preference Rules custom object view 2. Click New 3. Enter Preference Rule Name 4. Assign associated Preference Code 5. Save

Create Preference Rule Criteria

1. Go to a Preference Rule record 2. Click "New Preference Rule Criteria" in the Preference Rule Criteria related list 3. Choose Record Type 4. Enter Field using API Name of the field from the record type specified (Account or Contact) 5. Enter Operator 6. Enter Value to compare

Run the Preference Rule Engine Scheduled Job

1. Schedule "PreferenceRuleEngine_Schedulable" - this will run the rules engine for both Account and Contact

Schedule or Run the Preference Rule job for Account and Contact separately

1. Schedule "Account_PreferenceRuleEngineSchedulable" - to schedule the Preference Rule Engine on Accounts

2. Schedule "Contact_PreferenceRuleEngineSchedulable" - to schedule the Preference Rule Engine on Contacts

3. Run "database.executeBatch(new rC_Bios.Account_PreferenceRuleEngineBatchable());" - to run the Preference Rule Engine on Accounts

4. Run "database.executeBatch(new rC_Bios.Contact_PreferenceRuleEngineBatchable());" - to run the Preference Rule Engine on Contacts

Custom Preference Display for Contact and Account

Functionality


https://roundcorner.screenstepslive.com/12732/l/87952?data-resolve-url=true&data-manual-id=12732

• Choose a Preference Category to be displayed outside of the Preference Related list • Select Category and position Visualforce display separately for Contact and Account

Configuration

Set Category to Display

1. Go to Setup | Develop | Custom Settings 2. Click "Manage" next to Account Setting in the rC_Bios namespace 3. Edit and Enter a value defined as a Preferences Category in the "Preference Category" field

on the custom setting 4. Click Save 5. Do steps 1 through 4 for Contact

Add Visualforce component to Page Layouts

1. Go to Setup | Customize | Accounts | Page Layouts 2. Edit the page layout in use 3. Select "Visualforce Pages" from the left menu in the page layout editor 4. Add the Visualforce Page "Account_DisplaySociety" (It is recommended to create a single

column section to hold this) 5. Click Save 6. Do steps 1 through 5 for Contact

CASE Reporting (Advancement) Functionality

• Assign a Donor Profile to Preference Code records for reporting • 'Donor Profile' field comes prepopulated with Default CASE values

Configuration

1. Go to Setup | Create | Objects 2. Click on Preference Codes 3. Edit the Preference Codes layout used for standard Preference Codes records 4. Add the 'Donor Profile' field 5. Save


Giving Spring 15 Release from Winter 15 Release

Spring Release - Giving Package

Matching Gifts Post-Install Upgrade Functionality

• Batch job data updates for organizations upgrading from the Winter Release version of NGO Connect or Advancement Connect

• Run job for automatic configuration/data load for new Matching Gift functionality • The job selects Organization Accounts where Matching Ratio is not blank

Configuration

1. Upgrade to Spring 15 Release version of Giving. 2. Run the following job in the Dev Console "Database.executeBatch(new

rC_Giving.Account_CreatePrimaryRatioBatchable());".

For Manual data migration

1. Select all Organization Accounts with Matching Ratio / Matching Gift data. 2. Propagate that data into Matching Ratio records, linking back to the original Account and

marking the record as Primary.


Matching Gifts - Expanded Ratio Support

Functionality

• Allows multiple Matching Ratios per Organization Account • Original Matching Ratio fields (on Account) are now populated with data from the Matching

Ratio custom object record marked as Primary

Configuration

1. Go to Setup | Customize | Accounts | Page Layouts. 2. Edit the Organization Account page layout(s) in use. 3. Add the Matching Ratio related list to the layout. 4. Click Save.

Giving Amount Rollups on Campaign Updates Functionality

• Direct Rollup - At a Campaign record level, control whether Giving Amounts roll up from directly associated Giving records

• Hierarchy Rollup - At a Campaign record level, control whether Giving Amounts roll up from Campaigns lower in the hierarchy

Configuration


1. Go to Setup | Customize | Campaigns | Page Layouts. 2. Edit the page layout(s) in use. 3. Add the fields "Disable Direct Rollup" and "Disable Hierarchy Rollup" to the layout. 4. By default, these fields are unchecked - meaning that rollup is enabled.

• To disable direct rollup, check "Disable Direct Rollup". • To disable hierarchy rollup, check "Disable Hierarchy Rollup".

Review/Update Campaign Setting

In the rC_Giving namespace, review the Campaign Setting fields.

1. The "Rollup Giving Batch by Giving?" field has been deprecated, and is now labeled as such. If this field is checked, you MUST edit the record and select the "Rollup Giving Batch?" checkbox.

2. If the "Rollup Giving Batch? checkbox was not previously checked, it is recommended that you check it and the Disable Rollup Giving (3) fields, and then follow the steps below for scheduled Campaign giving amount rollups. This will suppress real-time Campaign rollup functionality and improve the speed of entering and updating Giving records.

3. Also check the Opportunity Setting in the rC_Giving namespace, and ensure that Disable Cascade Campaigns? is FALSE/unchecked.


Schedule Giving Amount Rollups to Campaign

Note - it is important to schedule this job so that Giving rollups to Campaign work correctly.

Functionality

• Schedulable job that assists with rollup of Giving Amount information to Campaign

Configuration

1. Go to Setup | Develop | Apex Classes. 2. Click Schedule Apex. 3. Schedule the following class based on the sample in the screenshot:

"Campaign_RollupGivingSchedulableByGiving".

Additional Summary Data Functionality

• View additional Summary Data related to rolled up Giving records

Configuration

1. Go to Setup | Create | Objects | Summary. Scroll down to the Page Layouts section. 2. Edit the page layout(s) in use.


3. Add the following fields: "Summary Count", "Summary #", "Current Campaign Source", "First Campaign Source", "Most Recent Add Campaign", "Most Recent Non-Add Campaign", "Previous Campaign Source".

Primary Affiliation on a Per-Account Basis Functionality

• Set an Account to have Affiliation fields roll up data different than the Org-wide custom setting selection

• Set a group of Accounts to have unique Affiliation via data loader

Configuration

1. Navigate to an Account. 2. Set the "Primary Affiliation" field to the custom configured Primary Affiliation of choice from

the drop-down menu.

CASE Reporting (Advancement) Functionality

• Assign a Purpose and a Type to General Accounting Unit (GAU) records for reporting • The 'Purpose' and 'Type' fields come prepopulated with default CASE values

Configuration

1. Go to Setup | Create | Objects. 2. Click on General Accounting Units. 3. Edit the General Accounting Unit page layout. 4. Add the 'Purpose' and 'Type' fields. 5. Click Save.


Connect Spring 15 Release from Winter 15 Release

Spring Release - Connect package

Batch Gift Entry The Spring '15 release includes a new Batch Gift Entry tool; officially replacing the legacy Batch Gift Entry tool.

The new tool is based on a Heroku app that users sign into with their Salesforce credentials.

Please review the following Product Manual articles to learn about how to access and use the new tool.

Batch Gift Entry guide in Screensteps

Again, this tool is officially replacing our legacy Batch Gift Entry tool as of the Spring '15 release. All enhancements moving forward will be made in the app described in the Product Manual articles mentioned above.

CVV Validation - Litle Payment Processing Validation Rule Impact - Validation Rule that was previously built into Litle trigger functionality is now removed. See below to create a custom trigger to require CVV for all Payment Methods. The trigger validation rule was removed because Litle does not explicitly require the CVV in order to process cards and because the rule was held in a trigger the function was not customizable to various organization needs.

Functionality

• Payment Methods associated to Litle Payments no longer require the CVV to be populated - customers that desire this validation should create a custom validation rule


https://roundcorner.screenstepslive.com/13822/c/38430?data-resolve-url=true&data-manual-id=13822

Matching Gifts Relationships integration

Note on potentially impactful validation - in 'Relationship Settings' Custom Settings in the rC_Bios namespace, the field "Disable PrimaryValidation?" determines whether Employment Relationship record must have at least one per Account marked as Primary.

• If set to False (default), each Household Account that has at least one Employment Relationship will be required to have one relationship record marked as Primary? = True

• If set to True, Household Accounts do not need to have any records marked as Primary? = True

• The Primary designation helps Matching Gift functionality properly assign a Matching Ratio to incoming Giving records for Matching Amount calculations associated to the Account.

• When enabled this validation will affect existing Employment Relationships - this can be resolved through a data update or by users manually selecting a Primary relationship during edits

1. Go to Setup | Develop | Custom Settings 2. Click the Manage link next to 'Relationship Setting' in the rC_Bios namespace 3. Click Edit 4. Mark the setting 'Disable PrimaryValidation?' based on org preference 5. Click Save

Functionality

• New Employment Relationships will automatically be assigned a Matching Ratio Type based on the associated Organization Account

• Primary Employment Relationship can be selected for use when Giving comes in to automatically calculate the Matching Amount

Configuration

1. Go to Setup | Create | Objects 2. Click the Relationships object 3. In the Field Set related list, open the 'ManageRelationships_CategoryEmployment' 4. Add the following fields: 'Matching Ratio Type' and (if used) 'Primary?'


Online Donation Forms - change to multi-page functionality - CONFIG CHANGE REQUIRED There are several new fields on the Batch Upload object, to which any Site Guest profiles will need to have access granted. Navigate to Setup > Develop > Sites > [your site name] > Public Access Settings.

In the newer Enhanced Profile manager, then click Object Settings > Batch Upload > Edit.

In the original profile manager, scroll to the Custom Field-Level Security Section and click View next to Batch Upload.

Grant Edit access on any fields to which the profile does not have access. It is mandatory to grant Edit access to the Batch Upload: Public Token field.


Volunteers Spring 15 Relase from Winter 15 Release

Campaign Record Type Custom Setting

Functionality

• This new Custom Setting allows you to redirect to multiple Visualforce pages when creating a new Campaign based on the Record Type.

• Each Record Type should be assigned to a Namespace and Visualforce page within that Namesapce.

• This Custom Setting is highly recommended (especially if rC_Event and rC_Volunteers namespaces are both installed)

Configuration

1. Click New 2. Enter the Name of the Record Type you'd like to setup 3. Enter the appropriate Namespace (either rC_Event or rC_Volunteers). NOTE: rC_Event is

singular. 4. Enter the name of the Visualforce page for creating and editing campaigns of this record

type. The Namespace prefix is not required in this field. 5. Click Save. 6. Return to Setup menu and navigate to App Setup --> Customize --> Campaigns --> Buttons,

Links, and Actions 7. Click Edit next to the "New" label. 8. Choose to override this button with the Campaign_RedirectRecordType

[rC_Volunteers__Campaign_RedirectRecordType] VF page.

If a Campaign Record Type is not listed in the Campaign Record Type Setting, then the user will be redirected to the standard page layout for the given Campaign Record Type. Note that using


this override requires granting a Volunteers package license to all users who will create or edit Campaign records.

Enable Visualforce Page Access for your Customer Community

1. Access the area to used to manage Community page access by using the Setup menu to navigate to the Communities page shown here.

2. Click on Manage next to your Community.

1. Click on "Go to Force.com"


Functionality:

• Setting access to these pages in the Community is required to access newly created pages in the Community.

• This will ensure your Community users can access all necessary Visualforce pages in the Community.

Configuration:

• After completing the steps above, access the Site Visualforce Pages section on this page. Click Edit.

• Ensure that these six rC Volunteers pages are accessible.


Ensure Account field is populated for Preference Records

Functionality:

• Ensure that the Account field is populated on ALL Preference records for your Volunteers. • This will ensure they have access to all Visualforce pages in the Customer Community,

should you grant them access.

Configuration:

• When creating a new Preference record, use the Account lookup to populate this field.


Events Spring 15 Release from Winter 15 Release

Connect Form Builder

Functionality:

• If you've installed Events alongside Connect, then you have access to the Connect Form Builder for Event Registrations.

• You can utilize either the Connect Form Builder or the existing Events Form. • Note: The Design Form button will direct you to the Connect Form Designer. The Manage

Form button will direct you to the existing Events form page.

Configuration:

1. Go to Setup | Customize | Campaigns | Page Layout 2. Edit the Event Page Layout, Event Session Page Layout and Event Template Page

Layouts. 3. Add the Design Form button to each page. 4. Click Save.

Payment Processor Options/Configuraiton View other Articles about setting up Payment Processors and configuring new Merchants.


https://roundcorner.screenstepslive.com/13822/c/39231?data-resolve-url=true&data-manual-id=13822

NGO Connect Winter Release Upgrade Guide


NGO Connect: Package Versions and Structure

Winter Release

Package Versions At the time of release, the Winter Release includes

• Bios 2.19 • Giving 2.22 • Inventory 1.8 • Connect 2.20 • Volunteers 1.5 • Events 1.18

Package Structure

NGO Connect is composed of the above components. There are four core packages that make up NGO Connect with Events and Volunteers available with NGO Connect licensing as well.


Bios Winter Release from Bios 2.16

Winter Release - Bios package

Secondary Contact Lookup Functionality

• Any Contacts created or updated with the Secondary Contact designation will be automatically populated in the Secondary Contact lookup (ON by default)

Configuration

1. Add the "Secondary Contact" field to Household Account page layouts. Go to Setup |Customize | Accounts | Page Layouts. Click Edit next to the page layout you need to edit (you can change multiple by repeating this process) Drag the Secondary Contact field from the top bar onto the page layout, placing it where you would like. Click Save

2. Functionality is turned on by default. Turn off by going to Setup | Develop | Custom Settings and finding the setting called Account Setting (in the rC Biops Namespace). Click Manage and then set Disable Set Secondary Contact? to true. Save.

Data Updates (optional)

1. Touch existing Contacts marked as the Secondary Contact to automatically populate the lookup on Account. Do this step after completing the upgrade guide steps for Giving and Connect.


Household Addressing on Account and Contact Creation

Functionality

• Apply Address to Account and Contacts when entering a new Household (ON by default)

Configuration

1. "Apply To All Contacts?" checkbox field appears when feature is enabled 2. Functionality is turned on by default - meaning the checkbox is displayed. Turn off (hide the

checkbox) by going to Setup | Develop | Custom Settings and finding the setting called Account Address Setting. Click Manage and then set Disable Apply To All Contacts? to true. Save.

Household Addressing on Account Address Edit Note - This is in beta and is turned off by default. Updates to the functionality are coming in the future.

Functionality

• Apply Address to Contacts when editing Household Addresses. (OFF by default) • Popup Appears when Saving Account Addresses, allowing the user to apply addresses to

selected Contacts. • Applies to 'Save' button but not 'Save & Close' button.

Configuration


1. Functionality is turned off by default for this release. Turn off by going to Setup | Develop |Custom Settings and finding the setting called Account Address Setting. Click Manage and then set Disable Apply Household Address? to false. Save.

Constituent Types

Functionality

• Allows assignment of Contacts to certain types of Preferences that can be displayed in a unique section on the Contact layout.

Configuration

1. Go to Setup | Create | Objects | Preferences. Add a picklist value to the Preferences Category field of "Constituent Type”. Then go to the subcategory field and add the different types of constituent that you would like to track, e.g. “Donor”, “Volunteer”, “Board Member” etc… After clicking save you will then need to alter the Field Dependency for subcategory as it is controlled by the Category field. On Subcategory page find the section called Picklist Options, next to “Category” click edit. Find the column labelled Constituent Type and then double click on your newly added values to make them available. Save

2. Add field "Primary" to the Preferences page layout. This indicates the Primary Constituent Type.

3. Add a section to the Contact layout with the Visualforce Page of "Contact_ManageConstituentTypes".To do this go to Setup | Customize | Contact - Page Layouts. Edit the layout you want to change and in the control bar along the top (where it normally lists all your fields) select VisualForce Component. Select the desire one and drag it to your page. You can configure the component by hovering over its top right corner and clicking on the wrench symbol. That will allow you to change size and also add a scrollbar.

4. OPTIONAL - Allow Constituent Type entry during Account and Contact creation via Visualforce page by enabling the Contact Setting - Enable Constituent Types? setting (this step will also require adjusting the "ContactManage" fieldset to accommodate the addition of the Constituent Type picklist to the display)


Constituent Types Ranking

Functionality

• Allows setup of ranking Constituent Types based on importance. • Allows for system-wide recalculation of Constituent Types to re-rank all Constituent Types

on Contacts based on changing organization priorities. • Displays Constituent Types in ranking order on each Contact.

Configuration

1. Complete instructions in prior step "Constituent Types" 2. Drag and Drop items in the Current Priorities list to set priority rankings based on values in

Subcategory, Type, and Subtype 3. Click button "Recalculate System-Wide" to update Contacts' Constituent Code ranking

Salutation Names Functionality

• Allows more advanced Name assignment to Contact records. (OFF by default due to Configuration steps)

Configuration


Apply Salutation Record Types of "Name" and "Salutation" to the desired User Profiles. Functionality will be standard Salutation if this update isn't made.

1. Go to Setup | Manage Users | Profiles 2. Open each profile that you want to change and scroll down to the Record type section. Find

the line for Salutations where it will most likely say {Master}. Click Edit next to this and assign the two record types and then click Save.

Update Salutation object page layouts to align with record type names.

1. Go to Setup | Create | Objects | Salutations 2. Scroll down the page until you find the Page Layout section 3. Click Layout Assignment s and then on the next page click Edit. 4. Select the column where record type = Salutation and assign it a Salutation page layout. You

may see two options, it does not matter which one you select. Repeat for Name. Save

Remove Age Range field from Contact Layout Age Range field was deprecated due to organization-by-organization differences in preferred range values. If the field is on layouts, it now displays as "@Deprecated(Version=2.18)".

This also affects the Demographic Profile field on Contact and the Primary Contact Demographic Profile field on Account. While these formula fields were not deprecated, they will now return "Unknown" as the middle element. They should be removed from layouts. The formulas in those fields can be used as a template to create a replacement Demographic Profile formula with a custom age range field.


Giving Winter Release from Giving 2.15

Winter Release

BEFORE Installation: Enable Orders

Prior to installing the Giving Winter '15 release package, navigate to Customize > Orders > Settings and check "Enable Orders". Orders is not utilized by any Giving functionality, but is required due to dependencies with new versions of Connect. Orders is utilized by optional Payment Grouping functionality in Connect.

Opportunity Record Type Setting

Feature (Mandatory)

• Opportunity Record Type Setting aggregates a number of custom settings in one place


• Configure Giving record types from visual display, rollups, functions, and names

Configuration (Mandatory)

1. To Navigate to this screen click Setup | Develop | Custom Settings and find the Setting call Opportunity Record Type Settings

2. Click Manage and you will most likely see a blank screen. Click New and follow the below steps for each record type that you are using.

3. The screenshot shows a basic recommended configuration (the default configuration for new installs). Organizations will need to make adjustments based on business processes or current configuration. You can import the file attached at the top of this page into the Opportunity Record Type Setting (rC_Giving__Opportunity_Record_Type_Setting__c) object using Apex Dataloader, Dataloader.io, or other dataloading tool.

4. Name - Corresponds to the name of the Giving record type. Recreate the record types currently used.

5. Transaction Name and Giving? - Used for records that have child record to track monetary values like Transaction or Pledge Payment. For existing record types that use 'Transaction' the name should be kept the same. If a Transaction Name is assigned then mark Giving? to TRUE. As of the Spring '15 release, only 'Transaction' is supported for automatic processing of charge card or EFT payments on their close date.

6. Enable NP? and Enable HE? - Assign based on type of organization. This setting will be utilized to a greater extent in the future.

7. Hard Credits? - Allows rollups of Hard Credits on Account and/or Contact from Giving records. (Note that some Account Hard Credit Rollups require Summary records)

8. Track Account Hard Credits & Track Contact Hard Credits - Hard Credits? must also be checked if either of these fields is checked. Indicate whether this record type can generate hard credits for Account and/or Contact. Note that the Disable Rollup HardCredits? field in the Account Setting and/or Contact Setting custom settings object needs to be FALSE for Hard Credits to calculate.

9. Summaries? and Activity Type - Specify one record type to generate Summaries. The default in prior releases was Membership. This will support multiple record type summaries in the near future. For the record type that has Summaries, make the Activity Type the same name as the record type name.

10. Default Page - Specify user experience by record type: NP Giving Wizard ("NP"), Basic Gift Entry (beta) "Basic", HE Giving Wizard ("HE") (Advancement nomenclature), or SFDC Standard layout "Standard").

11. Soft Credits? - Allows rollups of Soft Credits on Account and Contact from Giving records. 12. Giving Type Engine - Primarily affects record types with Summaries. Engines available are

Standard, Calendar Year, Fiscal Year, and Public Media. 13. Displayed Sections - For record types using the NP Giving Wizard, control the section

displayed to users. Review field help text for available sections/tabs. If sections are specified, they must be strictly comma-delimited. No extra spaces permitted before or after the comma.

Fields not mentioned above and/or with @WIP in the field label are reserved for future functionality and can be left blank.


Giving Level record configuration • In order for a Summary to be correctly generated for each of your record types a

corresponding Giving Level must exist for it. • If you want Summaries to appear for the Donation record type you will need to create at

least one Summary, this can be as simple as a record with a Min value of $0.01 and no maximum. • However, the Activity Type must say Donation and the Period Type must be defined if

Fiscal Year and Calendar Year (blank if using Standard/Public Media membership giving type engines).

• Note in some instances the only Activity Type available to be selected is “membership” you can change this by going to Setup | Create | Objects | Giving Level and finding the field called Activity type. Click on the Field Name and then scroll down and select New picklist values. Add the other record types you want and click save

Giving Button and Link Visualforce page Redirect Configure the Opportunity object to use the Opportunity Record Type setting specified path for New record creation and record edits

1. Update the Opportunity New and Edit buttons to use the following VF page "Opportunity_RedirectRecordType"

2. Update any other links that are custom configured

Advancement Giving Wizard Functionality

• Contains Advancement Connect specific nomenclature and references • Functions similar to the standard Giving Wizard - entry sections are arranged in a vertical,

page layout order instead of horizontal, tabbed order

Configuration

1. Follow configuration from previous steps and set Default Page for Giving Record types to "HE"


Basic Gift Entry

Functionality

• Contains limited set of fields for quick gift entry • This feature is in beta

Configuration

1. Follow configuration from previous steps and set Default Page for Giving Record types to "Basic"

Membership Summary Expiration Date Override Functionality

• For organizations that use Membership Summaries • Manually override Summary Expiration Date to adjust or extend a donor's Membership • Subsequent Summaries generated will be based on the Custom Expiration Date

Configuration

1. Add the following field to the Summary page layout "Custom Expiration Date"

Note - Custom Expiration Dates will get reset if Recalculate Giving Summaries is run on the Account with a custom Membership.


Contact Level Giving Functionality

• Giving records can have direct association to Contacts allowing Giving to display in Contact related lists

• Contact is specified on the standard page layout for Giving Types except giving types that use the HE Advancement Wizard where the field is populated directly on the VF page

• Giving Hard Credits can be configured to rollup to Contact (outlined in the next step)

Configuration

1. Add the following field to Giving page layouts "Hard Credit Contact"

Contact Level Hard Credits

Functionality

• Hard Credit Amounts are rolled up to new Contact level fields when Contact is specified as the Hard Credit Contact on Giving records

Configuration

1. See previous step to set Contact as the Hard Credit Contact 2. Add the following the Hard Credit related fields to the Contact page layout by searching for

"Hard Credit" and adding the selection

Note - There is a custom setting for Contact (in rC_Giving) "Rollup Hard Credits Batch?". This must remain FALSE for hard credit rollups to work because the batch job is not yet implemented.

Other Page Layout updates Configuration


1. Update Pledge and Outright Gift page layouts - typically these align to the existing Donation record type

2. Update the Pledge Payment page layout - typically this aligns to the existing Transaction record type


Connect Winter Release from Connect 2.17

Winter Release - rC Connect package

Litle Payment Processing Follow the Implementation Guide articles for Litle under "Payment Processing"

Batch Gift Entry Functionality

• This Batch Gift Entry tool is a unique app that sits on Batch Upload for quick data entry • The previous Batch Gift Entry tool is still accessible directly in your org if desired

Configuration

1. Navigate to the following URL each time for access - https://rc-batchentry.herokuapp.com/#/home

2. Continue through the URL 3. Login with your Salesforce credentials and grant permission to the app

Automatic Soft Credits based on Relationships Functionality

• Automatically create Soft Credits based on Relationships • Only Operates if “Primary Contact” field is populated on create.

• Either, create Gift from “Giving (Primary Contact)” related list on Contact Page. • OR Add primary Contact to Giving Wizard Manage Fieldset and populate Contact

manually. To do this go to Setup | Customize | Opportunities | Fieldsets find the Fieldset for the record types that you are using (ManageDonation, ManageMembership, ManagePledge etc… ) Drag the Primary Contact field onto the select fields list. Save.

Configuration

1. Add the following values to fields on the Relationship object Setup | Create | Objects | Relationships 1. Add “Auto Credit” as a value to the Category field. Make sure to make it available for all

record types 2. Add the values of “Giver” and “Recipient” to Role 1 and Role 2 fields. Agaian, make sure to

grant access to record types.


https://rc-batchentry.herokuapp.com/#/home

https://rc-batchentry.herokuapp.com/#/home

3. Role 1 and 2 are both dependent fields of Category, after saving your additions, go to the Rol 1 and Role 2 fields, look for the Picklist options section and next to Category click Edit. Find the column labelled Auto Credit and double click on Giver and Recipient to activate those values. Save.

Donor Profile Report (on Contact) Functionality

• Create custom reports of aggregated Contact information that can be viewed in org, printed, or made into a PDF (similar to the Account level functionality)

Configuration

• Configure display by customizing the custom setting "Contact Donor Profile Report" • Add the "Donor Profile Report" button to Contact page layouts

Payment Grouping and Charge Processing Functionality

• Groups payment transactions within specified time period use the same Credit Card Payment Method, have the same Account, have the same Pricebook

• Processes grouped payment transactions in one single transaction to payment vendor configured

• Grouping is a manual process and uses the Developer Console at this time.

Configuration

1. Add Related lists for "Contracts" and "Orders" to the Account page layout (not required - allows easier view of the payment grouping process)

2. Run the following job as Anonymous Apex Code "Database.executeBatch(new rC_Giving.Account_UpdateOrdersBatchable('pricebookEntry.Id','groupingType'),1);" - Set the Pricebook ID between the first set of single quotes, Set the Grouping Type as Day, Week, or Month between the second set of single quotes.

Note: Grouping Types are based on calendar basis. Day = today. Week = Current calendar week starting Sunday. Month = Current calendar month starting with the first day of the month.


Advancement Connect Winter Release Upgrade

Guide


Advancement Connect: Package Versions and Structure

Winter Release

Package Versions At the time of release, the Winter Release includes

• Bios 2.19 • Education 1.0 • Giving 2.22 • Inventory 1.8 • Connect 2.18 • Volunteers 1.5 • Events 1.18

Package Structure

Advancement Connect is composed of the above components. There are four core packages that make up Advancement Connect with Events and Volunteers available with Advancement Connect licensing as well.


Education Winter Release

Spring Release - rC_Education 1.1 package

Education and Education History Functionality

• Track the full educational history of a constituent including college and university, enrollment and graduation years, degree type, GPA, major and minor.

Configuration (Contact)

1. Go to Setup | Customize | Contacts | Page Layouts 2. Edit the Contact page layout(s) in use 3. Add the Education related list to the layout 4. Add ‘Class Year and Degree’ field to the layout 5. Save

Configuration (Account)

1. Go to Setup | Customize | Accounts | Page Layouts 2. Edit the Account page layout(s) in use 3. Add the Education related list to the layout 4. Add ‘Class Year and Degree’ field to the layout 5. Save

Communication Method Functionality

• The standard platform allows you to track a variety, though limited number, of phone, email and url communication methods for a Contact. This new feature enables unlimited communication types to be added along with opt ins and outs.


1. Go to Setup | Customize | Contacts | Page Layouts 2. Edit the Contact page layout(s) in use 3. Add the Communication Method related list to the layout 4. Save


1. Go to Setup | Customize | Accounts | Page Layouts


2. Edit the Account page layout(s) in use 3. Add the Communication Method related list to the layout 4. Save

Stage History details Functionality

• Each Account, Contact, and Proposal contains a Stage field • Proposal stage tracking can be used to indicate appropriate stage in the Ask timeline for this

Proposal. Each Stage will reflect a Probability % of closing the Proposal. • As you move close to being awarded a gift from a donor users should update the Stage to

indicate how close they are to completion. • Whereas, account and contact stage tracking can be used to track the stage history of a

prospect irrespective of a proposal. • Stage history will be auto-tracked every time the stage field is updated including number of

days in each stage and start/end dates. • The stage history record is automatically created when the stage is changed on the

individual, household, or proposal.


1. Go to Setup | Customize | Contacts | Page Layouts 2. Edit the Contact page layout(s) in use 3. Add the Stage History related list to the layout 4. Add ‘Stage’ field to the layout 5. Save 6. Go to Setup | Customize | Contacts | Record Types 7. Click record type in use 8. Edit Stage 9. Select an item from the Available Values list and add it to the Selected Values list to include it

as a picklist value for this Record Type 10. Repeat for all applicable record types 11. Save


1. Go to Setup | Customize | Accounts | Page Layouts 2. Edit the Account page layout(s) in use 3. Add the Stage History related list to the layout 4. Add ‘Stage’ field to the layout 5. Save 6. Go to Setup | Customize | Accounts | Record Types 7. Click record type in use 8. Edit Stage 9. Select an item from the Available Values list and add it to the Selected Values list to include it

as a picklist value for this Record Type 10. Repeat for all applicable record types


11. Save

Configuration (Opportunity)

1. Go to Setup | Customize | Opportunities | Page Layouts 2. Edit the Opportunity page layout(s) in use 3. Add the Stage History related list to the layout 4. Add ‘Stage’ field to the layout 5. Save 6. Go to Setup | Customize | Opportunities | Record Types 7. Click record type in use 8. Edit Stage 9. Select an item from the Available Values list and add it to the Selected Values list to include it

as a picklist value for this Record Type 10. Repeat for all applicable record types 11. Save

Teams for Prospecting Functionality

• Track the work being done by team across all your prospects, both high and low value. • Enable teamwork across Households, Organizations, People, and Contact Reports


1. Go to Setup | Customize | Contacts | Page Layouts 2. Edit the Contact page layout(s) in use 3. Add Contact_Display Teams VisualForce component to the layout 4. Save


1. Go to Setup | Customize | Accounts | Page Layouts 2. Edit the Account page layout(s) in use 3. Add Account_Display Teams VisualForce component to the layout 4. Save

Configuration (Activity Events)

1. Go to Setup | Customize | Opportunities | Page Layouts 2. Edit the Opportunity page layout(s) in use 3. Add Event_Display Teams VisualForce component to the layout 4. Save

Configuration (Team Roles)

1. Go to Setup | Create | Objects | Relationship | Category 2. Add 'Team Member' as new picklist value 3. Save


4. Go to Setup | Create | Objects | Relationship | Role1 5. Add client-specific team roles as new picklist values (i.e. Major Gift Officer) 6. Save 7. Go to Setup | Create | Objects | Relationship | Category 8. Edit Category Field Dependencies for Dependent Field 'Role1' in field dependency section to

include the values (yellow highlight) that you want to show in the Team Member Role picklist 9. Include Values and Save


Package Upgrades and Custom Settings


Removing Deprecated Custom Setting fields

Custom Setting that are deprecated and deleted as part of package development will need to be deleted manually after upgrade to ensure full management functionality of custom settings.

The steps below outline the process for one if the Custom Settings that needs updated post install. There will be others that need the same update. Package Upgrade Notes for your package version will list the Custom Settings for update if possible.

Sample Error

This error can show when clicking 'Manage' next to a Custom Setting where fields need to be manually deleted. If it does, first try the steps below before contacting support.

Navigate to Custom Setting object

To manage custom settings for field removal

1. In Custom Settings, click the link text for the Custom Setting. In this case "Campaign Product Management"


Delete fields removed from the roundCause package

1. Click the 'Del' link next to all roundCause fields that have the option (roundCause fields have the 'rC' prefix in the API Name column)

Manage the updated Custom Setting 1. Navigate to Custom Settings 2. Click the 'Manage' link next to the Custom Setting


rC Bios Upgrade Guide


Upgrading from Bios 2.10 to Bios 2.11

This article outlines the specific configuration steps required or recommended to upgrade to Bios 2.11 when Bios 2.10 is currently installed.

Update Relationship object picklist values to support two new record types Recommended - These updates ensure support for the Contact - Giving and Account - Giving record types that are new in Bios 2.11. The configuration below is minimal and meant to support the roundCause Sponsorship package, but there are many other possible use cases that can be defined.

1. Go to Setup -> Create -> Objects 2. Select the Relationships custom object 3. Update the picklists as follows

Category - Add "Sponsorship" Role 1 - Add "Sponsor", "Participant", and "Sponsorship Giving" Role 2 - Add "Sponsor", "Participant", and "Sponsorship Giving"

Update Giving page layouts to support Relationships Recommended - These steps are necessary if Relationships will be created from Giving records or need to be viewed on Giving records.

1. Go to Setup -> Customize -> Opportunities -> Page Layouts 2. Select the layout that needs to be updated 3. Add the 'Manage Relationships' button to the layout 4. Add the Relationships object related list to the layout 5. Configure the Relationships related list with the following order of column titles: Reference

#, Category, Role 2, Account To, Contact To, Role 1, Active?

Note: When Account - Giving or Contact - Giving relationships are created, the Account or Contact is always in the Account To or Contact To fields respectively.


rC Giving Upgrade Guide


Upgrading to Giving 2.16

Giving 2.16

Page Layout additions Add the following fields to the object page layouts listed:

• Giving Levels - Period Type • Summaries - Custom Expiration Date

Picklist Values additions Add the following values to the object picklist fields listed:

Giving Levels - Period Type

• Calendar Year • Fiscal Year

Opportunity - Giving Type Engine

• Calendar Year • Fiscal Year

Configuring Giving Levels

Also see the Data Updates step below for existing data.


Membership Giving Levels must not have a value in the Giving Level - Period Type field unless the Giving Type Engine default is cleared out, and defaults are defined via record type instead for each, Membership, Donation, and Purchase. This field is used only for Donation and Purchase Giving Levels.

See the above example of a configuration. There can be differences between the configuration of different Activity Types. They key difference that must exist is the Period Type setting.

Data Updates The following data updates to new fields are required based on the object and fields listed:

Giving Levels - Memberships

• No updated necessary. Giving Levels - Period Type should remain blank for Memberships unless special configuration is performed.

Giving Levels - Donation and Purchase

• Create Giving Level with Activity Type of Donation and Purchase to support Summaries for these record types if desired

• Set Giving Levels - Period Type to Calendar Year or Fiscal Year depending on period wanted. Remaining config is same as Membership.

Enable Basic Gift Entry Note: Basic Gift Entry does not support Donation or Purchase Giving Summaries by default. These Summaries require manual (or workflow) specification of Giving Type Engine.

1. Change the Opportunity Button action for New to use the VisualForce page "Opportunity_InsertBasicGift"

2. Update Opportunity Settings custom settings for the rC_Giving namespace to have "Enable Basic Gift Entry?" = TRUE

Custom Setting Management for Deprecated Fields Giving 2.16 deprecates and deletes a number of unused custom settings. At this time Admins must manually delete these Customs Settings after upgrading.

Follow the steps in this article to upgrade Custom Settings: http://roundcorner.screenstepslive.com/s/roundCause_Documentation/m/8404/l/269823-removing-deprecated-custom-setting-fields


http://roundcorner.screenstepslive.com/s/roundCause_Documentation/m/8404/l/269823-removing-deprecated-custom-setting-fields


Configure Giving Rollups (for Batch delayed rollup) The following Custom Settings need to be marked true to enable batch delayed rollups. They have related batch size (ending in "Batch Size") and batch run timing (ending in "Batch Delay") options that need to be set as well.

Account Setting (rC_Giving namespace)

• Rollup Summaries Batch? • Update Summaries Batch? • Rollup Hard Credits Batch? • Rollup Soft Credits Batch? • Rollup Affiliations Batch?

Contact Setting (rC_Giving namespace

• Rollup Soft Credits Batch?

Campaign Setting (rC_Giving namespace)

• Rollup Giving Batch?

With any of the above settings configured for batch rollups, execute the rollup management job. The one job will work for all the above settings. Campaign Rollups must be enabled for the job to run.

1. Open the Dev Console 2. Open the Execute Anonymous window 3. Run "new rC_Giving.rC_GivingAsyncRecovery().execute(null);"


rC Connect Upgrade Guide


Upgrading from Connect 2.11 to Connect 2.12

Upgrading to Connect 2.12 brings a major update to the way Payment Processing is handled. The upgrade should be tested thoroughly in a client sandbox prior to upgrade in Prod. The upgrade also requires a data migration to the simplified object model.

This article contains upgrade information toward the end that covers aspects of the upgrade configuration outside of the Payment Processing updates.

Disable the old Payment Processing configuration 1. Go to Setup -> Develop -> Custom Settings 2. Click the Manage link next to Payment Method Setting for the rC_Connect namespace 3. Ensure the following settings are checked (marked TRUE so that they are Disabled)

> Disable Insert Sage Vaults: Charge Card? > Disable Insert Sage Vaults: EFT? > Disable Insert Sage Vaults? > Disable Rollup Sage Vaults?

4. Go back to the main Custom Settings list and click the Manage link next to Opportunity Setting for the rC_Connect namespace

5. Ensure the following settings are checked (marked TRUE so that they are Disabled) > Disable Insert Heartland Transaction? > Disable Insert Sage Vault Bankcards? > Disable Insert Sage Vault VirtualChecks?

Further Configuration For additional customization of Payment Processing, refer to the article in the roundCause Administration Guide "Initial Payment Processor Setup".


Upgrading to Connect 2.17

Connect 2.17

Custom Settings Connect 2.17 deprecates and deletes a number of unused custom settings. At this time Admins must manually delete these Customs Settings after upgrading.

Follow the steps in this article to upgrade Custom Settings: http://roundcorner.screenstepslive.com/s/roundCause_Documentation/m/8404/l/269823-removing-deprecated-custom-setting-fields

Payment Processing Review Configuration for your Payment Processor(s) based on updated instructions in this Screensteps Chapter Initial Payment Processor Setup

Data Updates - Payment Method

1. Update every Payment Method record with the proper value in the Merchant Name field

Note: This value expected by payment processing is defined in the Payment Processing configuration in the previous step

Note: Most organization will have the same value in this field across all Payment Methods, the only reason for differing values is if multiple Payment Processors are configured in roundCause.




http://roundcorner.screenstepslive.com/s/roundCause_Documentation/m/12732/c/72846

Update Online Donation Form Payment Processing

Open any Online Donation Forms configured with Payment Processing

1. Ensure the desired Payment Processor is selected on the Form Flow


roundcause upgrade guide · to start creating a new account. 8. on the . select account record...

Documents