Users can copy the ID numbers from the results of a Profile Search to the Clipboard. Users can choose, via a context menu accessed by the Copy to Clipboard hyperlink at the top of the Search Results Display page, to use a tab, a comma, or a return to delimit the list of ID numbers. This functionality is a system-wide option, set by the System Administrator on the System Options page. The ID number field must be included in the Search Results in order for this to function as intended. To insure that the list of id numbers does not include duplicates, users must sort the Search Results by the ID number field, in either ascending or descending order, before clicking the Copy to Clipboard hyperlink.

A new field, copy_to_clipboard, has been added to the sysinfo system table to store this system option.

See Search Millennium Database, Save Search Results to Clipboard,and System Options,Copy ID number's to the Clipboard.

The text length for the display of value-based lookup fields (also known as super-lookups) has been increased so that the entire value of the field can be shown.

Data Insert Forms can be accessed via Hot Keys. The keystroke [ i ] will access a blank Data Insert Form for the data table that you are currently viewing. The keystroke [ v ] will access the Active Default Insert Form for the data table that you are currently viewing.

If you are viewing the data using your user Defined Display, the Insert Form for the first table shown in your Defined Display will be the Insert Form accessed.

Before using the desired Hot Key, first verify that focus has been placed on the Data Display area.

The following corebio fields can be utilized in Profile Searches.

• corenum1
• corealtid2
• corealtid3
• corealtid4
• corealtid5

These fields will not be part of the standard (default) Millennium Profile Search form, but can be added via the Custom Display Designer.

The custom alternate id fields are new to the corebio data table as of this release.

See custom alternate id columns and Customizing the Millennium Search Database Form.

Advanced Search and Secondary Search Results Display (for examples: relation or jobs company id search, event guest or correspondence search) screens have been modified to so that they will use the same Search Results Display as is used by the Primary (also known as Profile) Search Results display. If the Primary Search Results display uses the Standard Search Results Display screen, then they both will also use the Standard Display. And, if the Primary Search Results display is defined (customized) via the Defined Search Results Display applet, then all Secondary Search Results Displays they both will use this Defined Search Results Display.

If a secondary search (for examples: relation or jobs company id search, event guest or correspondence search) uniquely identifies a constituent, the user must click the name hyperlink on the Search Results Display screen in order to confirm that this is the desired constituent. Prior to this release, if a secondary search uniquely identified a constituent, the system did not give the user the opportunity to confirm that the identified constituent was the desired constituent.

See Data Maintenance.

Firefox version 2.0.0.14 has been tested and authorized for use with Millennium. However, the Custom Display Designer, Hot Keys, the Write A Letter, Add Tasks to Outlook, and Event Seating features will not work with Firefox. In addition, Firefox will not open certain UNC paths correctly unless a Locallink extension is added on to the Firefox browser. This affects all Firefox users who want to open site specific in-house applications through the Tools World Custom Utilities page.

Firefox and Attachments: If the Locallink extension has been installed, please open your Attachments with a left-click of the mouse.

See Browser Settings

The following user options that were accessed via the Options item on the Windows menu bar are now accessed via the Profiles World Options Action Button:

Select the Display item to set:

Display Linked Data on Short Display

Select the Data Entry item to set:

Table Lookups (by code or by value)

Delete Confirmation

The Profiles World Options Action Button previously presented a Profiles Options form on which users set various User Options. This Action Button now accesses a list of menu items instead.

Select the Display item to set the following options:

Display ID on Title

Display Linked Data on Short Display (as noted above)

Display Journals and Voids

Display Matching Transactions on the Matching Company

Display Matching Credits on the Matching Company

Group Linked Transactions together in the Mini-Display

Select the Data Entry item to set the following Matching Gift and Outlook options:

Find Matching Gift Companies

Potential Match Options

Search Spouse Matching Companies

Outlook Calendar and Outlook Task Options

Select the Define Display item to customize your Data Display Definition.

See Explorer-Windows and User Options

All Tables: Insert via default-Inactive lookup codes available to select when creating new Defaults or inserting via defaults.

Oracle System Alerts are not being generated.

When the windows client connection times out and prompts the user to login, a browser login screen opens inside of the client screen.

Mac users utilizing OS X 10.5.2 and Safari 3.1 are unable to see the Data and Table fly over menus.

Linked Attributes display with the primary rows to which they are linked. Users can now choose to include all linked Attributes with a constituent's Attribute display as well as with the display of the primary rows to which they link. Browser users can access this new User Option from the Millennium Explorer. Expand the User Options menu item under Profiles, and select Display. Windows users can access this User Option via the main Windows menu bar item labeled Options. See User Options, Linked Attribute Display.

For data maintenance purposes, users should continue to access these linked Attributes through the display of the primary rows to which they link and not through the constituent's Attribute display.

Show/Hide Payments - Users have the option to hide the display of payments, pledge payments made by other constituents on-behalf of the pledge owner, and write-offs that link to pledges, sustainer pledges, expectancies and match pledges. If the display mode is set to Long or Short, they can be 'collapsed' and displayed as a single line of totals. These totals will be grouped into payments (payments include both pledge payments and bequests), credits (the on-behalf-of payments) and write-offs, and include the count and total dollar amount for each type of linked transaction. If the display mode is set to Mini, the option to hide payments, credits and write-offs will only function if the Group Linked Transactions together in Mini-Display user option is checked, and the single line of totals will not be shown. Linked payments, credits and write-offs will always be shown in Detailed Display regardless of the user's Show Payments/Hide Payments setting.

The single line of totals will not count nor include in the total dollar amounts those transactions that link to the pledge payment, such as honors, memorials and/or credits.

This User Option is set via a context menu pop-up from any constituent's Giving Data Display. If payments are currently showing, the context menu item will be labeled Hide Payments. If payments are currently collapsed, or hidden, the context menu item will be labeled Show Payments.

Default payment amount shown when posting a pledge payment.

If the pledge payment insert form is accessed via the pledge transaction's context menu Post Pledge Payment item, or via the Post Pledge Payment icon located directly beneath the common information for the pledge, the Total Amount due will default to what is due on the date that the pledge payment form is accessed. This default amount is calculated from the payment schedule and will include the amounts that are due for all allocations. And, if the pledge is joint, this default amount will include the amounts that are due for all allocations on the linked joint transaction as well.

If the pledge is a multiple allocation pledge, and the pledge payment form is accessed via the Post Pledge Payment icon located below the information for an allocation other than the first, the Total Amount due will default to the total balance that remains on that specific allocation only. And, if the pledge is joint, this default amount will include the total balance that remains on the specific allocation on the linked joint transaction as well.

Prior to this release, Millennium defaulted the total amount due to the balance that remained on the pledge, including all allocations, on the date that the pledge payment form was accessed.

When the amount of the payment applied to an allocation exceeds the total amount of the allocation, a warning message will display near the bottom of the Post Payment Applet. This warning will not appear unless the Post Payment Applet has been accessed to distribute the payment among one or more allocations.

When a credit card information is entered, the expiration month and expiration year is selected from items listed in drop-list boxes. The expiration month list box will list the values 01 through 12. The expiration year list box will list ten years, beginning with the current year. When a credit card row is updated, the expiration month and expiration year values will continue to be maintained via text boxes.

See the Tender Data Maintenance topic.

The Clipboard Setup User Option accesses an applet, called Clipboard Settings, which enables each user to customize the Address table's Copy to Clipboard function layout to suit his or her own needs. Up to twenty data fields from the Address, Employment, Internet Address, Name and/or Phone Number data tables can be added to the user's Copy to Clipboard layout definition via this applet.

• For Browser interface users, the Clipboard Setup User Option is accessed via the Millennium Explorer. Expand the Profiles item and locate the User Options item at the end of the list. Expand User Options and select Clipboard Setup.
• For users of the Windows interface, the Clipboard Setup User Option is accessed via the Options Profile Action Button shown in the horizontal bar just above the Millennium display area. Click this Action Button, and select the Clipboard Setup menu item. Note that the Profiles Millennium Navigation bar item must be activated before this Profiles Options Action button displays.

Copy to Clipboard 'Rules':

If the user includes any data fields from the Name table in his or her definition, Copy to Clipboard will ASCII order the constituent's name rows by name type and then select the first one; this will most likely be the preferred name.

If the user includes any data fields from the Employment table in his or her definition, Copy to Clipboard will select the Employment row that links to the selected Address; if there is no linked Employment row, then no Employment data fields will be copied out.

If the user includes data fields from the Phone table, Copy to Clipboard will select the Phone row that links to the selected Address; if there is no linked Phone row, then no Phone data fields will be copied out. If more than one Phone row links to the selected Address, then Copy to Clipboard will ASCII order the constituent's Phone rows by phone type and then select the first one.

If the user includes data fields from the Internet Address table in his or her definition and the definition matches Address to Internet Address by Utilization and the selected Address to copy is the preferred address, then Copy to Clipboard will select the constituent's preferred Internet Address row; if the selected Address to copy is not the preferred Address, then no Internet Address data fields will be copied out. If the user includes data fields from the Internet Address table and the definition matches Address to Internet Address by Type, then Copy to Clipboard will select the Internet Address that has the same type as the selected Address. If no such Internet Address exists, then no Internet Address data fields will be copied out.

Each user's Copy to Clipboard definition is saved in the user_settings system table.

See Clipboard Setup, User Option and Addresses - Copy to Clipboard.

The Copy Clipboard Settings utility , a utility that closely relates to this enhancement, has been added to the software and is discussed under Tools Enhancements, below.

An Millennium user (with the exception of the System Administrator) can create and maintain multiple Sort definitions for each data table. New fields have been added to the sorts system table to support this functionality. Only one Sort definition at a time can be applied to a data table; the one that is applied will be considered the Active Sort on that table.

The Choose Sort menu item has been added to the context menu that is accessed via the Table Header. A user can easily select which Sort definition to flag as active and apply it to a table by utilizing this new menu item. And, the (none) item accessed via this Choose Sort menu item gives a user another way of removing a Sort from a data table. The Choose Sort menu item will be disabled if no Sort definition exists for a user, for a data table. Choose Sort will not be an available item on the context menu that is accessed via the Edit buttons that are associated with a table's individual data rows. Choose Sort will not be an available item for a user logged on as the System Administrator.

The Sort On/Sort Off toggle has been removed from the context menu that is accessed via the Edit buttons associated with a table's individual data rows. However, a user can continue to utilize the Sort On/Sort Off toggle on the context menu that is accessed via the Table Header, to apply the active Sort to a data table, or to remove the active Sort from a data table.

If a data table display is sorted, the Display Header will show the name of the Sort applied plus the word 'Sort'. For example, a Sort by zip code on the Address table is named Zip Code and is applied to the Address data table display, the Display Header will show '(Zip Code Sort)'.

A Delete button has been added to the Define Sort applet to allow a user to delete a Sort definition from the sorts system table.

The System Administrator (user name of 'sa' or 'MILLORA') can create and maintain two Sort definitions per data table. One Sort is applicable to his or her Snapshot View of the data and must be created and maintained via the Snapshot Setup Applet. The other Sort definition will be the System Sort definition for the data table, is named 'Profile Default', and is owned by the millennium_admin user name. If a user, other than the System Administrator, wants to apply the System Sort definition to a data table, he or she must first open the System Sort definition and then re-save it with a different name. Only the System Administrator can make changes to the System Sort Definition. Other user changes to the System Sort Definition must be saved with a different name.

For all Sorts that are currently owned by the System Administrator, the conversion to Millennium 7.7 will set the name to 'Profile Default' and set the user name (the owner) to 'millennium_admin'.

See Sorting and sorts system table.

An Millennium user (with the exception of the System Administrator) can create and maintain multiple Filter definitions for each data table. New fields have been added to the filters system table to support this functionality. Only one Filter definition at a time can be applied to a data table; the one that is applied will be considered the Active Filter on that table.

The Choose Filter menu item has been added to the context menu accessed via the Table Header. A user can easily select which Filter definition to flag as active and apply it to a table by utilizing this new menu item. And, the (none) item accessed via Choose Filter gives a user another way of removing a Filter from a data table. The Choose Filter menu item will be disabled if no Filter definition exists for a user, for a data table. Choose Filter will not be an available item on the context menu that is accessed via the Edit buttons that are associated with a table's individual data rows. Choose Filter will not be an available item for a user logged on as the System Administrator.

The Filter On/Filter Off toggle has been removed from the context menu that is accessed via the Edit buttons located to the left of a table's individual data rows. However, a user can continue to utilize the Filter On/Filter Off toggle on the context menu that is accessed via the Table Header to apply the active Filter to a data table, or to remove the active Filter from a data table.

If a Filter is applied to a data table display, the Display Header will show the name of the Filter plus the word 'Filter'. For example, a Filter by Attribute Group where the group is equal to 'Sports' is created, named Sports and applied to the Attribute data table display. The Display Header will show '(Sports Filter)'.

A Delete action menu bar item has been added to the Define Filter applet (access is via the applet's File function menu bar item) to allow a user to delete his or her Filter definitions from the filters system table.

The System Administrator (user name of 'sa' or 'MILLORA') can create and maintain two Filter definition per data table. One Filter is applicable to his or her Snapshot View of the data and must be created and maintained via the Snapshot Setup Applet.   The other Filter definition will be the System Filter definition for the data table, is named 'Profile Default', and is owned by the millennium_admin user name. If a user, other than the System Administrator, wants to apply the System Filter definition to a data table, he or she must first open the System Filter definition and then re-save it with a different name. Only the System Administrator can make changes to the System Filter Definition. Other user changes to the System Filter Definition must be saved with a different name.

The Choose Filter menu item is not available to the System Administrator.

For all Filters that are currently owned by the System Administrator, the conversion to Millennium 7.7 will set the name to 'Profile Default' and set the user name (the owner) to 'millennium_admin'.

See Filters and filters system table.

A Snapshot View of the data is similar to a user's Defined Data Display in that the user selects a subset of data tables to display when viewing a constituent's data. The Snapshot View, however, allows the user to select which rows within that subset of data tables to display, as well as the order in which they will display. In addition, the user can either choose to include Table Headers, data row separators, linked data, and/or data row Edit button Context Menus in the Snapshot View, or choose to exclude one or more of them from the Snapshot View.

Each user personalizes his or her own Snapshot View via the Snapshot Setup Applet, accessed from the Snapshot Setup User Option. A user selects the data tables, and options mentioned above, to include in his or her Snapshot View. This Snapshot View definition is then saved in the user_settings system table.

To use the Snapshot View, click on the Snapshot View item (or Snapshot Profile item, if you are a Windows interface user) toward the top of the Profiles items list in the Millennium Explorer.

To create or edit the Snapshot View, Use the Snapshot Setup User Option.

• For Browser interface users, the Snapshot Setup User Option is accessed via the Millennium Explorer. Expand the Profiles item and locate the User Options item at the end of the list. Expand User Options and select Snapshot Setup.
• For users of the Windows interface, the Snapshot Setup User Option is accessed via the Options Profile Action Button shown in the horizontal bar just above the Millennium display area. Click this Action Button, and select the Snapshot Setup menu item. Note that the Profiles Millennium Navigation bar item must be activated before this Profiles Options Action button displays.

Users (with the exception of the System Administrator) can create (or edit) multiple Sorts and Filters from within the Snapshot Setup Applet and then apply them to the Snapshot View. Sorts and Filters applied to a Snapshot View will not in affect the way data is sorted or filtered when the user views it in any other way. New Sorts that the user creates when defining his or her Snapshot View are saved to the sorts system table and are available for use even when the data is not displayed in Snapshot View. New Filters that the user creates are saved to the filters system table and are available for use even when the data is not displayed in Snapshot View. Similarly, changes (including deletions) that a user makes to existing Sorts when defining his or her Snapshot View are saved to the sorts table, and changes (including deletions) to existing Filters are saved to the filters system table.

The System Administrator can create only one Snapshot View Sort and one Snapshot View Filter per data table,each named Snapshot Default, from within the Snapshot Setup Applet. This Sort can only be used with his or her Snapshot View, and maintained from within the Snapshot Setup Applet.

If the System Administrator copies his or her Snapshot View definition to another Millennium user via the Copy Snapshot Settings utility, a data table's Snapshot Default Sort Definition and Snapshot Default Filter definition, if used in the System Administrator's Snapshot View definition, will be copied to the user as well. The user can then use this Snapshot Default Sort and Filter when maintaining his or her Snapshot View. If the user would like to use the Snapshot Default Sort or Filter outside of his or her Snapshot View, he or she must first open it from within the Snapshot Setup Applet and then save it with a different name.

See Snapshot Setup, User Option

The Copy Snapshot Settings utility, a utility that closely relates to this enhancement, has been added to the software and is discussed under Tools Enhancements, below.

Mailcodes (utilizations) have been added to the internetaddress and phone data tables. These codes are Y/N flags, their functionality is identical to the functionality of the address table utilization codes, and they will reference the address_utilization lookup table for their labels.

The Mailcode 1 fields for both internetaddress (intmc1) and phone (phnmc1) can be used to flag one preferred email address and one preferred phone number per constituent, if you so desire.

For existing internet address rows: the conversion to Millennium 7.7 will copy the value currently stored in the Preferred email Address (intpref) field into the Mailcode 1 (intmc1) field for each data row in the internetaddress table. The intpref field will no longer be used by the system.

As of version 7.6.1, Millennium supports the use of multiple merchant accounts for credit card and bank draft transaction processing through Paya Payment Solutions (SPS). The conversion to Millennium 7.6.1 moved the Verus id and Verus key values stored in the sysinfo table to the merchant id and merchant key fields in the merchant_account table and copied the default merchant id and merchant key to all credit card rows that did not have the merchant key filled in. For those sites who upgrade to version 7.7 directly from 7.6, the Millennium 7.7 conversion will do the same.

Background information: If your site chooses to allow users to save donor credit card and bank draft information for future use, account information is stored and can be retrieved by a user the next time a donor makes a contribution tendered by credit card or bank draft. All saved accounts for the donor display in a list box labeled Choose Accounts. The user can choose an account from this list or enter information for a new account on the credit card/bank draft insert form. If a saved account is chosen, the insert form is filled with the saved information. The user can then edit that information as desired before inserting the credit card/bank draft row.

Enhancements: The first item in the Choose Accounts list box will always be 'Choose Existing Account'. When the desired account is chosen, the credit card number (or bank account number, if the donation is tendered by bank draft) will display, masked with asterisks.

See Tender Data Maintenance, Bank Draft and Tender Data Maintenance, Credit Card.

For ease in data entry, USA will appear first in the drop down list of countries.

For every row inserted into the address_types lookup table, the system will a create a corresponding entry that is its 'Former' version. The Code for the 'former' entries will be the same as the original, but will end in 'f'. If the entry's code is 6 characters in length, the code for the 'former' entry will be the first five characters, plus the ending 'f'. The system will set the row's active flag (table_actv) and the Online Constituent Directory flag (table_ecom) to 'N'.

For existing rows in the address_types lookup table, the conversion to Millennium 7.7 will update all existing address types whose table value (table_val) contains the word 'Former' and set the active and Online Constituent Directory flags to 'N'.

If you site has existing address types without a corresponding 'Former' entry, you will need to manually add the corresponding 'Former' entry as the conversion utility will not do that for you.

If a Relation row has a Stop Date that is on or before the date that a user accesses his or her Favorite Prospects, a Relation Tree for a constituent, or a Prospect Tree for a constituent, then that Relation row will not be shown in those display (s).

The Credit Type field in the Gifts (giftcrdtyp) and Dues (duescrdtyp) data tables, previously listed as 'not available for use at this time', will now function as a secondary gift type so that a Giving or Dues Transaction can be further classified in whatever way your institution desires. The field is driven by the credit_types lookup table in both the Gifts and Dues tables. The field will not be included in either the standard Millennium Gifts/Dues Display or Maintenance forms. It must be added to these forms via the Custom Display Designer.

The starting month of the institution's fiscal year is now a system-wide option. The System Administrator sets this on the System Options page. When setting up Giving and Dues trends, individual users no longer will set the month to be used as the starting month of the institution's fiscal year.

Name-Suffix dropped from combined name when using Dr. title

When you change the Address Locator to Former when archiving an address, you receive a SQL Error if you do not let the archive process change this field to Former for you automatically.

Unable to remove Preferred Internet Address designation

Credit Card Insert; credapprov field missing from customized credit card insert form

The Comments publish flag 'commpubfl' is not being updated properly

Internet Address Preferred (intpref) and Publish (intpubfl) fields are not updating properly.

Gift insert using tender of credit card not populating credlast4 and credtender of creditcard table.

Unchecking the Attribute table link option in the Attribute Types lookup table makes the attribute unavailable on the Profiles Search Screen.

Combined Name is displaying in the Salutation field in letters

When you move the field codes to different locations in a letter document, the fields do not populate correctly when viewing the letter.

Journal & Corrected gift transaction with a subsequent journal does not appear in long or short display

Internet Address Defined Defaults Orphaned in prototype_name

When you have newly converted records in the Internet Addresses table or update existing records with a long comment, you receive an error message when viewing the record.

When a Parent Corporation has been added to a Basic Data Corporation, Foundation, or Organization record, you are unable to remove the association.

When entering dues transactions using the Fast Dues Entry process, the Automated Membership process is not being invoked with each transaction.

Giving/Dues insert or update does not accept account # in solicitation field and when applet fails, transaction form is cleared.

When a partial value is entered in the Attribute Type value-based (super) lookup field that should match multiple values in the Attribute Types lookup table, the applet is not finding the entries.

Defined Registration Status and Response Type lookup table values are not populating correctly from registration defined defaults

Assignments have been redesigned; most changes deal with the User Interface for defining Assignments.

See Categories and Assignments for a list of the types of Assignments that can be defined.

New Assignments

The Assignments applet is replaced by a Browser form with hyperlinks to access the possible types of Assignments that you might want to define.

The option exists to temporarily de-activate an Assignment at the time the Assignment is defined as well as when the Assignment is updated. Prior to Millennium 7.7, a user could temporarily de-activate (disable) an Assignment only by updating the Assignment.

Your Agent will run an Assignment only if the Assignment Run Status field (asgnrun) reads Success or is Null, the Assignment is Active (asgnactive = 'Y') and the Status is Enabled (asgnstatus = 'e').

• The system will set the Assignment Run Status field to Failure if an Assignment does not successfully execute. A user can then reset this field to Null by 'rechecking' the Assignment's Active flag. This will force the Agent to attempt to run the Assignment again.
• For certain Assignments, such as Campaign Amount, the system will set the Assignment Status field to Disabled (d) as a way of preventing the Assignment from needlessly running once the Assignment's criteria is met. Users can reset this field to Enabled (e) by re-saving the Assignment. See View Assignment, below, for more information.

Apply Notification To:

• An Assignment can be defined to focus on constituents who are listed in a worktable that your User ID 'owns'. This worktable may be a saved worktable that was generated when running report criteria, or a saved Search Results worktable.

• If you define an assignment to focus on your Prospects, you have the option remove those Prospects with a Relationship End Date that occurs before the End Date that you specify here.

Notification Via Letter

A user may now manually browse to the location of the Letter template by clicking the Browse button.

Notification Via Report: this has been removed as an option.

Criteria

The criteria available for some Assignment types has been modified. The Categories and Assignments topic includes a listing of available criteria for each Assignment type.

View Assignments

Prior to Millennium 7.7, defined Assignments were viewed in a grid-like display. This display has been replaced by a Browser form that lists each Assignment and its characteristics, such as Name, Category, Status, and Active/Inactive.

Prior to Millennium 7.7, the user could temporarily disable an Assignment by setting its Status radio button to Disabled. When the Assignment was viewed, the Status then read Disabled. In Millennium 7.7, the option for the user to set the Assignment Status to Enabled/Disabled has been removed from the Assignment update form and has been replaced by an Active Flag.

• To temporarily disable, or in other words deactivate, an Assignment, the user leaves the Active checkbox unchecked. The Active field in the View Assignments display will show the contents of the asgnactive data column: an N for an inactive Assignment and a Y for an active one. It may be important to note that the asgnactive data field was added to the Assignments table in Millennium 7.6. However, it was not in use until now.

• The system will continue to use the Status (asgnstatus) data field as a way to internally disable an Assignment. For example, the system will disable a Campaign Amount Assignment once the campaign reaches its target amount. However, the contents of the Status data field will no longer be shown on the View Assignments display.

The Status field on the View Assignments display will now show the contents of the Run Status (asgnrun) data field - Success, Failure, or Pending.

To the left of each Assignment is an Edit button, from which you can access a context menu that will enable you to update or delete an Assignment, set your Assignments to Active all at one time, or set your Assignments to Inactive all at one time. Prior to Millennium 7.7, you were not able to edit the name of a previously defined Assignment; now you can.

The conversion to Millennium 7.7 will update all existing Assignments by setting their Active (asgnactive) flags to 'Y'. If you had temporarily disabled an Assignment (by setting the asgnstatus field to Disabled) and still want for your Agent to not run this Assignment, you must manually edit it and uncheck the Active Flag. Each time the Millennium 7.7 conversion utility is run, it will set the Active flags of all Assignments to 'Y'. Each user will then have to manually edit his or her inactive Assignments and reset the Active flags back to 'N'.

A default reporting Queue and a default reporting Printer can be assigned to each user. When a user runs a report and sets that report's Run Options, the Queue name that is highlighted will be this assigned default Queue and the Printer name that is highlighted, if the report's destination is Printer, will be this assigned default Printer.

A default reporting Queue and a default reporting Printer for an individual report can be assigned via the Advanced Report Options form. These, then, will be the Queue and Printer names that are highlighted on the report's Run Options form each time the report is run.

The System Administrator can assign a default Queue and default Printer to all users who are members of a particular Millennium User Group via Group Maintenance. The System Administrator can assign a default Queue and Printer on a user by user basis via User Maintenance.

Any changes to the default Queue and Printer made at the Millennium User Group level, via Group Maintenance, will cascade to all individual users within that group; that is to say, these changes will override the defaults that were previously assigned to each user.

If no default Queue has been specifically assigned to a user, the system default Queue will be the default Queue for the user. If no default Printer has been assigned to a user, the system default Printer for the default Queue (whether the system default, or user assigned) will be the user's default Printer.

Two new fields have been added to the report_options system table to accommodate this new functionality:

• default_queue
• default_printer

When a new user group or a new user is inserted into Millennium a row for that group or that user will also be inserted into the report_options system table. When an existing user group is updated, if a row in the report_options table does not already exist for that group, then a row for the group will be inserted into the report_options system table. And when an existing user is updated, a row for the user will be inserted into the report_options system table if one does not already exist for that user name. Rows inserted into the report_options system table will be assigned default values for certain of the table's columns. See the report_options documentation for these default values.

See Group Maintenance, User Maintenance, Report Options, and System Information, Millennium Reporting Queues.

Crystal XI runtime is incorporated into Millennium. You may continue to create reports using older versions of Crystal, but do not install an older version of Crystal on either your IIS or your reporting servers.

The answers to <Prompted reply> criteria, and any standard Millennium parameter values , or Crystal parameter values, can be saved from one report run to the next.

Set the Save/Use Prompted Replies? option, located near the end of the Run Options screen, to Yes if you want to save the answers to <prompted reply> criteria, as well as the values supplied for any parameters included in the report, so that they can be used the next time that the report is run. Set this option to No if you do not want to save your prompts answers/parameter values. In addition, you may set this option to No if you have saved your prompts answers/parameter values in the past, but do not want the prompted replies/parameter values to default to these saved values for this particular run of the report.

This option is by individual user, by individual report, and always defaults to Yes.

See Running Report Criteria, Save/Use Prompted Replies?, Running Report Criteria, Prompts, and Running Report Criteria, Parameters.

Prior to Millennium 7.7, Online Directory Reports would limit the selection of constituents to those whose user names (coreuserec) were not blank and who were required to change their passwords when they next logged on to the Online Constituent Directory (core1passw = 'Y'). Online Directory Reports now include an option to not limit the selection, and Millennium Reporter will decrypt the ecomm password for all those constituents who are selected. This option is labeled Ecommerce Password and accessed via the Report Form, Options, Default.

The Copy and Paste Functionality, for use when constructing 'In The List Of' report criteria statements, is available for Browser Interface Users Only.

The Report Form can now be placed into either Clipboard Edit (multi-select) or Normal (single-select) Edit mode. On the Default Report Options Form, the Show Clipboard radio button has been added to enable the Clipboard Edit mode functionality. The default setting for this button will be Yes.

If the Show Clipboard radio button is set to Yes, the Report Form can be placed into Clipboard Edit mode (it does not have to be). When it is in Clipboard Edit mode, the Clipboard Controls - a Cancel Clipboard button, a Clear Clipboard button, and a Paste Window - will display on the Report Form. See Clipboard Controls for their functionality. In Clipboard Edit mode, multiple criteria lines and statements can be copied or cut, and then pasted, all at one time. In addition, criteria lines and statements can be copied or cut from one report, and then pasted into a different report. Behind the scenes, the copied or cut criteria are stored in the report_clipboard system table. The contents of the clipboard will be replaced when different criteria is copied or cut. In Clipboard Edit mode, the clipboard contents will be cleared only when the user clicks the Clear Clipboard button, or the user logs out of Millennium.  When the clipboard is cleared, the rows that the user owns in the report_clipboard system table will be deleted.

If the Show Clipboard radio button is set to No, then the Report Form remains in Normal Edit mode. The Clipboard Controls will not display. Only one criteria statement or line of criteria can be copied or cut, and then pasted, at one time. Criteria lines and statements can only be pasted into the same report from which they are cut. Copied or cut criteria are not stored in the report_clipboard system table. In Normal Edit mode, the contents of the clipboard will be cleared when they are pasted, when the current report is saved (via Save, Save As, or Run) or when the current report is no longer displayed for editing.

When the Show Clipboard Default Report option is set to Yes, the Clipboard Edit Function action item is enabled and can be used to toggle the Report Form's Edit mode between Clipboard and Normal. If the Show Clipboard option is set to No, the Clipboard item will remain disabled.

See Report Form, Edit Modes, Default Report Options, Edit Functions - Clipboard, Cut, Copy, Paste

A simple undo feature has been added to the Report Form.

The Undo action item has been added to the Edit Function menu bar. For each individual report criteria editing session, every new line of criteria that you add (via Add New, or Paste), every line of criteria that you change, and every line of criteria that you cut, will be held in an Undo buffer, and will be ordered from the first criteria line building or editing step (change) that you perform, to the last.  This will allow for a single line of criteria to be undone, one step at a time, from the very last criteria line 'change', all the way back to the first.

There is no Redo function. Undo is one way only and once 'Undone' is applied, it cannot be redone - once Undo is clicked, the step that is undone is cleared from the Undo buffer.

The entire Undo buffer contents will be cleared when the current report is saved (via Save, Save As, or Run) or when the current report is no longer displayed for editing.

See Edit Functions, Undo

The following characters are no longer allowed in report names:

• % (percent)
• ? (question mark)
• - (dash)
• $ (dollar sign)
• @ (at)
• ! (exclamation)

We strongly recommend that all punctuation, except for the underscore character, be avoided in report names.

The Millennium 7.7 conversion will replace the invalid characters listed above with an underscore in both the express_reports report_name field and the report_descripts report_name field. If this replacement causes a report name to be duplicated, a '2' will be appended to the end of the report whose name is changed. The old report name and new report name will be saved in a table called report_name_changes. If you are an Oracle site, this table is located in the data database. If not, this table is located in the millreports database.

The Institution Name text box has been removed from the Default Report Options form. If the Institution Name is passed as a parameter to a Crystal format, the name that will print will be the Institution Name that is stored in the sysinfo system table.

Rescheduled qqq files are written incorrectly to the queue folder when running utilities.

Reports selecting over 20000 records utilizing totals, summaries/years utility or decryption cause 'runrepor' to hang at Totals

When running a Custom Profile report on any field in the chart_of_accounts table, you receive an ORA-00923: FROM keyword not found error.

When running a user defined script that uses a custom worktable instead of the Generic, the contents created by the user defined script are not being saved to the custom worktable.

When you set a specific Options > Default 'Include Salutation' name type within a report, it is using the preferred name type instead of the selected name type.

If your site chooses to customize the Sample website HTML pages that Millennium provides, the customized versions must be saved to the \\Inetpub\wwwroot\ecomm\ directory, in the custom folder. The customized versions must have the same name as the standard Sample website HTML pages. When the Online Constituent Directory is accessed, Millennium will first look in the custom folder for the relevant HTML Pages, by name, and, if found, will load your version of the pages. If not found, it will then locate, in the \\Inetpub\wwwroot\ecomm directory, the standard version of the pages and load them.

When, in future releases, Millennium updates the Sample website HTML Page, only those pages that are contained in the \\Inetpub\wwwroot\ecomm will be updated. Pages in the custom folder should remain untouched, and it will be your site's responsibility to edit your customized pages to reflect the changes that Millennium makes to the standard pages.

Important! It is very important that you back up all of your site's customized website HTML Pages in the \\Inetpub\wwwroot\ecomm directory before installing Millennium 7.7. The Millennium 7.7 installation will create a new folder, called custom, in the \\Inetpub\wwwroot\ecomm directory. Once the installation is complete, move your custom website HTML Pages to this new custom folder.

The ability to make a donation in the form of a Sustainer Pledge has been added to the Online Constituent Directory.

Donors who contribute to your institution via Donate Now, the online giving component of the Online Constituent Directory, can choose to make either a one time donation, which the Advanced Data Examiner will then process as a Gift transaction, or they can make a recurring donation, which the Advanced Data Examiner will then process as a Sustainer Pledge.

If your site has a Customized Display of the Ecommerce pages (constituent and non-constituent), you must delete them and then re-customize in order to view the new data fields that support Sustainer Pledge donations.

When a donor enters credit card information, the expiration month and expiration year is selected from items listed in drop-list boxes. The expiration month list box will list the values 01 through 12. The expiration year list box will list ten years, beginning with the current year

A new field, named coreocdin, has been added to the corebio table. Millennium will automatically record the date and the time that a constituent last logged on to the Online Constituent Directory and store this date and time in this field.

An address in the input file can be matched to an existing Millennium address by address utilization (addrmc1) or by address type.

The utility can be launched and run in an unattended mode. The Unattended Mode Settings menu item on the utility's Main Application Window accesses the interface by which a user supplies all of the information that the utility will need in order to run the import into the pending tables without user input. This information is stored in an initialization file, located in the same directory as the utility's executable, to be used when the utility is launched from a command prompt or other unattended method.

If the Millennium log on password for a user who has set up the utility to run in an unattended mode is changed, the user will have to manually update his or her password before the utility can again be successfully be launched in an unattended mode.

See Using the ADE Import Tool - Unattended Mode.

Matching by the new alternate ID fields (corealtid2, corealtid3, corealtid4, corealtid5), or the Core Number 1 (corenum1) field has been added to the ADE Import Tool; you may choose one of these as the Millennium Identifier, if so desired.

The ADE Import Tool allows the Rel Whose ID field ( relrelatid) to be mapped so that the Advanced Data Examiner can create constituent relationships. The Rel Whose ID number must be the id number of an already-existing Millennium constituent.

In addition, the Import Tool enforces the following rules with regards to mapping and importing relationship types:

• If one of the relationship type fields is mapped, they both must be mapped. That is to say, if the Rel Is A (relisa) field is mapped, then the Rel Whose (relwhose) must be mapped, and visa versa.

• If the relationship type fields are mapped, they must both be mapped to fields in the input file, or they must both be mapped to lookup table codes. That is to say, if the Rel Is A (relisa) field is mapped to a code in the relationships lookup table, then the Rel Whose (relwhose) field must be mapped to a code in the relationships lookup table as well, and visa versa.

• If the relationship type fields are mapped, then the relationship must be one that is allowed by the system (see Allowable Relationships).

If both the Rel Is A ID field (relid) and Rel Whose ID field (relrelatid) are mapped, then the utility will check for duplicate spouses. The Rel Is A ID can own a constituent spousal relationship with the Rel Whose ID only. The Rel Is A ID can own a non-constituent spousal relationship as the Advanced Data Examiner will give you the opportunity to change this to a constituent relationship if you so choose. The Rel Whose ID can own a constituent spousal relationship with the Rel Is A ID only. However, the Rel Whose ID can not own a non-constituent spousal relationship.

The ADE Import Tool does not attempt to match a pending record to a relation record; however, the Advanced Data Examiner will attempt to match a pending spousal relationship to one that already exists in Millennium.

When reviewing Address pending data, the Advanced Data Examiner will display all of the constituent's existing Address records. This enables the following functionality:

• If the pending Address row is presented as a new data row to insert, and you would like to use the pending information to update one of the existing Address rows instead, select the Update this Address menu item from the context menu accessed via the edit button located to the left of the Address row you want to update. The information from the selected Address row will display to the left of the pending Address information, and the ADE will then process the pending Address row as an update to that selected Address.

• If the pending Address row is presented as an update to an existing Address row, but you would like to update another existing Address row instead, use the Update this Address context menu item to select the Address you do want to update. The information that displays to the left of the pending Address information will now be the information from the selected Address, and the ADE will then process the pending Address row as an update to that existing Address instead

The Advanced Data Examiner now processes both non-constituent and constituent Relation rows, and processes Relation rows for all relationship types. If the pending Relation row's relkey is populated with the relkey value from an existing Relation row, then the pending row will be presented as an update to that existing Relation row. If the pending row's relationship type is spousal, the ADE will search Millennium for an existing spousal Relation for the pending row's owner - a pending Relation row is 'owned' by the constituent identified by the Is A ID number (relid). If one is found, then the pending row will be presented as an update to the existing spousal Relation instead of as a new Relation row insert. If the relationship type is not a spousal one, the ADE will always present the pending row as a new row to be inserted into Millennium (unless the relkey is populated with a relkey from an existing Relation row).

If the pending Relation row's Rel Whose ID Number field (relrelatid) identifies an existing Millennium constituent, the ADE will process that pending row as a constituent Relation row. If not, the pending data information is presented as a non-constituent Relation row. You may leave as is and the ADE will process the row as a non-constituent row, or, if you believe that the pending row's name information will identify an existing constituent, you may 'instruct' the ADE to attempt to process the pending row as a constituent Relation row by checking the Change to Constituent check box.

As it now does for addresses, the ADE will display, for the constituent who owns the pending Relation row, all of his or her existing Relation records. If the pending Relation row is presented as a new data row to insert, but you would like to use the pending information to update one of the existing Relation rows instead, select the Update this Relationship menu item from the context menu accessed via the edit button located to the left of the Relation row you want to update. The information from the selected Relation row will now display to the left of the pending Relation information, and the ADE will then process the pending Relation row as an update to that Relation row.

If the pending Relation row is initially presented as an update to an existing Relation row, but you would like to update one of the other Relation rows instead, use the Update this Relationship context menu item noted above to select the Relation you do want to update. The information that displays to the left of the pending information will now be the information from the Relation row you have just selected, and the ADE will then process the pending Relation row as an update to that existing Relation.

When the ADE creates a new Relation row from the pending information, it uses the standard Millennium data entry procedures for creating Relation rows.

Error running the Login Creation utility

User id 'coreuserec' deleted when clicking forgot hyperlink

Customized OCD profile search screen causes 404 error when searching for other constituents

Pending Data Column includes data from Current Data row even though this data does not exist in the pending table.

'Search for Other Members' is creating views in database that are not being dropped when you log out

Online Constituent Directory Missing 4 Ecomm Updated Templates

Display Masks are now a User Group option, as well as a System Option. One of four types of display masks for each of the social security number, credit card number, and bank account number can be assigned on a User Group by User Group basis via the Group Maintenance applet. The four types available are:

• Default Mask - applies the System Defined Display Mask, which is aSystem Option.

• No Mask - displays the entire number; no mask is applied

• Last 4 Visible Mask - displays only the last 4 digits; a mask is applied to all but the last 4 digits.

• Complete Mask - a mask is applied to the entire number.

Each member of the Millennium User Group would then view social security, credit card, and bank account numbers with the display masks that are assigned to his or her User Group.

User Group Display Mask Settings are stored in the userlist system table user_security field for the user names that reference names of Millennium User Groups.

The User Maintenance Copy User functionality is expanded to accommodate the new default queue and printer functionality and to copy the existing user's Snapshot Settings, Defined Displays, other display and data entry options, Defined Defaults (prototypes), sorts and filters.

A row for the new user will be created in the userlist table. The options as set on the User Maintenance Form and the existing user's Defined Display definition, other display options (such as transaction display options), and data entry options (such as match options) will be copied into this new row and therefore 'assigned' to the new user. The display modes (Long versus Short) that the existing user last used when viewing the data tables will be copied into this new row. The new user will also be 'assigned' the existing user's default gift and dues batch numbers, gift trends and dues trends settings, and Agent character. A row for the new user will be created in the report_options system tables, containing the table's default values as well as the existing user's default queue and default printer as assigned on his or her User Maintenance form. If the existing user has a Snapshot View defined, a row will be created in the user_settings system table for the new user. A new row for each of the existing user's sorts will be created for the new user in the sorts table. If the existing user is displaying one or more data tables with a sort applied, the new user will see those data tables displayed with the same sorts applied. A new row of each of the existing user's filters will be created for the new user in the filters system. And, if the existing user is displaying one or more data tables with a filter applied, the new user will see those data tables displayed with the same filters applied. The new user will also get a copy of the existing user's Defined Defaults (prototypes).

A new menu item has been added to the Custom Display Designer. Copy To copies the Custom Display Definition for a data table from one display mode (Long, Short, Mini, Snapshot, and so forth) to another.

The customized Copy to Clipboard layout definition for one user can be copied to one or more other Millennium users via the Copy Clipboard Settings utility. Access to this utility is limited to the System Administrator (logged on as 'sa' or 'MILLORA, if Oracle). Once logged on, the System Administrator navigates to the Clipboard Setup User Option to access the Clipboard Settings Applet, and clicks the Copy to Users button access the Copy Clipboard Settings utility. The Copy to Users button is visible only to users System Administrator users.

This utility will enable the System Administrator to select the Copy from User (that user whose Copy to Clipboard layout definition you want to copy to the other users), and then select one or more Copy to Users (those users to whom you will be copying the definition). The utility includes features that will let you select the Copy to Users one at a time, in multiples, or by Millennium user group.

The ability for each user to customize his or her Copy to Clipboard layout definition is an enhancement new to this release and is discussed under Profiles Enhancements, above.

A Snapshot View definition for one user can be copied to one or more other Millennium users via the Copy Snapshot Settings utility. Any Sorts included in the definition will be copied to the other Millennium user (s). Any Filters included in the definition will be copied to the other Millennium user (s) as well. The copied Sorts and Filters will then available for the other Millennium users even if the data is not displayed using a Snapshot View.

The System Snapshot View definition (Snapshot Default) can also be copied to one or more other Millennium users, and any Sorts and Filters included in the definition will be copied to the other Millennium users as well. The copied Sorts and Filters, however, will only be available for the other Millennium users to the data is not displayed in a Snapshot View only if they first open them from within the Snapshot Setup Applet, and then save them with a different name.

Access to the Copy Snapshot Settings utility is limited to the System Administrator (logged on as 'sa' or 'MILLORA', if Oracle). Once logged on, the System Administrator navigates to the Snapshot Setup User Option to access the Snapshot Setup Applet, and clicks the Copy to Users button to launch the Copy Snapshot Settings utility. Note that the Copy to Users button will display on the Snapshot Setup Applet for System Administrator users only.

Once launched, The System Administrator selects the Copy from User (that user whose Snapshot View definition you want to copy to the other users), and then selects one or more Copy to Users (those users to whom you will be copying the definition). The utility includes features that will let you select the Copy to Users one at a time, in multiples, or by Millennium user group.

The ability for each user to create a Snapshot View definition is an enhancement new to this release and is discussed under Profiles Enhancements, above.

The ability to access external applications from within Millennium allows sites to tie-in their in-house Millennium applications to the Millennium interface. The System Administrator utilizes the Custom Utilities > Setup page to create and maintain a list of the applications that can be accessed from within the Millennium interface. All Millennium users can then launch or otherwise access these applications via hyperlinks on the Custom Utilities > Utilities Page.

If an in-house application has an installation program, then that installation program must be executed on a user's local machine (the client machine) before a user can successfully launch and use the application. In addition, the directory and folder containing the application must be shared and accessible from a user's local machine.

Important! Sites are cautioned to not use this as a way to launch the standard Millennium utilities that must be run on the IIS machine.

Before it begins to make any changes to the database, the Merge ID utility will check for duplicate spousal-type relationships. If both the Merge to ID (Primary ID)constituent and the Merge From ID (Secondary ID) constituent have a spousal-type relationship, the utility will return a message to inform you of this. Click Cancel to exit the utility and resolve this issue manually before launching the utility again.

In support of the Secondary Gift Type enhancement, noted above, the ability to map the secondary gift type (giftcrdtyp) to either a field in the input file or to an active, valid entry in the credit_types lookup table was added to the standard Phonathon utility.

The Reset Fields button located on the utility's main form was moved over to the left of the form.

All lookup table driven field codes are required to be active entries in their corresponding lookup tables.

In support of the Secondary Gift Type enhancement, noted above, the ability to map the secondary gift type (giftcrdtyp) to either a field in the input file or to an active, valid entry in the credit_types lookup table was added to the standard Gift Import utility.

All lookup table driven field codes are required to be active entries in their corresponding lookup tables.

Customizer should not pop up message to save receipts maintenance form

Prototype.exe utility is not creating default tables with fields that are consistent with its corresponding table.

Canceling from Gift Batch Number Insert causes application to hang

View Generator Error creating tracking view using Create All option

A searchable, keyword index has been added to the Help files. Browser users will access the index via the Millennium Explorer Reference World. Expand the Millennium Help item and select Help Contents. Click the Show button located in the upper right corner of the Help Contents page. In the frame that loads on the left side of the display screen, click the Index tab.

Windows Users: Click the round Home button located to the left of the main Millennium toolbar and then select the Help item in the Millennium Explorer on the left. The Welcome to Millennium page is launched in a new browser window. If the frame with three tabs is not displayed to the left of the Welcome page, click the Show button located in the upper right corner of the Welcome Page. In the frame that loads on the left side of the display screen, click the Index tab.

Documentation incorrectly reflected what the triggers do; it is changed to read:

Indicates the category for this constituent as defined by the CAE. When a new basic data row is inserted, the triggers will automatically populate this field with contents of the table_cfae field of the constituent type table if CAE Type field on the insert form is blank. If a basic data row is updated, and that update includes a change in coreconst (Constituent Type), the update triggers will not automatically change the value of corecfae.

Corrected to: When a Basic Data row is inserted, Millennium automatically populates the CAE Category field with the CAE that is associated with the Constituent Type that you have entered. This association is determined by the value of the table_cfae field in the Constituent Types (constituent_types) lookup table for each Constituent Type. And, if a Basic Data row is updated, and that update includes a change to the Constituent Type, Millennium will automatically update the CAE Category to the CAE that is associated with the Constituent Type via this table_cfae field.

For example, a Constituent Type of Alumni is associated with a CAE of 'Alumni'. If you insert a new constituent, with a Constituent Type of Alumni, into the database, the CAE field will auto-populate with 'Alumni'. In another example, a Constituent Type of Major Donor is associated with a CAE type of <blank>. If you update a record for a constituent with a Type of Individual and change her Constituent Type to Major Donor, the CAE field will auto-populate with a <blank>.

This behavior occurs automatically even if you have entered contradictory information for the CAE Category in the insert or update form. You may, however, override the automatic entry of the CAE Category by editing the Basic Data row once it has been created or updated. When you manually edit this field, the system will accept your inputted CAE in preference to the CAE that is associated with the Constituent Type lookup entry.

The rules that the Harris Utility uses to find matching Millennium records for Name, Address, Employment and Education information has been documented.

Documented the user_alertkey - a field that was added to the userlist table in Millennium 76.

Documentation for posting a Payment on a Multiple Allocation Transaction has been moved from the Allocation Data Maintenance topic to the Pledge Data Maintenance Topic.

Information about editing a payment schedule has been removed from this topic. Some of this information was outdated and the current information was located in the Payments topic already.

Documentation for the Advanced Data Examiner Matching Levels and Defined Defaults set up functions has been moved from the Online Constituent Directory Setup topic to the Advanced Data Examiner topic.

Documentation for Online Constituent Directory Reports has been moved from the Online Constituent Directory Log On topic to the Online Constituent Directory Reports topic.

The ability to use smart tags when setting up the email messages that are sent to constituents who forget their Online Constituent Directory log on credentials (as of release 7.6) means that these constituents no longer have to make separate user name and password information requests. The text within the documentation that states that they must make separate requests has been removed.

Enhancements, changes, and corrections made to the ADE Import Tool will be listed in the current release documentation with the Online Constituent Directory and Data Examiner Enhancements/Changes or Corrections. They were previously listed with the Tools Enhancements/Changes or Corrections.

Added documentation for the Ecommerce Users (GENERIC_ECOMM) export worktable format, which is used with the Online Constituent Directory Report and Online Constituent Directory Export Reports.

It is important to note that a worktable that uses the Ecommerce Users format will not be able to be saved.

The ADE Import Tool and ADE Import Tool and Events topics are now listed as subtopics of the Advanced Data Examiner. They were previously listed as subtopics of Utilities.

Change Select to the relevant _full view

Change Update to the relevant _pending view.

Change Delete to the relevant _pending view.

Change Insert to the relevant _pending view

previously stated:

Change Select to the relevant _full view

Change Update to the relevant _pending view.

Change Delete to the relevant _pending view.

Change Update to the relevant _pending view

Sites utilizing Microsoft SQL Server as their database engine are warned that enabling the Auto Shrink option may cause degradation in performance and cause utilities and reports to hang.

Fields from the Chart of Accounts table were made available for reporting through Millennium Reporter when Millennium 7.5 was released. This functionality has been documented.

Corrected the description of the ecommatchco and ecomjoint fields in the ecommerce_pending table documentation.

If a set of report criteria contain more than one prompted criteria statement, then the prompting text for each criteria statement must be unique.

The task reminder notice functionality is only available for those who use Millennium's Browser interface.

Do not pass a Null value as the field value parameter to the Crystal User Defined Functions millDecrypt or millEncrypt.

Utilization Codes are part of the standard Long Data Display and Data Maintenance forms for the Address, Phone Number, and Internet Address table. The Custom Display Designer can be used to add Utilization Codes to other Data Display forms, such and Short and/or Mini. However, if you add the Utilization by selecting the mc1, mc2, etc. field from the Customizer's Data Column List box, instead of the 'formatted' Utilizations field, the labels for the added Utilizations will be those from the added utilization field's alias in the fieldlst table. This is now documented in the Address, Phone Number, and Internet Address Utilizations topics.

For multiple allocation Pledge Transactions, if the Giving or Dues display mode is set to Long, a Post Pledge Payment icon will be shown directly beneath the allocation information for all allocations other than the first.   This icon was added to the software in a previous release, but was not documented.

Documentation updating and clarification.

repaired the Demographic Data Viewer, IRS Digital Daily (renamed to IRS Newsroom), and Mother Jones 400 links

removed the following from the Online Constituent Directory Sample website documentation:

If you so choose to integrate the sample website into an existing website, it is recommended that the site makes a copy of the ecomm folder found under \\Inetpub\wwwroot\ and creates a new folder under the same \\Inetpub\wwwroot\ directory to be customized. This allows the site to make any changes to a copy of the original sample website and revert back to the sample for it's original state. For, when you go to the previous mentioned URL and click on the 'click here' link you will be directed to the Log in page for Online Constituent Directory as well, but a few changes must be made to incorporate your existing website. When using the sample website you will notice the URL of http://<servername>/ecomm which is directing you to the sample website. Please note that when copying all the files from the ecomm folder to a newly named folder, you will also need to change the directed URL from http://<servername>/ecomm to http://<servername>/newfoldername. This allows you to go directly to your customized website and not the sample website. Along with the usernames and passwords you will be sending out to constituents, this new URL is the one that you will want to send out for them to log in to.

This was incorrect. In order for the Online Constituent Directory to work, all pages must be located in the \\Inetpub\wwwroot\ecomm directory. New for Millennium 7.7 will be the opportunity to save your site's custom HTML pages in to the custom folder located at the root of this directory.

The following has been added to the Online Directory Sample website topic:

In addition to updating the HTML page in the \\Inetpub\wwwroot\ecomm directory Millennium will place a copy of the updated page into the \\Inetpub\wwwroot\ecomm directory, in the Updated Templates folder. Millennium will not utilize the HTML pages in this folder in any way; this is done only to aid you in determining which HTML pages have been updated.

reference charts have been added to the documentation in order to help our sites to determine the menu choice, within each version of the Custom Display Designer, that is needed to modify the Millennium Display and Maintenance Forms relevant to each listed Millennium Explorer Choice or listed Millennium task.

No more than 2000 id numbers can be 'imported' into Report Criteria via the Add Import control on the Report Form.

The subsection 'Update Credits and Honors' is titled 'Updated Linked Transactions' instead of 'Update Credits and Honors'.

The prompting text for a Prompted Reply object should consist of numbers and/or upper and lower case letters only, with no punctuation. Other characters may work, but it is recommended that they not be used; for example, a colon (:) will not work.

When using stored parameters, if the field 'lookup_table' is populated with a table name, no values are available for selection at the prompt. If the field is populated with a data table's lookup-table driven column's name (for example, coreconst instead of constituent_types), the values are available. The documentation incorrectly stated that the lookup_table field should be populated with the name of the lookup table.

Online Help missing description for "report_type" field in the express_reports table

On Update, if the parent corporation field data is deleted (changed to 0) the parent corporation/subsidiary relationships are deleted. It should not say change to 0, if you put a 0 in there Millennium does a name lookup. To remove the relationship, remove the name of the parent corporation to set the field to blank.

Utilization codes (also known as Mailcodes) have been added to the internetaddress data table. These codes are Y/N flags, their functionality is identical to the functionality of the address table utilization codes, and they will reference the address_utilization lookup table for their labels.

Utilization codes (also known as Mailcodes) have been added to the phone number data table. These codes are Y/N flags, their functionality is identical to the functionality of the address table utilization codes, and they will reference the address_utilization lookup table for their labels.

Custom fields have been added to the data tables that are listed on the left and to chart_of_accounts. These custom are as follows:

• 10 date/time fields
• 10 money fields
• 10 numeric fields
• 10 Yes/No flag fields (12 have been added to plannedgifts)
• 5 free text fields

3 custom lookup table-driven fields have been added to the following data tables:

• chart_of_accounts
• corebio
• address
• attribute
• gifts
• education
• dues
• donor
• actions
• tasks
• rating
• plannedgifts
• event
• membership
• proposal
• attendance
• custombio
• customprospect

A new lookup table has been added to the database for each of the new custom lookup fields added.

This table is added to the database to support Millennium's ability to access external applications from within the Millennium interface.

The copy_to_clipboard field is added to store the 'Allow ID number's to be Copied from the Search Results Screen to the Clipboard' system setting.

The fy_start_month is added to store the start month of your institution's fiscal year. For example, if your fiscal year goes from July 1 to June 30, fy_start_month will be equal to '07'.

The new fields are added to support the Multiple Filters and Snapshot View enhancements.

The new fields are added to support the Multiple Sorts and Snapshot View enhancements.

This table is added to the database to support the Copy to Clipboard and the Snapshot View enhancements.

The conversion to Millennium 7.7 will add a new row in this table for every user in userlist.

The default_printer and default_queue fields will hold the names of the default reporting queue and default report printer for each user as well as for each Millennium user group, if a default report Queue or Printer is assigned to the group.

new_ocd_users is a Y/N flag to hold the value of the Ecommerce Password Default Report Options setting.

The coreocdin field indicates the date and time the constituent last logged on to the Online Constituent Directory.

The following fields are custom alternate id fields, available to your institution to track one or more alternate identifiers for a constituent.

• corealtid2
• corealtid3
• corealtid4
• corealtid5

The following fields were added to the assignments data table:

• asgnworktb
• asgncoluse
• asgnpmdate
• asgnactive