Overview
The Settings page contains options that allow you to configure settings controlling the behavior of Development Manager and users' preferences when interacting with the application. The illustration below identifies the main elements on the Settings page.
Note: You must have Diocesan Admin permissions assigned to your login credentials to view and modify information on the Settings page.
Administration Tab
Click Administration to display the Administration tab. This tab has two main sections:
DM Options
The options in this section are used to configure Development Manager. Use the checkboxes to enable or disable options. When a checkbox is selected, it appears as checked, and the option is enabled. Some options are pre-selected by default. You can deselect (disable) them by clicking your mouse inside the checkbox.
Only Batch Owner Can Modify Pledges in Batch
The person who initially creates a batch is considered the rightful owner. This option has two settings:
- Selected: Only the batch owner is permitted to change pledges in a batch.
- Not selected (default): All privileged users, including those who do not own the batch, can modify pledges in batches.
Note: A user with DDM Administrator access rights can override this option and change pledges in a batch.
Pledge Management - only show OBO Parishes with goals
Controls whether the OBO (On Behalf Of) Parishes list in pledge entry includes only the names of parishes that have goals configured.
This option has two settings:
- Selected (default): Only OBO parishes that have goals configured are available for selection (when adding or editing a pledge) in the On Behalf Of dropdown list in the pledge form.
- Not selected: All organizations in your database are available for selection (when adding or editing a pledge) in the On Behalf Of dropdown list on the pledge form.
Note: If you limit the OBO Parishes list to show only those organizations that have goals, but you need an organization that has no goals to be included in the list, you can add the desired organization to the list by specifying a zero-dollar goal.
Reset Appeal Code in Pledge Screen for every new Pledge
Controls whether the system displays a default value in the Appeal Code list for each newly created pledge.
This option has two settings:
- Selected: No default value appears in the Appeal Code list for new pledges.
- Not selected (default): The system displays the value selected for the previous pledge as the default in the Appeal Code list for each new pledge.
Display End Date for Pledge Entry
Displays the End date field in pledge data entry. The end date is the last date that payments can be posted to the pledge.
Import Behavior
These options give you finer control over how the system handles lockbox imports and contributions imported from Online Giving. Select one:
- Add Imported Pledge: The import process does not perform any validation checks for an additional active pledge. An active pledge is one with an end date that is either NULL or after today.
- Reject Imported Pledge: The import process checks for an additional active pledge associated with the same fund, family, and OBO organization. If a pledge matching this criteria is found, the process returns an error informing the user that an active pledge exists for the donor. An active pledge is one with an end date that is either NULL or after today.
-
Update Existing Pledge to Match Import: The import process checks for an additional active pledge. If one is found, it compares the value in the Adjusted Pledge Amount, Frequency, and Fulfillment Method fields. The process then does the following:
- If an imported contribution is attached to a pledge, the contribution is posted to the existing pledge with the Initial Contribution checkbox deselected (unchecked).
- Updates other fields in the existing pledge record, as necessary.
- If the value in the Amount field does not match, an adjustment is added to ensure the adjusted amount matches the amount in the imported record.
- If the values in the Frequency and Fulfillment Method fields do not match, change the values in these fields in the existing pledge record to match those in the imported record.
Show Donor Reports
Controls customer access to the Donor Reports module and, consequently, visibility of donor reports. This option has two settings:
- Selected (default): Displays the Donor Reports button, providing users with access to donor reports.
- Not selected: Hides the Donor Reports button, which prevents users from accessing donor reports.
Parish Refunds - show negative refunds
Controls whether negative refunds appear in Parish Refunds. This option has two settings:
- Selected: shows negative refunds.
- Not selected: hides negative refunds.
Enable Integration with Online Giving
Select the checkbox to activate the integration between Development Manager and Online Giving.
Important: This setting does not affect ParishSOFT Giving.
Organization ID
By default, the Development Manager uses the ParishSOFT ID (a unique identifier assigned by the ParishSOFT system) to identify parish organizations. If you prefer instead to use the organization ID assigned to parishes by your diocese, select the Local Org ID option from the dropdown list. After you make the change, the organization ID assigned to a parish by your diocese will appear on the following reports:
- Parish Master
- Designation Details
- Parish Date Over Goal
- Periodic Report
- Parish Roster
- Parish Refund/Shortfall
Additionally, the organization ID assigned by your diocese can be used when importing goal, shortfall, or refund data. Enter the organization ID into the OrgID field in the file you are importing.
Note: Local organization IDs for parishes are set on the Organizations page in the Administration module. The Local Org ID field in each organization's record is where the value is saved.
Development Organization
This field contains a list of all organizations in the diocese. The organization selected from this list appears in the header of all Development Manager reports and is displayed in the top-right corner of every page after the user logs in. The selected organization is responsible for managing the diocese's campaigns. The organization may be the diocese itself or an office, such as the Office of Development.
Batch Management
The options in this section are used to govern batch control in Development Manager. Use the checkboxes to enable or disable options. When a checkbox is selected, it appears as checked and the option is enabled. Note that some options are pre-selected by default. You can deselect (disable) them by clicking your mouse inside the checkbox to remove the checkmark.
Require Contribution Batches
Controls whether all contributions entered into the Development Manager must be entered by batch to be successfully saved.
This option has two settings:
- Selected (default): Batches are required. Batches are required for posting contributions.
- Not selected: Batches are optional and are not required for posting contributions.
Require Pledge Batches
Controls whether all pledges entered into the Development Manager must be entered by batch to be successfully saved.
This option has two settings:
- Selected (default): Batches are required. Batches are required for posting pledges. You cannot post a pledge outside of a batch.
- Not selected: Batches are optional and are not required for posting pledges. You can post a pledge outside of a batch.
Allow multiple funds per batch
Controls whether a batch can contain pledges or contributions for different funds.
This option has two settings:
- Selected: the account setup on the batch is the default fund for new pledges and contributions. However, the user can override the fund as needed at the individual pledge or contribution level.
- Not Selected: all postings in a batch must be to the same fund.
Batch Posting - Use Pledges by Default
Allows a user with the appropriate permissions to set the default value of the Batch uses pledges checkbox in the setup for all new batches (for a description of the Batch uses pledges checkbox, go to Batch Record Details).
This option has two settings:
- Selected: As illustrated in the batch data entry form below, this sets the default value of the Batch uses pledges checkbox to "true" (checked) for all new batches. When the value is "true", the system searches the database to locate a pledge that matches the contributions before posting them to a batch. If a matching pledge is found, the system links it to the contribution and displays the pledge icon next to the contribution record in the batch.
Note: Depending on the number of pledges in your database, selecting this option can slow data entry because the system needs time to locate a matching pledge.
- Not selected: In the data entry form for new batches, set the default value of the Batch uses pledges checkbox to "false" (unchecked) for all new batches. When the value is "false", the system does not search the database for a pledge to match posted contributions to. Contributions posted to batches are not linked to pledges, and no pledge icon is displayed next to contribution records in batches.
Important: A user can override the default value of the Batch uses pledges checkbox locally within a specific batch. This is easily done by changing the checkbox value in the batch from checked to unchecked, and vice versa. However, the user must make this change before saving the batch, as the system does not allow changes after a batch is saved. Additionally, a change made locally applies only to the specific batch.
Allow OBO changes even if batch is closed
This option has two settings:
- Selected: pledges can accept OBO changes even after the batch containing the pledges is closed.
- Not selected: OBO changes are not allowed.
Batch Posting - Enable Check # field by default
A global control that determines whether the Check Number field is displayed and included in the Tab key sequence for contribution posting for all newly created batches.
Note: This option sets the default display of the Check Number field for new batches. You can override the global setting when creating a new batch. In other words, you can enable the display of the field here, but select not to display the field when you create a specific batch.
This option has two settings:
- Selected: the Check Number field is enabled and included in the Tab key sequence for payment and contribution posting.
- Not selected: the Check Number field is disabled and skipped in the Tab key sequence for payment and contribution posting.
Batch Posting - Enable Memo field by default
A global control that determines whether the Memo field is displayed and included in the Tab key sequence for contribution posting for all newly created batches.
Note: This option sets the default display of the Memo field for all new batches. A user can override the global setting when creating a new batch. In other words, you can enable or disable the display of the field here, but a user can select not to display (or select to display) the field when creating a specific batch.
This option has two settings:
- Selected: the Memo field is enabled and included in the Tab key sequence for payment and contribution posting.
- Not selected: the Memo field is disabled and skipped in the Tab key sequence for payment and contribution posting.
Batch Posting - Use Quick Posting by Default
A global control that determines whether the Batch Uses Quick Posting option in the batch form is pre-selected when a parish user creates a new batch.
Note: This option sets the default display of the Memo field for all new batches. A user can override the global setting when creating a new batch. In other words, you can enable/disable a batch to use quick posting here, but a user can select not to use (or select to use) the functionality when creating a specific batch.
The option has two settings:
- Selected: The Batch Uses Quick Posting option is enabled (selected by default) in the batch form when a parish user creates a new batch.
- Not selected: The Batch Uses Quick Posting option is disabled in the batch form when a parish user creates a new batch.
Batch Posting - Default Contributions Default Family lookup
In this dropdown list, select the default search field for batch data entry. When the user posts a contribution to a batch, the system uses the default search field to match the posting on.
- Family ID: Sets the Family DUID, a unique ID used to identify each family, as the default lookup value.
- Member ID: Sets the Member DUID, a unique ID used to identify each member, as the default lookup value.
- Diocesan ID: Sets the Diocesan ID, a unique ID used to identify each family, as the default lookup value. Some organizations are set up to use the Diocesan ID instead of the Family DUID to identify families. This setup is done in the ParishSOFT Family Suite Administration module.
- Pledge ID: Sets the Pledge ID, a unique value used to identify a pledge, as the default lookup value.
- Family Name: Sets the family's last name as the default lookup value.
- Member Name: Sets the member's last name as the default lookup value.
- Family ID and Family Name: Sets the Family ID and Family Name as the default lookup fields in the data entry form for batches. In the data entry form, the Family ID and Family Name data are split into separate fields.
- Member ID and Member Name: Sets the Member ID and Member Name as the default lookup fields in the data entry form for batches. In the data entry form, the Member ID and Member Name data are split into separate fields.
System Tab
System Tab Click System to display the System tab. As illustrated below, this tab has two main sections:
File Import Setup
The options in this section are used to configure settings that govern file imports into Development Manager. Use the checkboxes to enable or disable options. When a checkbox is selected, it appears as checked, and the option is enabled.
Note: Some options are pre-selected by default. You can deselect (disable) them by clicking your mouse inside the checkbox.
Show ONLINE GIVING PLEDGE File Import
Controls whether the pledge file type for Online Giving is displayed in the file format list on the Imports tab. This option has two settings:
- Selected: The pledge file type for Online Giving is displayed in the file format list on the Imports tab.
- Not Selected (default): The pledge file type for Online Giving is not displayed in the file format list on the Imports tab.
Show ONLINE GIVING CONTRIBUTION File Import
Controls whether the contribution file type for Online Giving is displayed in the file format list on the Imports tab. This option has two settings:
- Selected: The contribution file type for Online Giving is displayed in the file format list on the Imports tab.
- Not Selected (default): The contribution file type for Online Giving is not displayed in the file format list on the Imports tab.
Allow LOCKBOX Import
Controls the ability of the Diocese to import contribution data using Lockbox banking.
ACKNOWLEDGEMENT RESPONSE Files Import
The Default Acknowledgement Response Format option allows customers to import a file into Development Manager that contains their organization’s pledge acknowledgement data.
Other Setup
As the name implies, this group contains additional setup options. Use the checkboxes to enable or disable options. When a checkbox is selected, it appears as checked, and the option is enabled.
Note: Some options are pre-selected by default. You can deselect (disable) them by clicking your mouse inside the checkbox.
Auto-Generate Diocesan ID
Controls whether users are allowed to edit the Diocesan ID field. This option has two settings:
- Selected: Prevents users from editing the value in the Diocesan ID field. The system automatically generates a Diocesan ID for each newly added family.
- Not Selected: Allows users to edit the Diocesan ID field. The field accepts integer values.
Show Online Giving Management
Controls access to Online Giving Management features. This option has two settings:
- Selected: Allows users to access Online Giving Management.
- Not Selected: Prevents users from accessing Online Giving Management.
Note: Neither the Online Giving Management menu option nor the Online Giving Management page tile is visible to users.
Show ACH CC Date
Controls whether the ACH Credit Card Date field is displayed in the payment area for pledge entry. This option has two settings:
- Selected: The ACH Credit Card Date field is displayed in the payment area for pledge entry.
- Not Selected: The ACH Credit Card Date field is not displayed in the payment area for pledge entry.
Lookups Tab
On this tab, you can manage lookup values for contribution types that users can select (from the Contribution Types dropdown list) when adding pledges and contributions to the system. You can add new lookup values, edit existing ones, and delete those you no longer use.
Add Lookup
Click to add a new contribution lookup value. Enter information into the Name and Code fields and, if desired, select the Active checkbox.
Edit
Click to edit the details for a lookup value.
Name field
Type a descriptive name for the lookup in this field. After you save the lookup value, the name you provided appears in the list on this page and in the dropdown lists throughout the application.
Code field
Type an abbreviation for the lookup. For example, you could type "Amex" for American Express or "MC" for Mastercard.
Active checkbox
Select this checkbox to make the lookup value visible to users, allowing them to select it from the Contribution Type dropdown list during pledge and contribution entry. If you do not want users to see the lookup value, leave the checkbox blank.
Note: The Active checkbox control can be quite helpful when setting up a lookup list. If you do not want users to see a particular lookup value immediately, leave the checkbox blank. When you are ready to give users the ability to select the value during pledge and contribution entry, select the checkbox and save the lookup. After you complete this step, the lookup is visible to users.
Save
Click to save a new lookup value or to save edits to an existing lookup value.
Undo
Before saving information entered for a lookup value, you can click to remove what you typed.
Delete
Click to remove a lookup value from the list. The system also removes the lookup value from associated lookup lists throughout the application.
Updated