SAGE FUNDRAISING Sage Fundraising 100 – Rainbow...

27
Sage Fundraising 100 – Rainbow Edition Version 7.0 SAGE FUNDRAISING RELEASE NOTES Proprietary Information These documents and the information they contain are proprietary to and considered a trade secret of Sage Software and shall not be copied without the authorization of Sage Software.

Transcript of SAGE FUNDRAISING Sage Fundraising 100 – Rainbow...

Page 1: SAGE FUNDRAISING Sage Fundraising 100 – Rainbow Editionfundraising_100rb.mip.com/FR100-RB-RelNotes-v7.pdf · 2013-05-09 · Overview Overview The following is a list of new features,

Sage Fundraising 100 – Rainbow Edition Version 7.0

SAGE FUNDRAISING

RELEASE NOTES

Proprietary Information These documents and the information they contain are proprietary to and considered a trade secret of Sage

Software and shall not be copied without the authorization of Sage Software.

Page 2: SAGE FUNDRAISING Sage Fundraising 100 – Rainbow Editionfundraising_100rb.mip.com/FR100-RB-RelNotes-v7.pdf · 2013-05-09 · Overview Overview The following is a list of new features,

Table of Contents

Contents Overview ..........................................................................................................................1 Version 7.0 New Features and Enhancements.............................................................1

Adhoc .......................................................................................................................................... 1 Campaign .................................................................................................................................... 2 Constituents/Profile Information .............................................................................................. 2 Designations/Funds................................................................................................................... 2 Endowment and Grants............................................................................................................. 3 Extras........................................................................................................................................... 5 Financial Data ............................................................................................................................. 5 Import .......................................................................................................................................... 6 Job Queue................................................................................................................................... 7 Miscellaneous............................................................................................................................. 7 Reports........................................................................................................................................ 8 Utilities......................................................................................................................................... 8 Volunteer Module ....................................................................................................................... 8

Version 7.0 Resolved Issues..........................................................................................9 Adhoc/Groups/Criteria............................................................................................................... 9 Awards....................................................................................................................................... 10 Campaign .................................................................................................................................. 10 Constituent/Profile Information .............................................................................................. 11 Designations/Funds................................................................................................................. 12 Endowments and Grants......................................................................................................... 14 Events........................................................................................................................................ 16 Financial Data ........................................................................................................................... 16 Forms......................................................................................................................................... 18 Import ........................................................................................................................................ 19 Job Queue................................................................................................................................. 20 Miscellaneous........................................................................................................................... 20 Projects & Tasks ...................................................................................................................... 22 Reports...................................................................................................................................... 22 Solicitation Manager ................................................................................................................ 24 Utilities....................................................................................................................................... 24

Page 3: SAGE FUNDRAISING Sage Fundraising 100 – Rainbow Editionfundraising_100rb.mip.com/FR100-RB-RelNotes-v7.pdf · 2013-05-09 · Overview Overview The following is a list of new features,

Overview

Overview

The following is a list of new features, enhancements and fixes that have been applied to Version 7.0 of Sage Fundraising 100 - Rainbow Edition software. More information regarding these changes is available in the online help distributed with your Sage Fundraising 100 - Rainbow Edition 7.0 system.

This guide is divided into sections based on Sage Fundraising 100 - Rainbow Edition version and revision. Within each version or revision items are divided into enhancements and fixes. The description of each item is followed by a number in parentheses. This number is an internal tracking number.

Page 4: SAGE FUNDRAISING Sage Fundraising 100 – Rainbow Editionfundraising_100rb.mip.com/FR100-RB-RelNotes-v7.pdf · 2013-05-09 · Overview Overview The following is a list of new features,

New Features and Enhancements

Version 7.0 New Features and Enhancements

Adhoc Adhocs: allow integration of selected Adhocs into the Run/Reports menu

You can now integrate selected Adhocs into Run/Reports using the Add to Run/Reports menu option. (6219)

Data being truncated in criteria prompts

In criteria prompts for asset pool codes and endowment IDs the field was not wide enough, causing descriptions to be truncated. The fields have been widened to allow users to view the full description. (5169)

Add Last Run fields for adhoc reports/export/merge

The Adhoc reports manager and the group manager views have two columns -- last edited by, and last edited, which only show when someone edited a report, not whether a report has been run. Three columns have been added to the view - "Last Run By" and "Last Run Date" and “Number Times Run” - in order to help identify groups and adhocs that are no longer being used. (6331)

Expose Credit Card Expiry Dates as redundant unencrypted field in Accounts Table for Adhoc / Criteria purposes

The credit card number and expiry date were stored as one value and encrypted together. Sites may need to report on the expiry date e.g. to alert donors when they have an upcoming scheduled payment with a credit card that will expire before the payment date. The fields have now been separated for reporting purposes. (6334)

When entering campaign year in Adhoc/Grouping/Criteria and Adhoc prompts the year needs to appear in descending sequence when presented in a dropdown list

Years now sort in descending order. (6335)

Criteria window - Change default for yes/no fields from no to yes

When one of the criteria items that requires a yes or no (Address Usage, Agency, Current, etc.) was selected, the default value in the choice was "No". Since the majority of times the preference is to use “yes”, the default was changed from “no” to “yes”. (6355)

Adhoc -- Field description adjustment in Export Layout and Composed field windows

The same field can be included multiple times in the same source but with different formatting options. For example, you could have "Acknowledgement Type (Code)" and "Acknowledgement Type (Description)". In the Export Layout and Composed Field Add/Edit windows, these fields would both appear just as "Acknowledgement Type". The formatting options are now visible, and therefore more distinguishable. (5896)

New adhoc sources were added

The following new adhoc sources were added to the system:

SOED Credited Event - the event that the parent solicitor credit record links to

NASOED Solicited Event Attendances - the event attendances for which this constituent has solicitor credit

NASOME Solicited Memberships - The memberships for which this constituent has solicitor credit

NASOPL Solicited Pledges - the pledges for which this constituent has solicitor credit

NASOGI Solicited Gifts - the gifts for which this constituent has solicitor credit

NASORV Solicited Receivables – (Common Receivable Data) - the receivables for which this constituent has solicitor credit. (6479)

Sage Fundraising 100 – Rainbow Edition v.7.0 Release Notes 1 April 2008

Page 5: SAGE FUNDRAISING Sage Fundraising 100 – Rainbow Editionfundraising_100rb.mip.com/FR100-RB-RelNotes-v7.pdf · 2013-05-09 · Overview Overview The following is a list of new features,

New Features and Enhancements

Campaign Campaign GL Account listing report modifications

The GL account listing report, accessed by clicking the Print button on the Campaign GL Interface window, has been modified to use standard heading and footings. Also, the Account Number field now wraps to a new line if it is too long. (6131)

New option for selecting default plus 1 in adhoc and group criteria

When specifying criteria using the campaign year, there is now a checkbox for specifying the Default Year +1. Previously, this option only allowed for selection of the default year minus, minus 2 and so on. (6196)

Constituents/Profile Information Add Corporate window: ‘Language Preference’ field added to Detail tab

A ‘Language Preference’ field has been added to the Detail tab of the Add Corporate window. (6181)

Address View – add right-click option to integrate Address View addresses with Google Maps

A right-click option to integrate ‘Address View’ addresses with a Google Maps has been added. (6190)

Right-click option to produce an MS-Word letter

A new ‘Quick Letter’ option function creates a letter in MS Word by merging the selected address’s name and address data with the specified Word Template file. (6193)

Adding a corporate/individual record should date and time stamp Edit Date and Time field and update User ID

Adding corporate records and spouses through a constituent only updated the Add Date and Time, while adding an individual updates Add Date and Time, Edit Date and Time, and updated the user ID. This functionality has been made consistent across all instances where constituents can be added, including Quick Entry, Import, adding constituents in relationships, memberships, event registration seating and sessions, employment, etc. (6250)

Save the user settings on the Name List - List of Possible duplicates window

When the Possible Duplicates window first appeared for a user, the Details portion was closed, causing the user to have to click to open it. The Details portion is now open by default during the first occurrence of the window for a user. The user can choose whether to leave this portion open or close it. When the user closes the Possible Duplicates window, the system holds the user’s settings. (6333)

Users can now permanently remove a payment from a confirmed deposit and replace it with another payment

In all cases, when a payment/gift/envelope content entry is removed from a confirmed deposit, the deposit status of the payment/gift/envelope content entry is now switched back to undeposited. Previously, it was kept as deposited/confirmed. (5658)

Alert display improved

The Alert window has been enhanced to display the note as the second column and by widening the Note column. (6461)

Designations/Funds Criteria: display problem Fund Code picker control

When editing an expression that used the Fund code and clicking the Value button, nothing was selected. To resolve this problem, the functionality of the fund picker box was enhanced. Users can now select funds by fund key. In the Fund Search window, the “By Program” page was replaced by a “By Code or Description” page. See the online help for more details. (5889)

Sage Fundraising 100 – Rainbow Edition v.7.0 Release Notes 2 April 2008

Page 6: SAGE FUNDRAISING Sage Fundraising 100 – Rainbow Editionfundraising_100rb.mip.com/FR100-RB-RelNotes-v7.pdf · 2013-05-09 · Overview Overview The following is a list of new features,

New Features and Enhancements

Endowment and Grants Grant Disbursement / Endowment Disbursement - date format inconsistent on display of check information

When a user displayed the check information for a grant disbursement or endowment disbursement by clicking the ‘...’ button beside the ‘Check Details’ field on the ‘View Disbursement’ or ‘View Endowment Disbursement’ window, the format of the dates displayed in this window were inconsistent. Some showed as '01/01/08' and others showed as '01 Jan 2008’. Now they all display in the longer format, using the month description, instead of number. (6241)

Approval Step Manager - add Select column heading to the grid column that displayed the checkmark

The Approval Step Manager has a column that shows a green checkmark if the step has been selected for the mass updating process. The column did not have a heading. It now has a heading of “Select”. Now users choosing the Manage Columns option on the right-click will see field names for all the grid columns. (6398)

Approval Step Selector window - Move decision amount to the beginning of the Details column

In Grant Proposals, Approval Steps, when adding an allocation approval step, the user selects a controlling decision approval step. The decision amount is displayed at the end of the Decision Making Body description, shown in the Details column. However, if the Decision Making Body description is long, the decision amount gets truncated, forcing the user to resize the selector window to its maximum. The decision amount is now shown at the beginning of the Details column so that the user doesn't have to resize the window to see it. (6399)

GL setup for Campaign/Endowment/Grants Management - widen segment name width for MIP

Previously, when the Segment Description was identified within FR100, there was a maximum of 10 characters. In MIP, the segment name can be up to 35 characters. Therefore, the segment description has been extended to match MIP. (6133)

Grant Proposals - store renewal key on base proposal so that it cannot be re-renewed accidentally

Previously, the same grant proposal could be renewed multiple times, which created duplicate proposal numbers and years. Now when a grant proposal is renewed, the new grant proposal key is stored on the proposal that was renewed. Then, if someone attempts to renew it again, they are not able to. The ‘Renewed Key’ has been added to the grant proposal grid on the Grant Proposal Manager and View. (6147)

Allocation approval steps - Controlling Step selector window shows only decisions that have not been fully allocated

When adding an allocation approval step to a grant proposal, you must select the decision step that is the parent controlling step. Previously, all decision steps were available for selection. Now, only decision steps that have not been fully allocated are shown in the selector window. (6148)

Approval Step Grid - show Decision Making body code & Allocation code in column information

In the Approval Step grid (visible on the Add/Edit Grant Proposal window, Grant Proposal view and Approval Step manager), the Funding Source code is now displayed in front of the description in the ‘Other’ grid column. Also, the Decision Making Body code displays in front of the description in the Type/Body grid column. (6149)

Grant Proposal window / view - expand on approval step and grant disbursement totals

Instead of having subtotals on each of the pages by the grid, a subtotal column is now available on the right of the Add/Edit window. This enables you to view all of the subtotals regardless of which page they are on. The following subtotal fields have also been added to the Add/Edit Grant Proposal window and the Grant Proposal view:

Total allocated amount, total approved decision amount, total disbursements entered, total disbursements approved, total disbursements exported, number of disbursements entered, number of disbursements approved, number of disbursements exported, approved amount, and allocation amount. (6160)

Sage Fundraising 100 – Rainbow Edition v.7.0 Release Notes 3 April 2008

Page 7: SAGE FUNDRAISING Sage Fundraising 100 – Rainbow Editionfundraising_100rb.mip.com/FR100-RB-RelNotes-v7.pdf · 2013-05-09 · Overview Overview The following is a list of new features,

New Features and Enhancements

Approval Step Model Smart Dates

The setup of approval step models has been enhanced to allow for a smart date calculation. If smart dates are active for a specific model, the ‘Date Required’ for the approval steps is automatically adjusted to fall in line with either the ‘Requested Date’ or the ‘Required Date’ of the grant proposal. (6166)

New Mass Fill Disbursements using Timing Codes utility

A new Mass Fill Disbursements using Timing Codes utility has been added to the Utilities->Grants Management menu. This utility asks for a year, as well as Grant Proposal criteria to identify which grant proposals are selected in the mass fill disbursements process. All grant proposals that have allocation approval steps with disbursement timing codes and that have had no disbursements generated for it are selected, and the disbursement schedule is built for these grant proposals using the timing code information on the allocation approval steps. (6167)

New Mass Renew Grant Proposals utility

A new Mass Renew Grant Proposals utility has been added to the Utilities->Grants Management menu. This utility asks for a base year, as well as Grant Proposal criteria to identify which grant proposals are selected in the mass renew process. All grant proposals that have not already been renewed and that match the selection criteria are automatically renewed for the next year. (6173)

Grant Proposal Manager & View - Filter based on year comparison

On the Grant Proposal Manager and View, in addition to being able to filter based on a specific year, you can now include a selection of either less than, greater than or equal to a specific year. (6197)

Grant Proposals - allow default Funding Source based on Decision Making Body

You can now identify a default Funding Source in Grants Management Setup, for use when adding allocation approval steps to a grant proposal. You can also specify a default Funding Source for a Decision Making Body. (6198)

New Mass Add Approval Steps utility

A new Mass Add Approval Steps utility has been added to the Utilities->Grants Management menu. This utility allows users to add approval steps to multiple grant proposals based on a specific approval step model. (6199)

New Mass Edit Decision Approval Steps utility

A new Mass Edit Decision Approval Steps utility has been added to the Utilities->Grants Management menu. This utility allows users to import the decision amount for existing decision steps on grant proposals for the upcoming year and flag the decision as completed. (6216)

Grant Proposal View/Manager - Disb. Schedule tab – new fields added

In both the Grant Proposal View and Manager windows, on the Disb. Schedule tab, when you choose the right-click ‘View’ option to see the detailed grant disbursement information, it now includes the user who created the disbursement, the create date, the user who approved the disbursement and the approved date. The same fields were added to the View Endowment Disbursement window. (6235, 6424)

Grant Proposal Number - change format of number to be right-justified

The proposal number for a grant proposal was left-justified. It has now been changed to right-justified, similar to other key fields, so that the proposal number can be sorted within a grid. (6236)

Allocation Approval Steps - add ability to tie to Directed Giving project and/or Receivable Key

An option to link a ‘Grant Allocation Step’ to a project for Directed Giving purposes was added to Allocation Approval Steps. Also, a link back to a receivable record was included, in case Directed Giving was not installed. Three new adhoc sources have been added so that the project and receivable information is available in adhoc. The Common Receivable source and Project source are now available from the Grant Approval Step - Allocation source, and the Grant Approval Step - Allocation source is available from the Project source. (6237)

Sage Fundraising 100 – Rainbow Edition v.7.0 Release Notes 4 April 2008

Page 8: SAGE FUNDRAISING Sage Fundraising 100 – Rainbow Editionfundraising_100rb.mip.com/FR100-RB-RelNotes-v7.pdf · 2013-05-09 · Overview Overview The following is a list of new features,

New Features and Enhancements

Extras Add Extras to Mailing History view

Extras have been added to Mailing History view. (6354)

Financial Data Installments grid on Membership and Pledge views and add/edit screen needs updating

The grids used for installments in the Pledge and Membership views and add/edit windows were not standard grids. They have been changed to standard grids. (6059)

In the DES Detail History view, the constituent name column does not sort correctly

In DES Detail History view, the Constituent Name column did not sort alphabetically because the ID number was part of the name. There is a separate ID column so the ID number was not required to be included in the format for the Constituent Name column. This problem has been resolved. (6163)

Collection Status currently must be visible on transactions in Quick Entry

Collection status was not available for inclusion on Quick Entry windows. It is now available so users can decide whether or not to make this field visible in their Quick Entry windows. (6314)

Designation Payout - cheque return/void run does not handle fees - this should be enhanced

If a Designation Payout had fees calculated and deducted from the payout amount, and a cheque return was done for the designation, the system did not factor in the fee that was charged to the agency. So, when the original payout was exported to an A/P package, it debited/credited the correct GL accounts, including the fee account. However, when the cheque return run was calculated, it did not look at the fees. The fee is now listed in the cheque return window and there is a new Return Fee Amount field that can be changed, as necessary. See the online help for more information. (5366)

Receivables: Add ability to designate a receivable as 'delinquent' on General Administration window

Users can now designate as delinquent those receivables that have not been paid in certain number of days. This feature was added for reporting purposes. A new control on the General Administration - Defaults Page allows system administrators to enter the number of days. The Pledge window now allows delinquent pledges to be colour-coded. (5687)

Response Code picker window should not display solicitations that are complete

In the receivable Add/Edit windows, the ‘...’ button beside the Response Code field displays a list of all un-responded mailing records for the donor. However, this list could get quite long, especially if the donor did not respond to direct mail items. To make this list more manageable, any solicitations that have been switched to a 'complete' status are now excluded. You can still type in a response code that corresponds to a complete solicitation, if needed. (6132)

Deposit Manager – Sorting problem on constituent ID

When a Deposit Slip was created, the ID number was being sorted as a character instead of a number so that 5 digit numbers were interspersed with 4 digit numbers, making it hard to cross-check reports to find a missing payment. The Result grid that appears when adding payments to a deposit has been modified to include a separate column for the ID and Name so users can sort on ID or name. (6338)

Envelope View Transactions Grid - Need to show the payment method description for pledges etc. in the envelope grid

The Envelope view/Transactions page was modified to include a Payment Method grid column. This column displays the payment method for pledges/gifts and payment type for payments. (6336)

Pledge view - convert pledge list to a grid, add colour definition

The Pledge view has been converted to a grid format and allows for colour coding based on a pledge’s balance status. (6350)

Sage Fundraising 100 – Rainbow Edition v.7.0 Release Notes 5 April 2008

Page 9: SAGE FUNDRAISING Sage Fundraising 100 – Rainbow Editionfundraising_100rb.mip.com/FR100-RB-RelNotes-v7.pdf · 2013-05-09 · Overview Overview The following is a list of new features,

New Features and Enhancements

Gift View - add additional grid columns

The Gift View was modified to show the following new columns: gift key, payment key, sub-appeal, workplace ID, workplace name, envelope key, summary flag, write-off amount, response code, anonymous flag, acknowledgement flag, acknowledgement type, base flag, user code, user data, EDI Flag, EDI payment method, Origin ID, Origin name, donor count, sponsor sheet key, project key, tax deductibility code, extra flag. The grid also saves and restores grid partitions from the last use of the view. (6352)

New System Administration allows sites to bypass data entry sessions for event registrations, even when DES are required by the system

A new option on the D/E Session tab of the General Administration window allows administrators to bypass the requirement for using a DES when entering event registrations. (6485)

Import Import of designations utilizing fund description - should stop the import if the fund description matches multiple funds

When receivables with designation information were imported and the import definition used the fund description to determine which fund to use, if the description matched multiple funds, the incorrect fund could easily be selected. The system now reports multiple matching funds as an error and does not import the transaction. (6423)

Import process - add ability of importing more than 255 characters for notes

You can now import notes longer of any length. (3926)

Import Check Information - modify procedure to work with MIP V8.1 and V9

The Import Check Information procedure was enhanced to work with V8.1 and V9 of MIP Fund Accounting. Also, the checking of valid version numbers for MIP has been removed. As long as the version is greater than 7, you are now allowed to run the Import Check Information process. (6224)

Import Duplicate Check needs to be converted to grids and to to show more information plus improve ability to cancel, save or save and finalize.

Various enhancements were made to the import duplicate check process, including:

• Using grids and showing additional data so users can do manual matching

• Changes to save and finalize options

• Sorting options.

See documentation for more information. (6332)

Enhance Import functionality to facilitate load of "Donate Now" data

Earlier, Sage Payment Solutions (SPS) introduced a 'Donate Now' feature for online giving, which is now used to increase annual fundraising. 'Donate Now' online transactions are stored in SPS servers, but they are not recorded by Sage Fundraising 100 software. With the introduction of Import of Donate Now data, you can now bring the Donate Now transactions processed through SPS into Sage Fundraising 100. Imported Donate Now transactions will contain the following data sources: Constituent, Address, Phone, Account (Credit Card), Gift (with a single fund designation), Tribute (optional). In the course of importing Donate Now transactions, you will run 2 pre-processing utilities, ‘Constituent Duplicate Check (System)’ and ‘Address duplicate check’, in order to attempt to match the data imported to existing records of constituents and addresses in the Sage Fundraising 100 database. A standard import definition will be supplied, and must be used, for the import of 'Donate Now' data. SPS transactions imported into Sage Fundraising 100 will be flagged in Sage Fundraising 100 with the new SPS status "Processed by 'Donate Now'". (6380)

Allow import of fund descriptions as an alternative to fund code/ fund key

Previously, you could import designations on receivables using a fund code or fund key. You can now also use a fund description. The description must be an exact match and only one record can be detected on the fund table to be considered a valid alternate match. (6381)

Sage Fundraising 100 – Rainbow Edition v.7.0 Release Notes 6 April 2008

Page 10: SAGE FUNDRAISING Sage Fundraising 100 – Rainbow Editionfundraising_100rb.mip.com/FR100-RB-RelNotes-v7.pdf · 2013-05-09 · Overview Overview The following is a list of new features,

New Features and Enhancements

New pre-processing option to check for duplicate addresses

This option checks imported addresses for duplicates existing in the Sage Fundraising100 database. If a duplicate address is found, the import treats the address being imported as already existing in the database. Otherwise, the address being imported is brought in as a new address. (6383)

Job Queue Job queue - do not allow user to authorize starting a job queue for another user who does not have authorization

Previously, if a user did not have security rights to start a job queue, another user with these rights could authorize it. However, this created problems when attempting to shut down the job queue, preventing the request from being processed. It is no longer possible to authorize the starting of a job queue for another user. (6154)

Job queue task crashes if users cancel their email notification during this process

An error occurred when users canceled the email notification during the job queue running process (i.e. selecting the "No" option when the system was trying to access Outlook to send out the email notification). (6231)

Miscellaneous Standard controls should allow right-click option when disabled

Right-click options were not previously available on disabled fields. The functionality has been changed to allow right-click options on disabled fields. (5617)

Note & Attribute Type lookup codes - Owner can be incorrectly identified at each level

For Note Type and Attribute Type codes you could identify an owner at each of the levels of the code and they could be different. The program has been modified so that if the top code has an owner, all sub-codes will automatically have the same owner. Note that if the top code has Everyone as the owner, then its subcodes can have a different owner. (6107)

If password character length exceeds 10, a warning is needed

The system only allowed a maximum of 10 characters for the user login password but did not prevent the user from entering more than 10 characters and did not give the user any feedback when they exceeded the limit when creating a password. Users are no longer allowed to save a password that is greater than 10 characters in length. (6317)

Allow the Sage Fundraising 100 - Rainbow Edition to startup in non full-screen and remember settings from last logout

Users with large monitors do not necessarily want the system to start up in full-screen mode. The system can now start in non full-screen mode and remember the settings from last logout. (6404)

Generic grid export to Excel

From certain grids, you can right-click and select an Export to Excel option to export grid data in Excel format. The grids where this feature is enabled are: Pledge View List page, Pledge View Designations List (Detail 1 page), Transaction History view (whether opened from a view or the Tools menu). (6185)

Add "Manage Columns" and "Hide Column" to UserGrid

Right-click functionality on grid columns now includes a Manage Columns option to move columns in the grid, and a Hide Columns option to remove columns from a grid. (6194)

Max number of Favorites increased from 10 to 20

The maximum number of favorites that a user can specify has been increased from 10 to 20. (6218)

Sage Fundraising 100 Microsoft Vista Compatibility

Sage Fundraising 100 is now compatible with the Microsoft Vista operating system. (6229)

Sage Fundraising 100 – Rainbow Edition v.7.0 Release Notes 7 April 2008

Page 11: SAGE FUNDRAISING Sage Fundraising 100 – Rainbow Editionfundraising_100rb.mip.com/FR100-RB-RelNotes-v7.pdf · 2013-05-09 · Overview Overview The following is a list of new features,

New Features and Enhancements

Reports Campaign Monitoring report removed

The Campaign Monitoring report has been removed from the system. The Campaign Monitoring with Leaders report is still available for use. (6337)

Campaign Monitoring Report with Leaders (R0_0302): Raw Data Export

A Raw Data Export option has been added to the Campaign Monitoring Report with Leaders. (6369)

Utilities Mass Edit Allocation Timing Codes utility

A new ‘Mass Edit Allocation Timing Codes’ utility has been added to the Utilities->Grants Management menu. It allows you to mass edit disbursement timing codes associated with existing allocation approval steps for grant proposals. (6175)

New Mass Edit Owner utility

A new utility enables you to transfer rights between owners or between departments. This utility is designed to assist with the transfer of responsibilities after staff changes. It is available on the Utility menu. Users must be granted security access to this utility by a system administrator. (6339)

Mass Add improvements

A new Source drop down box enables users to choose a source to mass add attributes and notes to, for example, financial sources, grants, endowments and so on. Note that some items, like involvements, mailings and workers, can only be added to constituents. In these cases, the Constituent source is automatically selected and the field is disabled. (6416)

Volunteer Module A new Volunteer Management module has been added and integrated with Projects and Tasks. See online help for details. (6251)

A matching tool is included in the Volunteer Management module to automate the process of matching volunteers with volunteer opportunities. (6347)

Three new Volunteer reports have been added: Monthly Volunteer Hours, Monthly Volunteer Activity, and Volunteer Training Class Lists. (6358)

Sage Fundraising 100 – Rainbow Edition v.7.0 Release Notes 8 April 2008

Page 12: SAGE FUNDRAISING Sage Fundraising 100 – Rainbow Editionfundraising_100rb.mip.com/FR100-RB-RelNotes-v7.pdf · 2013-05-09 · Overview Overview The following is a list of new features,

Resolved Issues

Version 7.0 Resolved Issues

Adhoc/Groups/Criteria Adhoc -- spaces in temp path cause Error 10 while running some Adhocs

This error only affected adhocs using composed fields or codes expanded into descriptions or encrypted fields. The error occurred when the temp file path had spaces in it. This problem has been resolved. (4895)

Secured constituent name can be viewed in the List Editor in Groups

The names of secured constituents would appear in the List Editor of the Group Manager. The Group Manager was modified so that when a user edits a manual list, if any constituents are secured, their name will not show. Note that the user can only add a secured constituent to a manual list if the user is the owner or has admin rights to secured constituents. As well, the import of manual records was modified to set the name to 'Secured' if a constituent is secured. (5115)

Adhoc Manager - Adhoc Ownership Rights only enforced if user clicked on Adhoc in the grid

If you clicked into the grid on an Adhoc and then used the keyboard arrow keys to scroll to another Adhoc, you would have full access to edit the selected Adhoc, regardless of your rights to that Adhoc. Only by clicking directly onto the Adhoc would the proper rights be observed. (This only concerns the Owner/Public rights issues, if you were not allowed to Edit Adhocs at all, it worked properly). This issue has been resolved. (6232)

Adhoc error with the "Common receivable" source

In some circumstances, creating an adhoc with the Designation source --> Common Receivable source --> Tribute source --> Tributee source or Common Receivable source --> Tribute source --> Tributee source could cause the following error: Error 1, File ‘.dbf does not exist. This problem has been resolved. (6260)

AdHoc: Incorrect behaviour of Automatic Suppression of Repeated Values

To improve the clarity of reports, Adhoc attempts to suppress repeated adjacent values according to specific rules. Because of an error in the sort-based suppression, the incorrect values were sometimes being suppressed. This could result in dollar amounts missing from reports, for example:

Payment Type Name Amount

CASH Bob Ace $100

(suppressed) Jill Hill $350

(suppressed) John Jones $5

Total for Payment Type $455

This sort-based suppression has been corrected. Also, the program has been changed to prevent the sort-based suppression from ever being applied to numeric fields. (6268)

Adhoc reporting – page header and footer would not print on final page

The Adhoc reporting page header and footer would not print on the final page if it only contained grand totals/counts. This issue has been resolved. (6292)

Adhoc: the "parent fund" source does not display anything

In adhocs with a parent fund source and a child fund source (that included fund and description fields), the child source would display the correct data on the report but the parent source would not display anything. This problem has been resolved. (6310)

Adhoc/Membership - SQL error

In Adhoc/Membership, an SQL error occurred when using Adhoc/Membership that looked for GL History. This issue has been resolved. (6312)

Sage Fundraising 100 – Rainbow Edition v.7.0 Release Notes 9 April 2008

Page 13: SAGE FUNDRAISING Sage Fundraising 100 – Rainbow Editionfundraising_100rb.mip.com/FR100-RB-RelNotes-v7.pdf · 2013-05-09 · Overview Overview The following is a list of new features,

Resolved Issues

Adhoc Criteria: The "Choose a Criteria Snippet..." popup was not filtering snippets correctly

In previous versions, the following problem with criteria snippets in Adhoc was identified. The correct snippets were shown in the first source, but no snippets appeared for a sub-source and although the filter was red, no master source matching the source you were on was listed. Snippets were only available for selecting if you turned off the filter. However, then you saw every snippet, regardless of whether it was applicable to the source. This issue has been resolved. (6318)

Groups: User can open multiple sessions of Group Manager

Users can no longer open multiple instances of Group Manager from the main menu. (6319)

Criteria error in "Common receivable + HAS Envelope" - Column 'EV_VLKEY' is not found."

This error could occur when using the Common Receivable Has Envelope sources and including the Envelope number field in the Has Envelope source. This problem has been resolved. (6385)

Adhoc Reports - Transfer to Email Rainbow Support causes error if user answers No to M/S Office access

If a user attempted to transfer out an adhoc report, export, or merge to Rainbow Support, M/S Office could prompt the user to allow access to MS Outlook. If the user answerd No to get access, the following error occurred: Number 1943, Message: Member RECIPIENTS does not evaluate to an object. This problem has been resolved. (6468)

Awards Award Level Description field does not display in Acknowledgement merge data file or Adhoc Export

The field is now present in both acknowledgment merges and adhoc exports. (6378)

Campaign Add Year to Campaign processing -- too many qSQL.Build updates in a single transaction

In certain circumstances, when linking a structure with constituent assignments to a new campaign year, too many qSQL.Build updates could cause the system to hang. This problem has been resolved. (4691)

Error during Export to Excel from Campaign Information view

From the Campaign Information view/Designation Detail tab, the Export to Excel could cause error “1426 OLE error code 0x800a03ec: Unknown COM status code” for constituents with large volumes of designations. If the volume of designations is too great, the system will report the error and give the user an option to exit. (6276)

Users were able to enter Individual Employee Campaign projections on the Campaign Information screen

Users can no longer add individual employee or individual special event data in the following Campaign Information fields: Projection Low/Medium/High, Reported$, Projected$, Status, Card Value, and Goal on Monitoring and Participation pages. (6353)

Campaign Information: Error on Designation Detail page when there are too many rows

Error: OLE IDispatch exception code 0 from MSFlexGrid: Unable to allocate memory for FlexGrid occurred when accessing this tab for large volumes of designations. This problem has been resolved by giving users a warning that only first 21800 rows will be loaded in the grid. (6376)

Designations Out view - crashes with error Tot_Corp does not accept NULL values

This problem has been resolved. (6341)

Campaign Info / Node Dollars Export to Excel -- improve defaulting of file path

Two problems were identified with this process:

• The path for export file defaulted to the parent folder (if any) of the last used folder, and not the actual folder the user used.

• The first time a user did a Campaign Info Export to Excel, there was no 'saved path from the last time', so the path defaulted to blank, and the file would be saved in the Rainbow Home folder unless the user directed it elsewhere.

The program has been changed to explicitly redirect the output to the user's default output path (as defined in File-->User Options) whenever it is blank or pointing to the Rainbow home folder. (6410)

Sage Fundraising 100 – Rainbow Edition v.7.0 Release Notes 10 April 2008

Page 14: SAGE FUNDRAISING Sage Fundraising 100 – Rainbow Editionfundraising_100rb.mip.com/FR100-RB-RelNotes-v7.pdf · 2013-05-09 · Overview Overview The following is a list of new features,

Resolved Issues

Constituent/Profile Information Addresses view - phone numbers overlapping email addresses

A constituent's email address overlapped phone numbers when there were more than four numbers assigned to an address. This problem has been resolved. (6178)

Problem with users who did not have security having access to address information

Users who could access the Edit Constituent window, but did not have security access to edit or delete address information, still had the ability to access the ‘Get Spouse Info’ and the ‘Update Spouse on Save’ check boxes. If they used either of these fields, they were updating address information, which they should not have been able to do. This issue has been resolved. (6209)

Audit Logging bug in Address Services Import on VFP

Address Services Import on VFP triggered an obscure Audit Logging bug that increasingly degraded system performance, causing it to hang. This issue has been resolved. (6211)

Constituent view --> "Prefer" tab: two labels for "Types of mail to send" versus "Types of mail to send" and "Phone contact allowed"

The phone contact area was incorrectly labeled “Types of Mail to Send”. This problem has been resolved. (6228)

Name List: List of possible duplicates view - sort issue

Users without rights to view secured constituents, the list of names in the Possible Duplicates list is re-selected to exclude secured constituents. The re-selected list is not sorted in alphabetical order. This problem has been resolved. (6254)

Enhance Mass Add Involvement for a group of Corporate Constituents to an Agency

In previous versions you could add involvements to corporate constituent records but could not mass add them to corporate records. The Mass Add of involvements now allows corporate constituents to be updated. (6265)

Quick entry (QE): unable to save the spouse name information

Spouse name information was not saved in the following situation: Add Constituent A. Then add Spouse and select the Give Jointly flag. The Give Jointly flag is selected on Constituent A’s record but the spouse name is there. This problem has been resolved. (6269)

Mailing Process: incorrect sorting by Postal Code

The Mailing Process ‘Sort by Postal Code’ was based on RECNAME + address type (regular/seasonal) instead of sorting by RECNAME only. This issue has been resolved. (6277)

Error 230 "Array dimensions are invalid." when clicking the "Edit" Icon while on the Detail Tab of an Extra view

This was a sporadic problem. A fix to the Edit Note process should resolve this on the rare occasions that it occurs. (6278)

Constituent Navigator list now shows all 10 constituents in the History buffer

This list previously showed only 7 names, forcing the user to scroll to view the remaining 3. (6307)

Cannot see the characters on entering values in Navigator search & cannot view lower part of Adhoc layout.

With a screen resolution of 800x600, users could not see the characters they were typing into the Navigator until they tabbed to the next field. This problem occurred in both the individual and organization search. Users were also unable to scroll down to bottom of the adhoc layout with 800x600 screen resolution. This problem has been resolved. (6308)

Worker & Assignment View - convert to grid, add filter option, add ability to add extras

The Worker & Assignment view was converted to display information in a grid format. As well, there are new filter options based on date range, campaign/year, worker/assignment type. Extras can now be added and viewed for both workers and assignments. (6356)

Sage Fundraising 100 – Rainbow Edition v.7.0 Release Notes 11 April 2008

Page 15: SAGE FUNDRAISING Sage Fundraising 100 – Rainbow Editionfundraising_100rb.mip.com/FR100-RB-RelNotes-v7.pdf · 2013-05-09 · Overview Overview The following is a list of new features,

Resolved Issues

Constituent View Performance Improvement

There were some data retrievals in the Constituent View that were being performed multiple times which could slow down the updating of this view. Changes have been made to improve performance. (6368)

Status Centre: Event Attendance View icon also opens Membership View

When a user opened the Event Attendance view from the Status Centre the Membership view also opened on top of the Event Attendance view window. This problem has been resolved. (6375)

Cannot add attribute with unique code if constituent has any other attribute

An attribute code with the Unique flag (set in the code’s Properties in the Lookup Table Manager) could not be added to a constituent if they had any other attribute, unique or not. This problem has been resolved. (6395)

Contact constituent on new corporate record does not have the Household ID field set

I modified the saving of a contact on a new corporate constituent so that the Head of Household field and Household ID field are set on the name table. (6438)

Note & Attribute Type lookup table - enable Usage types at all levels of code

In version 6, functionality was changed to disallow usage defaults on the second and third levels of the Note Type and Attribute Type codes in the Lookup Table Manager. In version 7, this functionality was changed to allow users to set the usage fields on the second and third levels if the level above allows all usages. That way, users can set the first-level code to be all usages and then restrict the second-level could based on where it was being used. (6456)

Designations/Funds Cosmetic problem under Fee Manager

On the Designation Payout - All Designations page, you can right click an existing designation and choose Properties, and then change the amount of the designation that is being paid out. When you click OK, the fee will be recalculated, but the grid was not being refreshed. Now, if the fee amount is different, the grid is refreshed with the new fee amount. (5536)

Balancing issues with Designation Payouts

Occasional balancing problems with designation payouts have been encountered, where the summary figures did not balance to the detail figures. This could cause the error: ” PO_AMOUNT does not match with the sum of DX_AMOUNT for the payout nnnn.” Investigation showed that all detail and summary tables are being updated correctly. This error is very rare and hard to duplicate because payout data is updated in many places in the system. To ensure that a particular payout is balanced, some changes were made to the Designation Payout Manager:

• You can now only close the Detail window on the Designation Payout Manager with the Close button.

• When you close the Detail window, the system verifies that all summary and detail figures are balanced. If they are not, the system corrects the balancing issues immediately.

• Note that when the payout is finalized, the system performs the same balancing procedure as when the Detail window on the Designation Payout Manager is closed. However, it will only report any balancing errors that are encountered. If an error is reported, you can go back into the Detail window and then close it again to rebalance it. This is not likely to happen because the balancing problems occur rarely.

• While the system is correcting any balancing issues, to ensure all changes are implemented correctly, the constituent and designation records will be locked. If the balancing fix cannot be completed because the record is locked, it will be reported to you and will identify that the payout is still out of balance. (6188)

Sage Fundraising 100 – Rainbow Edition v.7.0 Release Notes 12 April 2008

Page 16: SAGE FUNDRAISING Sage Fundraising 100 – Rainbow Editionfundraising_100rb.mip.com/FR100-RB-RelNotes-v7.pdf · 2013-05-09 · Overview Overview The following is a list of new features,

Resolved Issues

Designation Payout - problem with calculation of fee amount to be returned

Various issues with the calculation of return fees were fixed:

1. In the Fee Manager, set up a Cumulative (Designation paid) fee for an agency that contained a percentage, minimum and maximum to charge. Pledge and payment were entered for an agency that used this fee method. Ran designation payout and it calculated the fee amount correctly. Finalized payout. Edited pledge and changed designation to another agency. Ran payout again using the original agency. Instead of returning the full fee amount, it returned only a portion –it was taking the return amount and adding the minimum fee amount to it. For example, original fee charged was $10, minimum fee amount was $3. On the second payout, the fee amount returned was -7.00, calculated by taking -10 + 3. This was incorrect. The program has been changed and the full fee amount is now refunded.

2. On the Fee Manager, set up a Cumulative (Designation paid) fee for an agency that contains NO percentages, with a minimum and maximum to charge. If you followed the same steps as in 1, no fee amount was returned in the second payout. This is has been corrected.

3. If running fees using Non Cumulative by Designation Paid with no percentages entered, the fee was calculated correctly. However, if the receivable was included in a finalized payout, and the designation was then changed, the fee was not calculated at all on the reversing amount. For example, a fee of $3 was charged on the original payout for the designation. When the designation was changed, the fee on the new payout should have been negative $3, but it calculated $0. This problem has been resolved.

4. After a payout was finalized, the grid was refreshed, but the buttons on the manager window were not, making it look like you could run the Finalize again on the payout that you just finalized. The window now refreshes correctly. (6298)

Fee Manager - the grid is not refreshed after a fee item is deleted until the list is clicked

On the Fee Manager, if a user deleted a fee, the grid was not refreshed until the user clicked on it, making it look like the record was never deleted. The grid now refreshes properly after a fee is deleted. (6324)

Designations Out view - crashes with error Tot_Corp does not accept NULL values

After opening the Designations Out view for an individual constituent, the following error could occur: Tot_Corp does not accept NULL values. This problem has been resolved. (6341)

Designation Payout - when recalculating a payout, including fees, the fee amount gets reset incorrectly in certain circumstances

This problem occurs under the following circumstances:

1. two or more payouts are open for the same agency and they have not been finalized

2. the fee calculation method is set to Cumulative (Desig. Paid) or Cumulative (Total Desig.)

3. when the details are added to the second payout, the fee is calculating correctly

4. if you recalculate the second payout, the fees are set to an incorrect value

The fee amount is now being correctly recalculated. (6453)

Fund Search window - general ease of use issues

The following changes have made the Fund Search window easier to use:

1. When the window first opens up, the cursor is on the by Agency page frame. Now, when the Agency page is active, the cursor is in the Agency field, so users can start typing immediately.

2. When users entered a description in the Fund field on the Fund Designation window (any receivable window, Fund Designations grid, right-click Add), the Fund Search window opened with a list of the funds that matched the description. In this case, the By Fund Code or Description tab was active. When it opened up the first line was highlighted, but the Select button was not active. This window has been changed to make the grid active so users can just click the Select button to select the first fund.

3. On the same page as item 2 (By Fund Code or Description), the user can now double-click any fund listed in the grid. Previously, they had to click the grid to highlight the applicable item and then click Select. (6473)

Sage Fundraising 100 – Rainbow Edition v.7.0 Release Notes 13 April 2008

Page 17: SAGE FUNDRAISING Sage Fundraising 100 – Rainbow Editionfundraising_100rb.mip.com/FR100-RB-RelNotes-v7.pdf · 2013-05-09 · Overview Overview The following is a list of new features,

Resolved Issues

Designation Payout - running void payout locks all records in payout before processing

When a void payout was run, the process locked all constituents and designations included in the run. Then, it processed the records, and then unlocked them. For large payouts this could result in the process hanging up or result in messages indicating that the lock table was missing. The program was modified as follows:

1. Donors are no longer locked en masse at the beginning of the process. There locks at the end were also removed.

2. Each individual donor/designation record is locked as it is being processed. If the item is locked, the user has the option of cancelling or skipping the record.

3. Before, when a single agency was voided (from the Details window) from a payout, the Void Date, User ID and Void flag were updated. Now, the Void Date and User ID are automatically updated on both the agency payout record (PayoutAG) and the Payout record. If no designations were skipped due to a locking problem, the agency payout record (PayoutAG) is flagged as Voided. If one or more were skipped, then the flag is left as Not Voided, so the user can re-run the void process again later. Note that the void procedure will only select designations that have not been previously voided. If the user voids each agency on the payout individually, when the last agency is voided, the Void flag on the payout record is also updated to Yes.

4. The Void Payout procedure (from the Manager window) was modified so that it does not update the Void fields on the payout, since it is now updated when each agency is voided individually. (6492)

Endowments and Grants Grant Proposal view - clicking on a page multiple times for the same record should not reload the object

In the Grant Proposal view, the grant proposal object was being recreated each time a user clicked on a page, although it only needed to be created when the user clicked on the page the first time for a specific grant proposal. It is now only updated when necessary, which improves speed performance. (6183)

Grant Disbursement Letters - manually entered incomplete check run numbers were accepted

The check run selection in the grant disbursement letters only allows users to select completed check runs. However, users could still type in a check run number that is not completed and it would run. This issue has been resolved. (6139)

Constituent Key Search ability added

The ability to search the Grants Management system by Check Request # and Check Number has been added. (6180)

Grant Proposals/Allocation Step - the transaction ‘Accounting Date’ was not updated when DES was not required

When DES sessions were not required for Grants Management and you created an allocation step and changed the accounting date, the allocation step recorded the correct accounting date, but the corresponding allocation transaction did not. This issue has been resolved. (6233)

Grant Proposals/Adjusting Allocation steps - open D/E Session should disable accounting date field

When adjusting allocation steps in Grant Proposals with a DES open, the accounting date field was enabled and the user was able to change it to any date they wanted. This issue has been resolved. The field is now disabled and is set to the accounting date from the DES. (6238)

Grants Management GL Interface - problem with printing Grants Management mapping report

An error occurred in the Grants Management GL Interface when a user attempted to print out a report of the Grant Management Mappings, Account Types. This issue has been resolved. (6242)

Grant Proposals/Decision approval step - right-click ‘What’s This?’ shows incorrect information

On both the Add/Edit Decision Approval Step window from the Grant Proposal Manager and the View Decision Approval Step window from the Grant Proposal Manager, the ‘Owner’ field is not pointing to the proper data dictionary field and the ‘What’s This?’ shows an incorrect file and field name. This issue has been resolved. (6258)

Grants management/Document Out Letters – unnecessary processing of documents

After executing the live run Document Out processing, the documents selected and processed were still being selected in subsequent runs of the process. This problem has been resolved. (6281)

Sage Fundraising 100 – Rainbow Edition v.7.0 Release Notes 14 April 2008

Page 18: SAGE FUNDRAISING Sage Fundraising 100 – Rainbow Editionfundraising_100rb.mip.com/FR100-RB-RelNotes-v7.pdf · 2013-05-09 · Overview Overview The following is a list of new features,

Resolved Issues

Add/Edit Grant Proposals - Fill Disbursement Schedule crashes if Check Type of None is selected

Error Number 107, Message: Operator/operand type mismatch could occur if a user selected a Check Type of None after using a fill option for disbursements. This problem has been resolved. (6285)

Editing Endowment grant disbursement on a new grant proposal with a sponsor disbursement name causes a crash

Error 1925, ENDOWGRNTDISBFORM.PF.TRPG.DISBNAMEBOX.SETDESC occurred under the following circumstances: Manually enter an endowment grant disbursement, entering all the required endowment information. On the Disb. Letter page, select the Send Disb Letter check box and enter one new sponsor disbursement name. Click OK to save the endowment grant disbursement. Before saving the new grant proposal, right-click and edit the new endowment grant disbursement. The system produces error. This problem has been resolved. (6288)

New Grant Disbursement Manager

This manager is available on the Managers|Grants Management menu. It enables you to view selected grant disbursements for one or all grantees. It also includes Mass Update options for changing the Scheduled Payment Date and mass approving disbursements. (6295)

Grant Proposals - warning message should be displayed when a grantee/payee that is inactive is used

Previously, a grantee or payee that was inactive could be used on grant proposals. This may be necessary, so the system does not prevent this, but now displays a warning message indicating that the record is inactive. (6300)

Grant Proposal Manager/View - grant disbursement grid could incorrectly show endowment information

This problem would only occur when the grid was showing endowment grant disbursements first and then regular grant disbursements afterwards in the grid. The last endowment that was displayed in the grid would then be copied into the regular grant disbursements. This problem has been resolved. (6302)

Endowment DES Report crash when GL Account Summary selected

Error 107, Operator/operand type mismatch could occur when printing the DES GL Account Summary report when there are no transactions in the DES. The report has been modified to show that there are no transactions. (6304)

Grant Proposal allocation steps - allocation transaction amounts do not balance to total allocation amount

The sum of the allocation transactions should always balance to the allocation amount on grant proposals. Under certain circumstances, these amounts could be out of balance. This occurred when an allocation was adjusted, then edited (with a non-financial field being changed). This problem has been resolved. (6306)

Grants Management GL Interface - unable to map allocation adjustments using Special Category of None

In the Grants Management GL Interface, you can map Allocation Adjustments by Special Category. If you select a mapping type with a special category and then select a special category of None and click OK, the system gives you a warning message that the special category cannot be blank. However, blank should be a valid option, since it represents None. This problem has been resolved. (6320)

Grants Management GL Export - summary reports are incorrectly showing grant proposal information

The Grants Management GL export summary reports are including the following information: Grant Proposal Key, Grant Proposal Number and Year. This information is misleading and incorrect, since the summary reports summarize based on the GL account and either Accounting Date or Data Entry Session. The Grants Management GL export utility has been modified so that the summary reports do not include any Grant Proposal information on them, since the summary report would have multiple grant proposals summarized on one line. (6366)

Endowment Mass Refund Disbursements error

Error 12, variable 'LERRORCNT' is not found could occur when an endowment disbursement was selected for the Mass Refund utility based on asset pool and the endowment did not have a refund asset pool identified for it. This problem has been resolved. (6379)

Grants Management GL Export - MIP export file incorrectly contains separators in the GL account

If using MIP GL export process for Grants Management and separators have been set up in the GL account format, when running the Grants Management GL export utility, the separators are incorrectly being included in the GL account information. This causes some of the GL account to be truncated. The system now uses the unformatted account number (which does not include separators) for the export. (6387)

Sage Fundraising 100 – Rainbow Edition v.7.0 Release Notes 15 April 2008

Page 19: SAGE FUNDRAISING Sage Fundraising 100 – Rainbow Editionfundraising_100rb.mip.com/FR100-RB-RelNotes-v7.pdf · 2013-05-09 · Overview Overview The following is a list of new features,

Resolved Issues

Endowment Manager - override administration fee fields display incorrectly if a previous endowment in grid has these fields activated

In the Endowment Manager grid, the override administration fee fields (Override Fixed Fee, Override %, Override Min Fee, Override Max Fee) sometimes displayed incorrect values. This occurred when a previous endowment in the grid had the override admin fields activated and a later endowment did not. It maintained the override administration fields from the previous endowment and used it for the next endowment in the list. This problem has been resolved. (6396)

Multiple problems with Grant Approval Step adhoc sources

In any criteria window using the source of 'Approval Steps - Comment', any selection criteria specified resulted in no items selected. This problem has been resolved.

When creating an adhoc report using Approval Steps - Comment, there are two fields listed that say Comments. One is from the related field on the GRNTSTEP file and the other seems to be pulling from the NOTE table. The NOTE table one was eliminated, since the comment is not stored there for comment approval steps.

There are a number of new fields that were introduced for allocation steps in the GRNTSTEP file. However, these fields appear in adhoc criteria for all types of steps. They should only be available for allocation step sources. This problem has been resolved. (6452)

Search returning non-agency and/or non-grantee results in an agency or grantee-only search

The Search option in Grants Management had been modified to only show constituents who were grantees (when searching for grantees) or payees (when searching for payees). When the 'Active Constituents Only' check box is cleared the searches within Grants now bring back all constituents, disregarding the grantee or payee constituent check boxes. This problem has been resolved. (6462)

Printing Disbursement Cheques – problems with locking

Errors could occur during the cheque printing process when the system encountered a grant proposal or endowment was locked during processing. These errors have been resolved. Note that for endowment disbursements, as part of these fixes, the system now locks the endowment at the beginning of the cheque printing process giving the user an option to get the other user out of the endowment and retry or skip the cheque request. (6486)

Events If there were more than 2 fee codes in an event, users would receive an error message when attempting to edit the registration. This problem has been resolved. (6313)

Endowment Period End Import – error occurs when an endowment is locked by another user

Error 1925, Unknown member ENDOWOBJ would occur when the Endowment Period End Import utility encountered a locked endowment during processing of a trial run. This error has been resolved. The system now reports a locked endowment to the user, allowing the user to click OK to bypass the locked endowment and continue processing. The locked endowment is recorded in the utility’s error report. (6340)

Void process for endowments not verifying date correctly

When voiding a cheque for an endowment disbursement, the accounting date that is used for the void process is not being checked to make sure it is after the lock date for the affiliated endowment. The system is verifying that the accounting date falls within the Endowment or Grants Management valid accounting date range, but it also must check that it is after the lock date on the endowment. This problem has been resolved. (6372)

Financial Data Funds view/ Designation In tab/ Program column is not sorted alphabetically

Problem was caused by the fact that the maximum sort length was set to 25 characters. This meant that program names that had the same first 25 characters were not sorted, since sorting did not occur after those 25 characters. The maximum sort length has been increased to 50 characters. (6158)

Error when running the SPS installment process with MS Office Document Image writer set as the default printer

Error 1958, Error Loading Printer Driver occurred when users cancelled an MDI document from the prompt generated by the SPS Installation process. This problem has been resolved. (6201)

Sage Fundraising 100 – Rainbow Edition v.7.0 Release Notes 16 April 2008

Page 20: SAGE FUNDRAISING Sage Fundraising 100 – Rainbow Editionfundraising_100rb.mip.com/FR100-RB-RelNotes-v7.pdf · 2013-05-09 · Overview Overview The following is a list of new features,

Resolved Issues

Edits to Transaction History DES or Accounting date were not being Audit logged

The edits to Transaction History DES or Accounting date were not being Audit logged. This issue has been resolved. Note, only users with specific rights can change the DES or Accounting date on transaction history entries, and only if the history entry has not been exported to GL and is not in a Locked Batch. (6222)

System allows NSF payment application

The apply payment window allowed NSF payments to be selected. This issue has been resolved and it is no longer possible to select a payment to apply that has been NSF'd. (6239)

Alerts in Quick Entry( QE) have incorrect constituent name

Selecting a constituent that has an alert in Quick Entry while another constituent with an alert was displayed in the system Navigator led to the correct alert being displayed, with the incorrect name. This problem has been resolved. (6263)

Inconsistent toolbar behavior when adding Attributes

When adding extras on a receivable, the toolbar buttons (i.e. add, edit buttons) remained disabled during and after adding notes, attachments, and links until the receivable was closed and saved, but this did not happen when adding attributes to a receivable. The toolbar buttons no longer remain enabled during the process of adding attributes on a receivable. (6267)

Pledge reminders merge data file: pledge DUEDATE is showing the date of the pledge (PL_DATE) and not the schedule date due.

This problem has been resolved. The Scheduled Payment Date is now entered into the Due Date field when installments are present. (6271)

MIP Export files - text fields cannot contain characters " or |

The import of information failed in MIP Fund Accounting if the description field in the Sage Fundraising 100 export file contained either " or |. These characters will now be eliminated from the campaign, endowment and grants GL exports. (6272)

Alert duplication in Quick Entry (QE)

In Quick Entry of envelopes alerts would appear multiple times, forcing users to click or use ALT+C to close the alert window. The alert is now only displayed for a workplace when the envelope is selected or when the workplace ID is added to a new envelope. Note that if a user attempts to Delete an envelope and it is not successful because details have been added to it, the alert does display again because the envelope is actually cleared and then reloaded again. (6262)

Disabled Routing and Address buttons in Gift view

The Routing and Address buttons in the Gift view were disabled. They are now available for use. (6266)

Deposit Manager: Add Extras

Extras functionality (notes, attributes etc.) has been added to the Deposit Manager. (6357)

Data Entry Session Manager - add search option

The Data Entry Session manager was modified to add a Find button beside the filter button at the top right of the window and on the right-click menu of the grid. The Find window allows the user to type in text to search for in the Description field of the Data Entry Session. (6360)

Deleting the gift portion of a gift – not the payment – shows a negative balance in the Constituent view

This problem occurred for constituents who had no prior campaign participation and then had a gift added. When the gift portion was deleted but the gift payment was not deleted, a negative balance would appear on the Giving tab of the Constituent view. This problem has been resolved. (6373)

Envelope View: Up and Down arrows to move between envelopes is tied directly to the envelope number and should be independent of this field

For example, if a user sorted on a field other than Envelope Number and then used the up and down arrow keys, the down arrow was disabled on the largest envelope number and the up arrow was disabled on the smallest envelope number, wherever they happed to be positioned in the envelope list. This problem has been resolved. (6429)

Sage Fundraising 100 – Rainbow Edition v.7.0 Release Notes 17 April 2008

Page 21: SAGE FUNDRAISING Sage Fundraising 100 – Rainbow Editionfundraising_100rb.mip.com/FR100-RB-RelNotes-v7.pdf · 2013-05-09 · Overview Overview The following is a list of new features,

Resolved Issues

Envelopes: Error 45 occurs when attempting to run Envelope Detail reports

When a user attempted to run the report without selecting either the “Memo Designations versus Detail Designation or the List of Required Detailing Receivables” reports, error 45 “not a character expression” could occur. This problem has been resolved. (6457)

Message "Unbalance GL Transaction" while editing Pledge with NSF payment application

The problem resulted from the fact that NSF payment applications were were not processed first in processing the adjustment. The program has been changed to process any NSF applications first. (6475)

Gift view: NSF a Gift and it display's the same gift twice

A gift that was deposited, confirmed, and then flagged as NSF would appear twice in the Gift view. This problem has been resolved. (6482)

Forms Improved sorting of tax receipts, and four new output fields

Previously, payments within a given receipt were sorted by payment key. Under normal circumstances, for a given constituent, this would correspond to the payment date order. But for sites using multiple data entry streams (e.g. lock box imports), the payment key order did not necessarily correspond to the payment date order for a constituent. To avoid this potential sort problem, the receipting process now explicitly sorts payments within a receipt by “date + key” rather than just by “key”.

The following new fields have been added to standard receipting output to allow a site to easily use MS Word Merge files to include a list of payments on the receipt rather than a list of payment-applies:

• INPYMTCNT – number of payments represented on this receipt

• INPYMTSEQ – record sequence number within this payment

• RPYAMOUNT – receiptable amount of this payment

• NRPYAMOUNT – non-receiptable amount of this payment. (6359)

Tax Receipting/Tax Substantiation Letters- the receipting program will reject payments that do not have same Employee Reference Number (EMPREFNO)

JobTitle, EmpRefNo, and JobDept are unique per payment, but the validation in the receipting program required them to be unique per receipt. The validation program was changed to allow different EMPREFNO on a receipt. (6390)

New definition loaded despite cancelling out of Definition Manager

In any form using the new definition controls, if a user opened the Definition Manager, selected a different definition than the current one and clicked cancel, the selected definition would be loaded even though the select button wasn't used. This problem has been resolved. (6426)

Error when reminders are run using a group that selects 0 constituents

Error 107, Message: Operator/operand type mismatch could occur when running reminders for a group with zero constituents. This problem has been resolved. (6427)

Reminders only for constituents who do not want reminders mailed If reminders are processed for one or a selection of constituents who meet the reminder criteria, but have "mail reminder?" set to "no" this process would create a completely blank summary report (no title or headings) then fail to print reminders with a message "Reminder process failed" followed by a message "0 reminders processed".

The reminder program was modified so that the reports, mailing record update and the generation of the merge file only occurs if there is something in the actual Reminder work area. If selections have included constituents that have been flagged to not receive reminders, these records will not get inserted into the Reminder work area. (6428)

Sage Fundraising 100 – Rainbow Edition v.7.0 Release Notes 18 April 2008

Page 22: SAGE FUNDRAISING Sage Fundraising 100 – Rainbow Editionfundraising_100rb.mip.com/FR100-RB-RelNotes-v7.pdf · 2013-05-09 · Overview Overview The following is a list of new features,

Resolved Issues

Import Import: Lookup table controlled fields could import invalid blank code

When importing data, and a field controlled by a lookup table is present in the import definition, the record will be added with that field left blank regardless whether or not blank is a valid lookup code. This is problematic if there is no blank code in that lookup table. This problem has been resolved. (5744)

Import allows illegal value in EM_PRIMARY field

Users were allowed to import “N” for non-primary. This could later cause an error when editing the constituent’s employment record. The import now only allows valid values ('Y' or ' ' blank) to be imported into the EM_Primary field. (6309)

Import problem when importing multiple notes Designed behaviour when importing multiple notes was problematic for some users. The issue occurred in the following circumstances:

Create an import with an attribute of your choice (even a defaulted one).

The Note->Note field was neither mapped in the import definition nor defaulted.

Create another instance of a note or attribute, but this time map it to an import field for Note->Note.

When you import, both notes/attributes inherit the note text, even though there is no note text mapped to one of them.

This problem has been resolved by allowing users to map the blank occurrence of the field NOTE (and other fields of MEMO type) as field #0 in the import definition, with a default value of <BLANK> or <SPACE>. In previous versions, only CHARACTER fields had that option. (6322)

Import: preprocessing utility Custom Constituent Match (UWAC) crashes

Error 1734, Property DECYPT is not found could occur when running the Custom Constituent Match utility during import. This problem has been resolved. (6349)

Import problems: missing record(s) in Import Load, Duplicate Primary Employment records after importing receivables

Invalid Fund key assignment FU_KEY = “NO KEY” error. When the file is being loaded none of the fund keys are found even though all of the fund codes are valid. If the same file is unloaded and reloaded the problem resolves itself. This problem has been resolved. (6374)

Import: Crash when importing a gift with a new EDI account

SPS procedures allowed users to add a gift only with an existing EDI account. But when Import attempted to add a gift with a new credit card account, the following error occurred: Error 2028: API call caused an exception. Also if the constituent imported this way was a new constituent, then Account Name field contained the constituent ID instead of full name. Both problems have been resolved. (6397)

Import problems: missing record(s) in Import Load

Two problems were identified:

• Missing records in Import Load even though it said “complete” e.g. 2 lines from the CSV file were missed. In some cases the problems could be resolved by unloading and reloading the data, but without knowing files were missing, most users wouldn’t know to do that.

• Missing records in Mass Apply Payroll payment import.

Both problems were resolved. (6413)

Import of employment records is always setting the Current Flag to Yes, even if the field is set to blank in the import file

When the import definition contained both the Primary flag and Current flag the current flag was always set to Yes, even if the field was included in the import file and the data was blank. If the Current flag is blank, the program now imports the employment record as non-current. (6420)

Sage Fundraising 100 – Rainbow Edition v.7.0 Release Notes 19 April 2008

Page 23: SAGE FUNDRAISING Sage Fundraising 100 – Rainbow Editionfundraising_100rb.mip.com/FR100-RB-RelNotes-v7.pdf · 2013-05-09 · Overview Overview The following is a list of new features,

Resolved Issues

Problems with Import duplicate check tool

If a user ran the standard import duplicate check titled "Constituent Duplicate Check (System)" that is part of the system, the system did not restore the window size to its last use. The program has been modified to save and restore the window size based on the last use. (6471)

Job Queue Job Queue: Jobs submitted to the ‘ANY’ queue could be processed on queues to which the submitter did not have rights

If a user submitted a job to the ‘ANY’ queue, it was supposed to be processed by the first available queue to which the user had rights. However, it would be processed by the first available queue, regardless of whether or not the user had rights to submit jobs to that queue. This issue has been resolved (6407)

Miscellaneous Definition Manager: Deletes a definition without confirmation from the user

In all processes that use the new definition manager (mailing process, all forms, etc.) when a definition is selected to be deleted and the delete button is clicked, the definition is deleted immediately without verifying that you wanted to delete the definition.

Also, if you deleted the currently used definition, then clicked Cancel on the definition manager, the system warned you that you must select a definition since the current one has been deleted. If you then clicked the Select button, assuming that it would select the currently highlighted item (if there is one in the list), it warned you that no definitions exist and that you must create one. If you then clicked on the grid, and then clicked Select, it worked correctly. These issues have been resolved. (6063)

What's This window sometimes would appear behind the active form

In certain circumstances, the right-click “What's This” option would result in the What's This window appearing behind the active window. This problem has been resolved. (6130)

Redirect URL for some menu options

The Help menu had multiple “Support” options pointing to the same Web address. Duplicates have been removed. (6286)

View/Edit Notes missing refresh function

On certain monitors, the View and Edit Notes windows were not refreshing after being resized. This issue has been resolved. (6143)

A window’s right-click menu may appear in a grid instead of the grid's right-click menu

This occurred occasionally after right-clicking several times without making a selection. This problem has been resolved. (6214)

Incorrect highlighting in grids with pictures

Manager windows were not highlighting the image column if there was nothing being displayed in it. This issue has been resolved. (6215)

Counter limit for "Automatic logout of idle sessions after" # of minutes

Due to some reported questions on the upper limit in this field, the maximum value was changed to 999. (6225)

The "UNIQUE" flag on attribute code table was not working

Duplicate 'unique' attribute codes could be added and it was also possible to import duplicate unique attribute codes for one constituent. These issues have been resolved. (6255)

Outlook Integration: Error when reminder date set after start date

The error that occurred when the reminder date was set after the start date has been resolved. (6284)

Sage Fundraising 100 – Rainbow Edition v.7.0 Release Notes 20 April 2008

Page 24: SAGE FUNDRAISING Sage Fundraising 100 – Rainbow Editionfundraising_100rb.mip.com/FR100-RB-RelNotes-v7.pdf · 2013-05-09 · Overview Overview The following is a list of new features,

Resolved Issues

Fields using a lookup table - resize the drop-down list of information so that the full description can be seen

Fields using a lookup table code could sometimes have the description truncated because the field was not wide enough to display the full value. The program has been modified to calculate the width of the longest description being displayed and then set the description to this width so the whole description can be seen. Note that there is a minimum width of 100 pixels and a maximum width of 66% of the available work surface in Sage Fundraising 100 – Rainbow Edition. (6393)

Allow for system cross reference paths to be greater than 50 characters

If any of the paths in the system cross reference setup were greater than 50 characters the live system flag would not be correctly set. The path names can now be greater than 50 characters. (6403)

Grid export to Excel will crash with an error if invalid characters are used in the file name

When choosing the right-click Grid Options / Export Grid Data option from any grid and the user included square brackets in the file name, the following error occurred: Number: 1429, OLE IDispatch exception code 0 from Microsoft Office Excel: The file could not be accessed. The error also suggested the removal of invalid characters, including the square bracket and ensuring the path and filename did not exceed 218 characters.

This problem has been resolved - the program now checks to make sure that invalid characters are not included and that the path name is no longer than 218 characters. (6412)

Custom font size in Windows crashes RB

Changing the font size in the appearance of a Windows desktop caused error 1881, Error with WORKERGRID - Height : Expression evaluated to an illegal value. This problem has been resolved. (6425)

Acknowledgement Flag - "What's This?" description needs to be updated for all receivable types to show the correct options for this field

The description states that the flag options are "None, Pending or Done", when the actual options are, "Yes, No and Done". It has been corrected for all receivable types.i.e. Pledge, Gift, Membership and Events. (6451)

Local copy of help file wouldn't refresh in some circumstances

This problem has been resolved. (6454)

Outlook integration setup not in setup menu if site doesn't have the membership module

The code to add the Outlook setup was mistakenly linked to the membership module. This problem has been resolved. (6256)

Saving an Edit with no changes still logs an Edit Record entry in Audit

In SQL Server systems, when a user clicked OK on an edit screen, but did not actually change anything, the system still recorded the edit. It appeared in the Audit Log as an EDIR record in the Audit table. This problem has been resolved. If there are no changes made to the record, the item is no longer recorded as an Edit in the Audit Log. (6315)

Outlook Integration: Recurring Outlook items causing crash when synchronizing

If the system identified the item in Outlook as a recurring item, the date/time info was not being passed back to Outlook during synchronization. Date/time changes made in Outlook are now being brought back to Sage Fundraising 100 – Rainbow Edition during synchronization. (6394)

Sponsor sheets deleted when merging constituents

The Merge Constituent process deleted sponsor sheets from the source constituent without comment in the merge note. The process has been changed to move any sponsor sheet and sponsor sheet series information from the inactive ID to the active one. (6460)

Improve SQL Server performance by adding indexes to large temp tables before linking back into system data tables

Temporary tables (used for linking data) were causing performance issues in various areas of the system, including the Campaign Information view, some financial views, Mass Apply and Designations Payout. New indexing for the temporary tables has resolved this problem. (6465)

Sage Fundraising 100 – Rainbow Edition v.7.0 Release Notes 21 April 2008

Page 25: SAGE FUNDRAISING Sage Fundraising 100 – Rainbow Editionfundraising_100rb.mip.com/FR100-RB-RelNotes-v7.pdf · 2013-05-09 · Overview Overview The following is a list of new features,

Resolved Issues

RBAdmin ignores paths specified in fr100.ini and uses system default paths

The upgrade process made the assumption that all the directories were in the root of FR100 and ignored settings in the FR100.ini file. This problem has been resolved. (6472)

Projects & Tasks Various problems with copying and pasting tasks reported

Two users could cut and paste the same project at the same time. This was resolved by placing a lock on the project when the first user cuts it. The Extra tab was not refreshing properly when selecting a project – this problem was also resolved. (6411)

Projects & Tasks – problems with owner and public rights

The problems identified were:

1. Two users were working on the same constituent in Projects & Tasks and one of the users deleted a project. If the second user attempted to edit the project that was being displayed on the view, but had been deleted, the following error occurred: Error # 9 - Data Type Mismatch on line 1697 of TASKFORM.PF.NOTEPG.NGCONTAINER.LOADNOTES. This problem has been resolved.

2. Users could cut a project / step / task if they did not have edit/delete or admin rights for all of the items that were being cut. Users must now have edit/delete or admin rights to perform any of these functions.

3. On a project where there was a step with multiple tasks and one or more of the tasks had a different owner and a user did not have admin rights for projects/tasks but changed the owner at the step level, the system asked whether the ownership change should be replicated. If the user said yes, all tasks would be switched to the new owner, including the ones where the user did not have edit rights. It now only switches the owner on the tasks for which the user has rights to edit.

4. As in step 3, when a user switched the owner on a step and clicked OK, a message appeared asking whether the owner on all linked steps should be changed. The message was really referring to tasks and now says “linked tasks”.

5. If a user edited a step or task and then clicked Cancel, the treeview reset itself to the top element in the view. It now stays on the last record that was edited. (6422)

Error when mass adding a task in Project Models

Error "LTOOBJECT is not an object" could occur when mass adding a task in the Project Models window. This problem has been resolved. (6421)

Reports Assorted problems with Individual/ Employee Campaign (Payroll) report (R1_0006c)

The About information for this report needed to be improved and the report includes all payment methods, not just payroll, so the heading was inaccurate. The About information was rewritten and the name has been changed to reflect the fact that the report shows payroll and non-payroll donations. (3167)

Account Planning Guide report (R0_0070) shows value "Y" only for the last level of the attribute

For attribute codes with multiple levels, this report showed the value "Y" only for the last level of the attribute, while leaving the higher levels at “N”. Analysis showed that this report was breaking each multi-level attribute code into separate, individual attribute codes. This problem has been resolved. (5140)

Incorrect number of donors appear on Account Planning report (R0_0070) when there are individual employee pledges but no employee pledge on the corporate record

If there was no summary employee pledge on a corporate record but there were individual employee pledges linked to the corporate record, the donor count on this report would be blank. This problem has been resolved. (5152)

Report Run Error 1426 and Error 202 when running Corporate Designations Report (R1_0004) and exporting to Excel

These errors could occur when running a summarized data export. This problem has been resolved. (5256)

Sage Fundraising 100 – Rainbow Edition v.7.0 Release Notes 22 April 2008

Page 26: SAGE FUNDRAISING Sage Fundraising 100 – Rainbow Editionfundraising_100rb.mip.com/FR100-RB-RelNotes-v7.pdf · 2013-05-09 · Overview Overview The following is a list of new features,

Resolved Issues

Campaign Monitoring report (R0_0202): Error 1581

Error 1581, CM_CARDVAL does not accept null values and M_GOAL does not accept null values could occur when this report was run with the options Detail and Individual Constituents selected. This problem has been resolved. (5831)

Designation Payout report does not display "void" flag for voided details

There were multiple issues with the void flag. The following changes were made to resolve these problems:

• From Payout Manager, Print button: Designation Payout Report – The report layout was modified to include a column in the details to show whether the designation was voided from the payout. As well, if it was voided, an asterisk now prints beside the Amount and the Fee Amount fields. The subtotalling based on Campaign/Year and by ID no longer includes the voided amounts that are being shown. The grand totals never included voided amounts.

• From Payout Manager, Print button: both the Designation Payments Export reports (Summary and Detail) have been modified to exclude voided transactions.

• Reports\Financial\Donor Designation Payment Report - This report was modified so to exclude voided transactions. (6174)

Errors in Campaign Monitoring with Leaders (R0_0302.APP)

Error 1581 CM_CARDVAL does not accept null values, CM_GOAL does not accept null values, and CM_ECCGOAL does not accept null values could occur with this report. These problems have been resolved. (6212)

Donor Designation Payment report (R0_0046.APP) error 12 "Variable 'PO_CAMPDSC' is not found" if the payout selector has been sorted by Campaign/Year

When selecting Payout Options for this report, if you clicked the Payout key selector ('...' button) and sorted the Payout Selector view by Campaign/Year you would get error 12 "Variable 'PO_CAMPDSC' is not found. This problem has been resolved. (6253)

“Nothing to Report” when running Account Status by Worker report (R0_0066) with some groups

For groups where the Group Count was zero and the Group Last Updated date was empty, this report would result in a “Nothing to Report” message. The error was caused by incorrect processing of the group in the report. The group is now processed correctly. (6279)

Donor Churn Report (R0_0086, R1_0086 ): Report is not displaying Community Impact funds in correct column if the Fund type has a second level

If a fund used a Fund Type code that had a second level, then the report did not place this fund in the Community Impact column of the report. Fund types with a top level only appeared correctly. This problem has been resolved. (6291)

Individual / Employee Campaign Giving report crashes when an individual constituent is selected

In the Employee Campaign Giving report (R1_0006A), if a user specified a single constituent that is an individual, the following error occurred: Error # 1734, Property CVALIDMESS not found at line 3845. This problem has been resolved. (6470)

Task Progress by Coordinator / Task Progress By Constituent reports missing text

Both Task Progress reports (by Coordinator or by Constituent) were missing text beside the check box on the Export Options page to indicate that these are raw results. The report was modified to include the phrase “Raw Results” beside the Export Options check box. (6474)

Designation Payout - Designation Payments Export (Detail) Report - report groups by agency name rather than agency ID

On the Designation Payout Manager, the Report button enables users to print 3 reports. The Designation Payments Export (Detail) report grouped information by agency name and provided sub-totals. If there were agencies with the same name but different ID, the data was being grouped together. The report has been changed to group the data by agency ID. (6476)

Sage Fundraising 100 – Rainbow Edition v.7.0 Release Notes 23 April 2008

Page 27: SAGE FUNDRAISING Sage Fundraising 100 – Rainbow Editionfundraising_100rb.mip.com/FR100-RB-RelNotes-v7.pdf · 2013-05-09 · Overview Overview The following is a list of new features,

Resolved Issues

Solicitation Manager Constituents incorrectly included during solicitation

In certain circumstances, a constituent who should have been excluded from a solicitation run by an “exclude” select was being included in a subsequent select. The problem occurred when the Head of Household flag was set in any of the selects' criteria. For each select, a temporary table is created based on the criteria. The selects aren't necessarily processed in the order they appear in the structure, and if a select criteria was processed with the Head of Household flag active, all subsequent select criteria were processed with it on as well. The program has been changed: if the user has one criteria where the One Per Household flag is set to TRUE, the flag will not remain TRUE for the remainder of the selects. (6467)

Utilities Project models->Mass Add utility generates error "Out of SQL Cursor names" while adding project models to a large group

Error -101, GT: Out of SQL Cursor names could occur when adding project models to large groups. This problem has been resolved. (6275)

Sage Fundraising 100 – Rainbow Edition v.7.0 Release Notes 24 April 2008