>

Millennium Release Notes 7.2.2

System-wide Enhancements

Profiles World Enhancements

Profiles World Corrections

Events World Enhancements

Events World Corrections

Reporting World Enhancements

Reporting World Corrections

Standard Reporting Enhancements

Standard Reporting Corrections

Tools World Enhancements

Tools World Corrections

IDEA Enhancements / Corrections

Reference Enhancements / Corrections

Database and System Changes

Online Constituent Directory Enhancements

Interface - Database

Function

Description

Browser/Both

Macintosh OS

Macintosh OS X Panther Version 10.3+ is required for Millennium Version 7.3. It is mandatory that Safari 1.2 and Java 1.4.2 be used with this newest version of Macintosh.

Note: If prior versions of Macintosh are still being used please be aware that all functionality is not available and that it is mandatory that Netscape Communicator 4.78 and MRJ 2.2.5 be used.

Browser

Agents/Assignments

The Agent component of Millennium is now fully accessible from the Browser interface. Previously, these functions were only available via the Windows interface. Using this feature, each user may define any number of Assignments to be carried out by the user's personal Agent. Assignment definitions instruct the Agent to scan the database periodically for certain data changes, and when found, to notify you of that fact. Notification can occur as a pop-up text message or delivered as an audible message from an animated character, whether you are logged into Millennium at that moment or not. For instance, you might want to be notified when a particular constituent changes address or employment, or when any of the constituents for whom you are prospect manager make a donation, or when a certain campaign achieves a particular milestone amount. In addition, the agent can send an email to any address that you choose, or prepare a letter, or report using information from your assignment definition.

Both/Both

Appearance

Each Millennium user may now independently control several additional aspects of the display throughout the system, to suit his or her own needs and preferences. This includes the background color or image, the font style, size, and color for the table headers, for the data, and for the data labels, and the choice of colors to be used for highlighted and accented information. Images to be used as a background must be stored on the IIS. Appearance settings are controlled via the My Millennium item within the Millennium Explorer and are applied to the user's access to each of the worlds of Millennium.

Both/Both

Correct GM

A new, optional module is available as a means of having the most timely information about Matching Gift corporations, foundations, and their subsidiaries. Institutions choosing to subscribe to Correct GM (Gift Match) will periodically download data files from Community Brands, containing information gathered by Higher Education Publishing (HEP). Functions have been added to Millennium that allow that data to be linked for display to the Basic Data row for the matching entity or its subsidiary or affiliated foundation. The data includes such details as matching ratios and gift ranges, contact info, eligibility, policies, and subsidiaries.

Both/Both

Data Display and Maintenance

Prior to Release 7.3, the Browser interface was dependent on the use of HTML templates to control the display and maintenance of data, and the Windows interface used the Customizer to control the comparable functions. Sites that had users of both kinds of interfaces, who also wanted to make customizations to the data display and maintenance forms were required to make those customizations for both interfaces.

With Release 7.3, each site will make an institutional determination on which technique (either HTML Templates or the Customizer) it will use to control the Screen Layout of the display and maintenance area (the large box on the lower right side of the screen) and to make any desired customizations. This institutional choice does not restrict the ability of the individual users at the site to use either of the interfaces (either Browser or Windows.) Thus, a site might choose to use the Customizer to control the layout of the display area, and yet all or some of the individual users might use the Browser interface (the Explorer and the Toolbars portions of the screen) to access Millennium. And conversely, the site might choose to use HTML templates (the .mit files) to define the display area and maintenance forms, and yet all or some of the individual users might use the Windows interface.

The institutional choice for a Screen Layout option is set in the System Options page within the Tools World.

To accommodate this standardization, both displays now use a combination of edit buttons and context menus to perform all functions. Previously, the Browser interface used buttons in the display header for functions such as Insert, Default, Options and Help, and a Special button within the maintenance form accessed a context menu for additional functions. Previously in the Windows interface, those functions were accessed by clicking the display of a specific data row, or right clicking the display of a specific data row, or on the table header to produce a context menu of functions. With this release, all displays use 'fly-over' context menus to perform the same functions that were previously accessed in the ways described just above and which were dependent on the interface you were using. Now, simply passing the mouse pointer over any table header or over any Edit button (round, green button with yellow arrowhead) generates a context menu that is specific to the situation. (The context menu from a display header does not include the option to Update/Delete since no single data row has been identified, for example.) The context menus will remain in view until or unless you click outside of the menu to close it, or until you click on an item in the menu. If a context menu shows an arrow pointing to the right, and if you pass the mouse pointer over that item, a cascading menu will appear to the side, showing additional options. In addition, if you click on the edit button for a data row, the update form for that row is presented.

Note that if your institution has been using modified versions of the HTML templates, it is our recommendation that your institution rename existing custom templates (to use as a reference/backup) and then create new custom templates based on the current Millennium standard templates, with your prior modifications re-applied. This technique will ensure consistent and appropriate display results, in light of the display changes. This is especially true for the Gift, Dues, and all associated templates (such as Credit Card, Quid Pro Quo, etc.), which have had major changes to accommodate the enhancement permitting greater flexibility in the handling of allocations.

If your institution has been using Customizer-defined modifications, the installation of this release will convert your saved definitions for use with 7.3. It will also install new standard default definitions.

Both

Online Constituent Directory

(Coming Soon)

A new, extensive, optional Millennium component allows you to construct the Online Constituent Directory Web site for your institution. A sample Web site is available, constructed using scripts, form tags, and smart tags. It allows you to use a combination of standard Millennium techniques such as the Customizer to define layouts, and appearance settings to control colors and fonts, and HTML programming principles to adapt the Web site for your institution's use.

The Online Constituent Directory module includes an online constituent directory, which draws selected information from your Millennium database for display. Constituents may submit new data, or data edits online . Such edits will be available for viewing online immediately, even though it is held in a pending table until your staff reviews the information and accepts it for incorporation into the standard Millennium database. Alternately, such edits may be incorporated without prior review, if that is your institutional preference.

Both constituents and non-constituents may make online donations via your Web site.

The eDirectory setup functions include a utility that will generate Log On Id's and Passwords which you may distribute to your constituents for their initial visit to the Web site. When they do so, they will be required to change the password, choose a prompting question, and a personal response, which the system will subsequently use to authenticate any user who has forgotten their password.

Both/Both

Favorites/
Bookmarks

The set of functions that were previously accessed via the Bookmark item in the Windows interface has been renamed to be known as Favorites. In the Explorer panel at the left, the Profiles item that was previously labeled Favorites is now labeled Bookmark. All of the prior functionality in that area remains as it existed previously - simply re-labeled.

In addition, this set of functions has now been activated for the Browser interface. This allows a user to easily return to the most recently used reports, or to easily access Profile data display for his or her own prospects or those constituents that he or she has 'bookmarked'.

Both

Default Home Page

The default home page now includes the Community Brands logo, rather than the graphical image. The version number and hyperlink to the Current Release Notes is shown as previously. This is the page that will be shown if the user has not customized his or her own Home Page settings via the new item, My Millennium.

Both

My Millennium

There is a new category of functions called My Millennium. This set of items includes several new functions, as well as some re-organized and re-named functions from earlier versions.

Setup allows you to choose elements to display on your personal home page, and to select a background, font type, size and colors for your use throughout Millennium. It also allows you to configure a personal Home Page for Millennium, choosing from elements such as Advisories, Tasks, Charts, Reports, and sets of links to Community Brands and Millennium Support, or other fundraising Web sites.

Advisories provides access for users of the Browser interface to view their own Advisories - a function of the Agent component of Millennium. (This function continues to be available to users of the Windows interface via the Agent item in the horizontal action toolbar.)

Agent provides access for users of the Browser interface to install or configure the Agent component of Millennium on their personal workstation. (This function continues to be available to users of the Windows interface via the Options, Agent item in the main Millennium menu bar.)

Assignment provides access for users of the Browser interface to create or view their own Assignments - a function of the Agent component of Millennium. (This function continues to be available to users of the Windows interface via the Agent item in the horizontal action toolbar.)

Charts & Graphs shows the elements that were previously shown in the Statistics section of the EIS World in the Browser interface.

Reports shows links to any report that you have run via the Millennium Reporter and saved as a 'Home Page Report' - a new Report Group designed for this purpose. It also has links to 'On Demand' reports which are comparable to the EIS reports from the Browser interface and the Interactive Reports section of the Reporting World in the Windows interface.

Tasks shows all of your Tasks (assuming that you are a constituent on the system) which do not have a Completed Date.

The items described above are available in My Millennium in both the Browser and Windows interfaces. In the Browser interface, it also includes items to access your Advisories, Agent options, and Assignments. (In the Windows interface, these functions continue to be available via the Agent item in the Action toolbar.)

With this new access to the 'On-Demand Reports', the EIS category is no longer shown in the Browser Explorer, and the Interactive Reports category is no longer shown in the Reporting World Explorer for the Windows interface.

Item #

Interface

Function

Description

E8.2.3/3154

Both

Address Linked to Employment

When an Address is linked to an Employment row and the Status of that Employment row is changed to 'No Longer at this Position' (Code = no), a pop-up message box will now ask if you want to unlink the Address. If you say Yes, the linkage will be removed but the Address will be retained just as it is. If you want to link it to a new Employment, you must do so by using the Link, Employment item in the context menu for the Address row and then inserting the new Employment row.

NA

Both

Address - Map It

If using the Customizer-defined displays (rather than the HTML templates) Addresses shown in Long Display will now include a hyperlink labeled, Map It. When you click on that link, a new browser will automatically open to the MapQuest Web site, and the data from that Address will automatically be used as the map search data. If found, the map will be displayed showing that location.

E8.1.10

Both

Address - Non-USA

Previously, during the insert of an Address row, the District, Region, Territory, and Zone fields were automatically populated for USA Addresses based on the data in the ZIP Code lookup table, and that behavior is unchanged. With this release, non-USA countries will have the same functionality, but based on the chosen entry in the Countries lookup table, instead of ZIP Code. To make this change, the Countries lookup table has had those fields added.

E9.4.2.1

Both

Address - Update/Archive

When an Address is updated and automatically archived, the Stop date on the archived Address is now set to the Start Date of the new one, whether you use the default Start date of the current date, or whether you manually enter a different date as an override.

E9.4.2.10

Both

Attachments

A field has been added to the Attachments table allowing you to enter a 255 character description with the other Attachment information.

3386

Both

Automated Membership Process

The Automated Membership Process applet now includes an appropriate tab order for the active text boxes shown in the form.

3197

Both

Basic Data Delete

An option has been added allowing each institution to determine whether or not to allow users to perform a super delete (deleting the Basic Data row which causes the deletion of all data rows belonging to the constituent ) when that data includes Gifts or Dues. This option is set on the System Info page in the Tools World.

3273

Both

Basic Data Birthdate

Three fields have been added to the Basic Data table for the individual pieces of the birthdate. This provides a site the option to edit the standard display and maintenance definitions for Individuals and use either the standard field, corebirthd (a single, datetime/date field) as before, or use some or all of the new standard, free-text fields: corebirthyr, corebirthmn, and corebirthdy.

The installation process for Release 7.3 does not automatically populate the new fields. In regular Millennium use,the use of one option does not automatically populate the unused column(s) for the other option.

E9.4.1.7

Both

Basic Data Match Through Id

The Basic Data functionality associated with the field coremtchid has been activated.

When a Corporation or Foundation (A) uses another entity (B) to deliver and administer its matching gift funds, you may now maintain that link between the two using the Match Through (coremtchid) field. Both A and B must be constituents. The link is established via the Link item in the context menu for A's Basic Data row. When B is identified, the system automatically copies the matching information from B's Basic Data into the corresponding fields in A's Basic Data.

If your institution uses the optional Millennium component, CorrectGM, and if B has a link to an entity (C) in the Correct GM database, that same linkage will be established for A. When updates to that database are downloaded and imported (both actions are regular functions of CorrectGM), C's updated matching information will be also be updated for B and A.

During gift processing, IF you have your user option set to suggest matching transactions, and if one is to be suggested on the basis of an Employment row where A is the Employer, the system will automatically show B as the source of the payment for the transaction and calculate the match amount based on the data in A's Basic Data.

E8.1.3

Both

Basic Data Title Bar

The length of the Title Bar field has been increased from 30 to 60 characters.

3300

Both

Countries

Columns have been added to the Countries lookup table in order to facilitate the automatic entry of a District, Region, Territory, and Zone, when the Country chosen for an Address is a non-USA country. (If it is USA, that information is automatically taken from the ZIP Code lookup table.)

E8.1.13

Both

Data Entry using Lookup Tables

Data Insert forms have been modified so that all list boxes for lookup table-driven fields are initially presented showing the designation, '-CHOOSE-'. This acts as a placeholder and reminder that an active entry from the lookup table MUST be chosen for that field. If you do not select an entry from the lookup table (you leave the word CHOOSE in place), and if the lookup table includes an entry that uses a 'blank' (not the word blank, but a space) as its code and value, and if that blank entry is flagged as active for data entry, then the system will automatically select the blank entry for that data field when the data row is inserted or edited. If your institution wants to make it a policy that a meaningful choice MUST be made for a data field then there should be no blank entry in the lookup table, or if it is present it should be flagged as inactive.

However, please note that when any lookup is set to inactive (including blank), it can cannot be used when inserting new data or changing data. But, if an inactive code exists in a record and the record is edited, the inactive value is allowed. For example, if a site enters a Campaign "New Building Fund", enters gifts using this campaign, then marks it inactive because the campaign is no longer active (the building is built), a user may want to go back and add a comment to the gift. If they were forced to change the campaign, the data would then be incorrect.

In light of this change, you should ensure that you do not happen to already have entries in any of the lookup tables that use 'choose' as their Code.

NA

Both

Easy Ask

The Easy Ask dictionary has been enhanced to include the Correspondence and Gifts tables.

3106

Browser

Easy Ask - Browser

Access to the English-language query tool, Easy Ask, has now been incorporated into the Browser interface of Millennium, when using Internet Explorer. This allows those users to perform constituent searches by typing in text questions or instructions such as, 'List corporations in Denver, Colorado.' The system uses an internal dictionary to translate the text into an SQL query statement, used to perform the search. The search results may be viewed, saved, printed, or re-accessed at a later time. Note that you may not use this feature when logged onto Millennium using the browser on the IIS computer itself.

3118

Both

Easy Ask - Printing Results

It is now possible to print the Search Results that are generated from an Easy Ask question. The new item on the Easy Ask action toolbar, File leads to a pull-down menu which includes the item Print and Clear. (Previously, Clear was shown in the first position on that toolbar.) When you click on Print, you will be given a Print dialog screen where you can specify printer and other options such as portrait or landscape. When printed, the page includes the question that was asked, followed by the data that was displayed in the Results display area.

E8.1.15

Both

Employee Listing

A new on-demand report (accessed via the yellow Report button in the upper right corner of the Profiles display) has been added for Corporation or Foundation types of constituents. The Employee Listing shows the names and positions for all of the employer/employee Relations where the constituent whose data is being shown is the employer.

NA

Both

Employer Name

When a constituent employer is identified in an Employment row and the system populates the jobsconame field, it will now do so using the formatted name from the constituent employer's Name row.

3153

E8.1.4

Both

Employer Name

When performing an Employer Id search and no match is found, the message now says, 'No match on criteria; Re-Specify or Enter Non-Constituent Employer'. When you click on the hyperlink portion of the message (Enter Non-Constituent Employer) the Employment row is inserted using the name information from the search form as the non-constituent employer name.

Also, when performing a search in this situation, if name information is used (rather than an Id #) and a unique match is found, the system will now generate a Search Results display for the one name - allowing you to confirm the data before it is entered in the database.

E8.1.5

Both

Fast Gift Entry

A feature has been added to the Fast Gift or Dues Entry Mode, allowing you to choose between two behaviors. You may click on the Insert button to enter the transaction and have the Search form automatically presented for the next constituent search (just as this component behaved prior to this release). Now you also have the option of clicking the new Display button on the Fast Gift Entry form to have the transaction inserted and also displayed in detailed display mode. Below the display of that transaction is a Search button, which allows you to proceed to identify the next constituent for whom you want to create a transaction.

E9.4.1.8

Both

Gift Processing - Allocations

Previously, there were about ten data fields that were available for editing from allocation to allocation. With this release, that capability has been very significantly increased. There are now only sixteen of the data fields that are NOT available as allocation-specific data. All others (except for the system-generated fields which are never available for editing) may be included as allocation-specific data.

To accommodate this change, and in combination with the concurrent move to the HTML Template/Customizer display definitions, the Browser's Allocation Applet is no longer in use, and the Windows interface's expanding transaction insert form has been replaced. Now, both interfaces will use a static insert form for the creation of the primary allocation and the main portion of the transaction (the data that is common to all allocations). That form includes a check box indicating that you want to create additional allocations, and when it is activated, the system will automatically present an insert form for the allocation information. That form will contain a copy of the primary allocation's data, which you may edit as desired before inserting the secondary allocation.

In the display, each allocation will have its own Edit button and when you use it, you will be given that specific allocation data, only. If you delete or journal any of the secondary allocations, the amounts will automatically be added back into the primary allocation in order to preserve the total value of the transaction. You may then create a new or replacement allocation.

Pledge payments that are applied to a multiple-allocation pledge may be distributed using the Pledge Payment Allocation Applet, just as previously. For Windows users, the application is no longer in a 'pop-up' window, but is embedded in the display area.

As was the case previously, for joint, multiple allocation transactions, when you are inserting either the primary or secondary allocation data, the system will show the full amount of the transactions (the sum of amounts of each constituent's half of the transaction) and will then automatically split it between the joint constituents. During editing, the system will show the constituent's half of the full amount, just as displayed.

E9.4.1.1

Both

Gift Processing - Closed Batch

The system now allows for the editing of the following fields, even when the Batch Number or the Ledger Flag for the transaction is closed: Comment, Source, Classification 1, Classification 2, and all custom fields.

E3418

Both

Gift Processing - Editing Joint Gifts

The system will now ensure that when edits are made to either 'side' of a joint transaction, the same edits will automatically be made to the other side as well. This applies to the following fields (Only the Gifts fields are listed, but the behavior applies to the corresponding Dues fields.):
giftrest, (and the associated fields: giftacctno, giftacctid, giftacctnt, giftacctgl, giftacctcf, giftacctdv, giftacctgp, giftacdprt, giftacctnm) giftsolic, giftcamp, giftcampyr, giftexrate, giftbatch, gifttender, giftanon, giftprocdt, gifteffdat, giftcurr, giftcomm, giftsource, giftchckno, giftaba, giftdepost, giftclass1, giftclass2, giftbnkact, giftbnkaty, giftdate1, giftdate2, giftdmny1, giftmny2, giftnum1, giftnum2, giftyesno, giftlook1, giftlook2, giftlook3, gifttext.

(Note that if a joint transaction is a pledge with an associated Payment Schedule, the system does not automatically adjust both sides of the Payment Schedule - you must do so manually.)

NA

Both

Gift Processing - Honor Marker

When inserting a joint gift on behalf of a third party, the gifthnrmkr field will be updated with a B for both sides of the joint transaction.

3168

Both

Gift Processing - Matching Gift Default

Each site may choose a Tender Type to use as the default Tender when creating a Matching Gift transaction. When a Matching transaction insert form is presented, that Tender will automatically be in place, though it may edited before the data row is inserted if desired. This site option is set by the system administrator on the System Info page in the Tools World.

M10110

Both

Gift Processing - Pledge Payment

When a Payment is applied to a conditional Pledge, you may now override the trigger-calculated Net Present Value amount at the time that the row is inserted.

NA

Windows

Gift Processing - Pledge Payment

In previous versions, Campaign Year and Solicitation fields were not part of the default payment form, but the parent record information for those fields flowed down to the child records automatically. Now, the Campaign Year and Solicitation fields were added to the default payment form.

Please note that if you plan to remove those items from the Customizer screen in order to retain the familiar form experienced in prior versions, the payment row is not updated with parent record giftcampyr or giftsolic values, it will be blank. This is the expected functionality; behavior was requested by user groups to be able to edit these fields in the payment rows, and did not want them to always automatically be populated from the parent record.

E9.4.1.4

Both

Gift Processing - Pledge Payment

When a Pledge Payment is being created, the form now includes the Campaign Year as one of the fields that can be edited as the payment is created. (It may differ from the Campaign Year of the Pledge.)

E8.1.1

Both

Gift Processing - On Behalf of Pledge Processing

A change has been made to the system behavior in the handling of pledge payments in the following circumstance. Constituent A makes a pledge and credits Constituent B. This results in a pledge for A and a pledge credit for B. Then, Constituent B makes a payment toward A's pledge. Previously, this resulted in a credit for A which was linked to A's pledge, a gift for B and a credit for B linked to B's pledge credit. Now, a payment for B will be linked to B's pledge credit and no credit will be created for B.

E8.2.6

Both

Giving Display - Match Credit

An improvement has been made to the information shown in the cross-reference link to a Match Credit that is linked to a Matching Pledge to which Payments have been applied. The reference now includes the amount of the Matching Payment.

E8.1.7

Both

Giving Display - Secondary Information

When a giving transaction has linked secondary information (Credit Card, Gift in Kind, Securities, or Quid Pro Quo data rows), and that transaction is jointly owned, the giving display of the secondary 'side' of the transaction will now display the secondary data row that is linked to the primary side of the transaction. To clarify which of the constituents actually owns the secondary data, it is shown below the cross-reference showing the name of the secondary constituent.

E3176

E3177

Both

Giving - Original Pledge Amount

New fields have been added to the Gifts and Dues tables (giftorigpl and duesorigpl) to track the original, total amount of all linked allocations that make up a pledge, prior to the application of any payments, journals, or write-offs.

The 'Pledged' amount in the display will be based on this new field and not on the giftalloc field as was previously the case. (The display will continue to calculate the Pledged amount for jointly owned pledges to show the full amount, rather than the constituent's share.)

NA

Both

Giving - Print Receipt

A Print Receipts option has been added to the context menu for giving transactions. When you click on that item in the menu, a new browser will open and a Receipts report based on that specific transaction will be displayed. From that display, you may print the Receipt.

E3171

E9.4.1.3

Both

Giving - Void and Write-off of Match Pledge

The notations on the hyperlink for Match Pledges or Match Potentials that have either been journaled or written off have been adjusted. For journals, on the original constituent's display, the hyperlink says 'voided by' and the corporation's display no longer says 'paid by' but shows the transaction type of match pledge (or potential) void and a ratio of 0.0000:1. For write-offs, the amount is adjusted to reflect the remaining balance (if any).

9.4.2.20

3149

Both

Joint/Linked Data Rows

You may now create one-to-one joint (linked) rows between spouses or other constituents in many additional tables, in a similar manner as you have previously created linked Addresses. To do so, you must create a row for one of the constituents and then use the appropriate item in the context menu for that row to create the linked row. (You may not link two existing data rows.) The context menu will include a cascading menu item, Link, which will include items such as Tracking to Spouse, and Tracking (for the Tracking table.) These will be enabled or disabled in accordance with the conditions - whether a link already exists, whether the first constituent has a spousal relationship (sp, spnm, lp, lpnm), whether the primary row has a link (secondary rows such as Attributes linked to Tracking, can only be linked if the primary rows are already linked.)

When edits or deletions are performed on a linked row, the same changes will be made on the joint row. You may unlink the rows via the context menu.

This functionality has been added for the following tables:
Actions (as a stand alone row, or an Action linked to Proposal, or Planned Gift)
Attributes (as a stand alone row, or an Attribute linked to Tracking)
Comments
Demographics
Financial
Planned Gifts
Proposals
Ratings
Relations (as a stand alone row, or a Relation linked to Proposal, Planned Gifts, or Tracking)
Tracking

E3448

Both

Marital Status for Surviving Spouse

When a constituent has a non-constituent Spousal Relationship that is changed to a Surviving Spouse/Deceased Spouse Relationship (the constituent is the surviving spouse), the Marital Status in the Basic Data of the constituent is automatically changed to Surviving Spouse (ss).

NA

Both

Membership tables

The Membership tables, Membership, Benefits, Benefit Level, Subscription, Subscription Level, and Membership Cards now include the standard set of custom fields. As in other data tables, this variety of data type fields may be used in any way that your institution finds useful. These fields include two dates, two money, two numeric, one flag, three lookup-driven, and one comment field. Your system administrator may add any of these fields to your display and maintenance definitions.

NA

Both

Membership Expiration Date

Two new options have been added to the current five options for the calculation of the default Membership Expiration Date in the Automated Membership Process. The new options are:

RB - Rolling, End of Month Backward. This option considers the Renewal Setup Day and if the Effective Date (and therefore the membrnewdt) is before the Setup, the Expiration Date rolls to the end of the prior month.

RW - Rolling, End of Month Forward. This option considers the Renewal Setup Day and if the Effective Date (and therefore the membrnewdt) is after the Setup, the Expiration Date rolls to the end of the following month.

The calculations for these new options are called into for new, rejoin, rejoin upgrade or rejoin downgrade Memberships.

NA

Both

Mini Display

As part of the re-structuring of the control of the display in both the Browser and Windows interfaces as described above, you may now display data in Long, Short, or Mini display mode. The new, standard, Mini mode will generally consist of one or two display lines per data row.

Your site may modify the definition of the Mini display mode using the Customizer or the new set of HTML standard templates for that purpose, in accordance with the display option in use at your institution. The same Mini display definition will be available to all users at your institution and all Profiles tables, excluding Gifts and Dues, just as the Long and Short display modes have been used in the past.

Therefore, a new radio button is available in the Customizer (accessible by the system administrator) for the Mini display mode. And a new set of HTML templates are included in the installation. In general, these templates are named, xxxxx_mini.mit, where xxxxx is the table name or prefix.

A new set of standard HTML templates have been added to control a very abbreviated display of the data tables in the Profiles World, for those institutions which choose to use HTML templates for their display definitions. As with the other HTML display templates, these may be edited by your site, in accordance with procedures for doing so. See HTML Templates.

NA

Both

Print Profiles

A function has been added to the Profiles display which allows you to print the set of data that is currently displayed for a constituent. A new button labeled Print has been added to the display header, to the right of the Spouse and Reports buttons. When you click this button, a new instance of the browser will open, showing only the contents of the display area of Millennium. Your session of Millennium will remain open and unaffected below that browser. At the same time that the new browser opens, a standard Print dialog box is shown with the printers and other options that are available for that workstation. You may select any of the available options and execute the print command. When the print dialog clears the screen, you may close the new browser and continue working in Millennium.

3191

9.4.2.16

Both

Relation Tree

The hyperbolic Relationship Tree display now includes the ability for individual users to restrict the tree display to the Relationship Groups that they specify, rather than all Groups.

Also, each institution may (if desired) place a limit on the number of degrees of separation that it's users may specify for the Relation Tree displays. Once this site option is set by the system administrator on the System Info page in the Tools World, the pull-down list for Degree on the display of the tree will only show those which are available at your institution.

3273

Both

Relationship Birthdate

Three fields have been added to the Relationship table for the individual pieces of the birthdate. This allows a site to edit the standard display and maintenance definitions for Individuals and replace the relbirthdt (a single, datetime/date field) with some or all three of the new fields. The new, free-text fields for this feature are relbirthyr, relbirthmn, and relbirthdy.

E8.2.9

Both

Relationships for Constituents

The standard display definitions for constituents no longer include the fields which track the non-constituent information: Gender, Child, and Birthdate.

3473

Both

Relationships for Disbanded/Deceased Constituents

Functionality has been added so that when a corporation or other organization is disbanded or when an individual is deceased (by the creation of a Death data row), all Relationships where the disbanded/deceased constituent is the Employer, are automatically updated from Employer/Employee to Former Employer/Former Employee.

E9.4.2.21

Browser

(IE only)

Search

When using the Internet Explorer and the Browser interface and a constituent search has resulted in the display of a set of Search Results, the display will also include the hyperlink, refine the query. When you execute that link, you will be returned to the search form, including all of the data that you used to produce the Search Results. (This functionality was already available in Windows. Netscape limitations do not allow for the use of this function with that browser.)

E9.4.2.1.5

Both

Search

The standard constituent Search form now includes a text box for the City from an Address row. This data is case sensitive, and you may enter partial data. For example, if you enter 'Williams', the system will return Addresses with a city of Williams, Williamsburg, Williamsport, etc.

E8.2.10

Both

Search - Data Entry

When the constituent Search form is used for data entry purposes (rather than for data display) and Name information uniquely identifies an existing constituent, the Search Results form is produced, showing that constituent information, allowing you to confirm the identity before it is inserted in the data. This applies to situations such as creating Relationships, Solicitors, a Gift Given By another constituent, etc.)

A constituent search that is conducted in order to display a profile and which identifies a unique match will continue to show the profile automatically - without displaying the Search Results page.

E8.2.1

Both

Summaries

Additional fields have been added to the Summaries table for custom use. The Summaries utility has also been enhanced to allow you to include these fields in the definition of numeric Summaries (only).

3184

Both

System-generated Names

When the system is constructing a combined name and the Suffix begins with 'Esq', the Suffix will be suppressed in the combined name.

NA

Both

Title Bar

The Title Bar display of a constituent's name will now automatically include a star symbol when the current constituent has been bookmarked by the current UserId.

NA

Browser

User Options, Data Entry

An option has been added allowing each user to set his or her preference regarding lookup table pull-down list boxes in insert and update forms. You may choose to have the lists display the Values (only) and be ordered by them, or to have the lists display the Codes followed by the Values and be ordered by the Codes. In the Profiles World, this applies to data maintenance forms, only. The display will always show the Values (unless your institution uses the Customizer for display definitions, and specifically defines a display to show the Code (only) for a particular lookup-driven field.)

This setting also affects the display of lookup table entries when constructing reporting criteria in the Millennium Reporter.

This option was already available via the Windows interface.

Issue #

Function

Database

Interface

Description

SS20009

Actions Completed Date

SQL

Browser

If an Action had a Completed Date and a new Task (without a Completed Date) is added to the Action, the Action's Completed Date was not reset (to blank).

M10168

Address linked to Employment

Both

Both

When an Employment was linked to an Address and the Address was deleted, the hyperlink on the display of the Employment row was not removed.

M10174

Address

Both

Both

When a Company's Address was linked to more than one individual, the first individual was showing two hyperlinks, one for the company and one for the second individual.

6301

Allocation Maintenance

Both

Browser

When a transaction is in a closed batch, the allocation maintenance Edit button was disabled.

M10121

Basic Data - Known Subsidiaries

Oracle

Both

When a Parent Corporation was added to a Basic Data row for a constituent, the Known Subsidiaries field was not being updated correctly in the Basic Data for the constituent parent corporation.

M10071

Benefits

SQL

Both

When attempting to add a Benefit to an existing Benefit Level row, an SQL insert error occurred.

M10224

Benefits

Oracle

Browser

When linking a Benefit Level and filling in the number field, then linking a Benefit you would see that the number field displays with a capital letter to the number.

6301

Closed Batch

Both

Browser

If a multi-allocation transaction's batch was closed, the allocation edit button was disabled, making it impossible to journal individual allocations.

6321

Comments

Both

Windows

The Comment on a journaled match pledge was not displaying.

M10009

Comments on Gifts

Both

Browser

The Edit form for a Pledge Payment, Write-off or Credit transaction did not include the Comment.

M10184

Correspondence

Both

Browser

When inserting a Correspondence row the display screen was not taking you to the row you just inserted.

SS20017

Correspondence

Both

Browser

If the Correspondence display template was edited to include the custom fields for Custom Lookup1 or Custom Lookup2, errors occurred on data entry.

M10051

Define Display

Both

Windows

If the Define Display dialog screen was closed using the Windows 'X' control in the upper right corner, an 'Invalid Procedure call' error resulted.

M10073

Demo/Finance

Both

Windows

The data indicator 'light' did not respond correctly if there was data in the Financial table but not in the Demographic table.

M10140

Dues Data Entry

Both

Browser

When a joint Dues Pledge had a payment applied and the system returned to the display of the Dues transaction, the notation, 'Lookup not found' displayed (inappropriately).

M10194

Dues Data Entry

Both

Browser

When inserting a Dues transaction then using the Journal & Add Correction feature twice, the original transaction disappears on the display.

SS20032

Dues Data Entry

Oracle

Browser

When inserting a Dues Transaction and changing the Given By to another constituent, the automated membership applet did not appear and displayed an error.

M10003

Employment

Both

Windows

When a constituent Employer has a name containing numbers and when you attempted to link an Employment to one of the Employee's Address rows, an error resulted.

M10093

Employment Company Name

Both

Both

The system stored the Company Name from an Employment row using a semi-colon and no space (Best Software;Inc.) To accommodate Easy Ask, it now stores the name with a comma and space (Best Software, Inc.)

M10147

Employment Industry

SQL

Both

If an existing Employment row was edited to a different constituent employer, the Industry field in the Employment row was not automatically edited to show the Industry from the new employer's Basic Data.

SS20000

Employment Source

Both

Browser

When an Employment Status was edited to 'No longer at this position', the Source field was blanked out.

SS20018

Filtering

Both

Both

When a user was in a security group with no lookup access, that user was prevented from creating Filters or Sorts, or from creating reports in the Millennium Reporter using lookup tables.

SS20024

Filtering

Both

Browser

When Defining a Filter on any table, and selecting only records for a specific User Id, the User Id was not enclosed in quotes which gave an error after the filter had been saved and applied.

M10130

Financial

Both

Browser

When the custom money fields for the Financial table were added to the display template, they displayed 'Invalid Field' rather than the data for the fields.

M10065

Gift Total

SQL

Both

When a Payment against a joint pledge was either deleted or journaled, the total amount for the transaction did not reduce accordingly.

6332

Gift Match Totals

Both

Both

The Match Total fields in giving transactions had inconsistent data, in particular when a matching transaction was linked to a pledge payment. The conversion to Release 7.3 includes a re-calculation to the data in the mptotl, mdtotl, and mctotl fields

SS20043

Gift Processing

Both

Windows

When inserting a Credit transaction with a Tender of GIK, the system prompted for the creation of a Gift in Kind row. Linked Tender rows (Credit Card, Gift in Kind, Securities) are not available for Credit transactions.

M10151

Gift Void

Both

Windows

When a Gift Void (gv) was shown in a single line display, and you attempted to edit the transaction, Run-time errors resulted.

M10009

Giving Comment

Both

Browser

The update form for Pledge payments, Write-offs, or Credits did not include a text box containing the existing Comment.

M10078

Giving Default Definition

Both

Windows

When defining a Gift or Dues Default, if you attempted to make the amount greater than 999, an error message was generated and the amount could not be saved.

M10212

Giving Default Definition

Both

Browser

When defining a Gift or Dues Default, if you attempted to check the box for Honor/Memory Non-Constituent, then inserted via Default the box was no longer checked.

M10059

Giving Detail

Both

Windows

The header for the Giving Detail display for a limited set of constituents showed as Event Correspondence.

M10041

Giving Detail

Both

Browser

When inserting a transaction with a comment that includes an & the comment that is inserted shows an umlaut instead of the &.

M10173

Giving Detail

Both

Browser

When inserting a pledge transaction and immediately logging out and then back in and going straight to that last transaction and trying to Add Joint Transaction the joint row was not inserted.

M10044 M10234

M10251

Giving Detail

Both

Both

When inserting a joint pledge transaction with either a single or multiple allocation, the original amount would split correctly but if a pledge payment was made, the amount was off by a penny.

Also, the same happened when using the Journal & Add Correction feature.

SS20035

Giving Display

Oracle

Both

When a Solicitor was added to a transaction, the display showed the correct Solicitor name, but instead of showing the correct Id# for the Solicitor, it showed the Id# of the donor.

SS20036

Giving Display

SQL

Both

When a Solicitor was added to a transaction given by someone else, the link showed twice on the given by record.

M10233

Giving Display

SQL

Both

After inserting any transaction type the display does not take you to the transaction you just entered.

M10180

Giving with Multiple Allocations

SQL

Windows

Browser

Inserting a gift transaction with split allocation and post match, then selecting the edit menu of the matching constituent and selecting post payment the screen hangs and not insert the payment.

Inserting a gift transaction with split allocation and post match, then selecting the edit menu of the matching constituent and selecting post payment the allocation maintenance screen does not display it just inserts the payment with a total of $0.00 and a NPV of $999,999,99999999.99.

M10064

Giftjntid

SQL

Both

When a joint pledge is paid down by a third party (creating joint credit transactions) the giftjntid field in the first constituent's credit transaction was not being populated with the ID of the joint constituent.

M10081

Giftamount

SQL

Both

The giftamount field on a Match Credit was not being reduced when payments were made against the Match Pledge to which it was linked. The conversion to 7.3 will check existing data and where the giftamount is greater than the gifttpledg field, it will set the giftamount equal to the gifttpledg field.

M10111
 

M10141

SS20045

Giftamtplg

Both

Both

The giftamtplg was not filled in for Match Credit transactions.

Also, if the second allocation of a multi-allocation pledge was journaled and re-entered, the giftamtplg was not re-calculated correctly.

When entering a joint pledge transaction, the original constituent was only getting half the amount in the giftamtplg field and not the full amount.

M10133

Gifttpledg

SQL

Both

When a write off was applied to one allocation of a multi-allocation, joint pledge, the system did not correctly re-calculate the gifttpledg field.

M10198

Giving Trees

Browser

Oracle

If a Giving Tree was defined to use the Account Number as a node, and if the Account Number included a hyphen, the information was not grouped correctly.

M10199

Giving Trees

Browser

Both

When the Giving Tree Options were set to include or exclude Pledges, Bequests were not handled correctly.

M10007

Giving Trends

Both

Both

When selecting the Giving Trends Options and changing the beginning month of Fiscal Year to July from January, the Consecutive Years of Giving displayed 1 regardless of how many years of giving were inserted.

M10037

Giving Trends

Browser

Both

The calculations for Giving Trends did not appropriately include Bequests.

M10064

Joint Pledge Payment on Behalf of

Both

Both

When a Payment was created toward a joint Pledge, and that Payment was made by a third party, the giftjntid field on the credit transaction that was created for the original Pledge owner was not filled in. It should contain the Id of the joint constituent. That constituent's credit transaction was created correctly.

M10190/1

M10177

SS20028

Journal and Correction

Windows/

Browser

Both

When two or more journal and corrections were performed on the same gift transaction, the display 'lost track' of the original giving transaction. It was still present in the data but missing from the display (Windows). If there were three or more journal and corrections, a 'Page not found' error resulted (Browser).

Also, when a journal and correction was performed on a pledge payment and the correcting payment was an overpayment of the original pledge, the Total amount in the display did not reflect the overpayment amount.

M10068

Letters

Windows

Both

When a document template for the Letters function was edited on the local machine and then re-accessed via Millennium, the edits had not been preserved.

M10156

Match Pledge

Browser

SQL

When a Match Pledge was created as the original donor's transaction was created, and a Credit transaction for another was added after the fact, a Match Credit was not generated for the Matching Pledge constituent.

M10114

Match Pledge

Both

Both

The transaction total was not calculated correctly in the following situation: A pledge is made and a payment applied to it. A match pledge was linked to the payment and when the matching pledge payment was made, it was also applied as credit for the original donor's pledge.

M10027

Match Pledge Payment

Both

Windows

When a Match Pledge Payment was also credited against the original donor's Pledge, the internal field, giftmrcvd was not being populated with 'M' on original donor's Credit transaction.

SS20027

Match Pledge Payment

Browser

SQL

When a Match Pledge was overpaid, the amounts on the original donor's transaction and the Match Pledge were adjusted correctly, but if there were linked Credit transactions, their amounts were not adjusted.

M10055

Membership Processing

Both

Windows

When using the Automated Membership Process, if a Membership Type (from the lookup table) had a value of more than 44 characters, the applet would generate Type Mismatch errors.

M10058 SS20016

Membership Processing

Both

Browser

Problems occurred with the display of the Automated Membership Process for the Membership Benefits, when there were more than twenty Benefits associated with a particular Membership Type.

M10182

Membership Processing

Both

Browser

When the Automated Membership Process attempted to calculate Expiration Dates based on a prior Expiration Date of Feb 29, 2004 (a correct leap year date), an error occurred.

M10245

Membership Processing

Both

Browser

When the Dues transaction for a Membership consisted of multiple allocations, and when the Automated Membership Process based on the first allocation was Cancelled, the process did not continue with the subsequent allocations.

M10210

Membership Override

Both

Browser

When using the Automated Membership Process to override the Best Fit system choice of a Membership Type, the system did not accept the override data but instead created the Best Fit type.

M10228

Name Deceased Flag

Both

Both

When a Name row was added to a constituent who already owned a Death data row, the flag on the new Name row indicating that the constituent is deceased or disbanded was not automatically set.

SS20007

Names

Oracle

Both

When a Name was inserted without any Name information (Title, First, Middle, Last were blank) and then the row was subsequently edited to enter data, the namesmashd field was not populated.

M10181

Payment Schedule

SQL

Both

When a Matching Pledge transaction was created, the system did not create a row in the Payments table schedule in all situations. It now does so for all Match Pledge (mp) transactions.

M10101

Pledge Credit Transactions

SQL

Both

The internal field giftamtplg was not being populated for Pledge credit transactions.

M10192

Pledge Payments Journal and Correct

SQL

Both

When a Journal and Correct was performed on a Pledge Payment that had overpaid the original Pledge, and then the correcting payment was also journaled and corrected, the Total amount shown on the transaction was not correct.

Also, when the second allocation of Pledge is journaled and corrected for the same amount, the internal data field, giftamtplg was not calculated correctly.

M10231

Pledge Payment on Behalf of

Both

Both

If the Given By name on the Pledge Payment insert form was changed to another constituent (creating an 'On Behalf of' transaction), an Millennium Gift Control error could result.

SS20042

Pledge Payment on Behalf of

Oracle

Both

If the Given By name on the Pledge Payment insert form was changed to another constituent (creating an 'On Behalf of' transaction), an empty, linked Correspondence row could be created.

M10222

Pledge Transactions

Both

Both

The displayed Total for a transaction was incorrect in the following situation. A Pledge had a Matching Pledge and then a Matching Pledge Payment was posted using the option, 'Also Credit as Payment on Donor's Pledge.' Then the Credit that was created for the original Donor was deleted.

M10123

Profile Reports

SQL

Browser

When executing the on-demand Profile Reports, the timing of the execution sometimes resulted in an HTTP 500 error. This situation would self-correct by waiting for 30 seconds.

6230

Profile Reports

Both

Both

If a constituent had no Name row of the Type 'Preferred', that constituent's data did not appear in the report. It now does, using the first found Name Type for the constituent.

M10200

Proposal Action Tasks

Oracle

Both

When deleting a Proposal which had an attached Action, and a Task linked to that Action, the system deleted the Proposal and linked Action, but did not delete linked Tasks.

SS20034

Prospect

Both

Browser

When linking a gift to a planned giving transaction the plangflag is set to 'Y' but was not being reset to 'N' when the linked gift was deleted.

M10001

Prospect Tree

Both

Browser

The Prospect Tree contained an 'Options' button (inappropriately).

M10024

Quid on Closed Batch

Oracle

Both

The database did not permit you to add a Quid to a transaction in a closed batch.

M10000/6333

Quid Pro Quo

Both

Windows

When a Quid Pro Quo was linked to a gift given on behalf of another, the Quid was linked to the Credit, rather than the Gift transaction.

M10080

Quid Pro Quo

Both

Windows

With the user options set to use lookup table values rather than codes, when you attempted to edit the Quid item, the system did not preserve your edit.

SS20033

Relationship linked to Tracking

SQL

Windows

When viewing a row from the Relationship display, and that row is linked to a Tracking row, clicking the hyperlink generated an 'Invalid procedure call or argument' error.

M10074

SS20008

Relationships

SQL

Both

If the Start Date, Stop Date, or Birthdate was edited from null to a date, or from a date to null, the system did not update the Last Edit Date or Last Edit User fields. Changing from one date to another worked correctly.

Also, if the Comment on a Relationship was null, and then edited to contain text, the Last Edit Date and Last Edit User fields did not update.

M10197

Relation Tree

Oracle

Browser

When the Relation Tree attempted to display a relationship with a constituent with an extremely long name, the display was not created correctly.

M10146

Search

SQL

Browser

Following a constituent search that found no matches, the next search that should have identified a constituent instead gives an error message, 'Unable to read temporary user file.'

M10189

Search

Both

Windows

After running the MergeID utility then deleting that Corebio record for the constituent you just merged, hitting Next Search would bring up the screen from the merged constituent showing No Name Found in the title bar.

M10053

Search Hot Keys

Both

Windows

In the constituent Search dialog screen, if the focus had advanced past the Name/ID text box, the Hot Key combination for the Name/Id (ALT+N) did not move the cursor back to that position, for some workstations.

SS20013

Search, Load Results

SQL

Browser

When saved Search Results were loaded and then the Last Search function was activated, the display area remained blank. Also, subsequent attempts to load saved results would generate duplicated data in the display in this situation.

M10132

Tasks Linked to Actions

SQL

Browser

When the display of Tasks linked to Actions was changed to Long, a 'Page cannot be displayed' error could result.

SS20039

Tracking - Custom Fields

SQL

Windows

When using the custom lookup 2 or 3 fields, the display showed the code rather than the value.

SS20045

Write-off

Oracle

Both

When entering a pledge transaction joint with spouse, the spouses side was showing the correct amount in the giftamtplg field, but the original constituent was only getting half the amount in the giftamtplg field and not the full amount.

M10152

M10133

Write-off of Multi-Allocation Pledges

Both

Browser

If the first allocation of a multi-allocation pledge has both a writeoff and an overpayment applied to it (such that the overall pledge balance amount appears to be zero) but the second allocation still has a balance unpaid, the option to writeoff the second allocation is disabled.

Also, if a writeoff is applied to a joint pledge with multiple allocations, the internal field, gifttpledg was not adjusted correctly.

Issue

Function

Description

E3094

Activity Items

If no Items have been associated with an Activity, a Guest's Attendance row for that Activity will not display the Activity Items display header below the Attendance row.

E3135

Attendance

A data field (attid) has been added to the Attendance table to track the Id number of the Attendee, if that Attendee is a constituent. If the Attendee is a non-constituent, the field will be blank. This allows you to use the Attendance table when constructing criteria for Profiles reports.

E3090

Attendance data entry

When entering seating information on a Guest's Attendance data maintenance form, the system checks to verify that the information is not a duplicate and presents an error message if it is. That message page now includes a Back button so that you can return to the maintenance form and preserve the data that you had entered. You must then edit the seating information to avoid the conflict.

E3129

Default Data Entry

It is now possible to create and use default definitions for data entry in the Events World. In situations where the Search Results page included a link such as 'To create a new Event, click here.', the system now includes a similar link allowing you to create the new Event using defaults.

In the rolling Registration process, the Event Guest form will follow the behavior of Registration row. If you use the default for Registration and check the Create Guest row checkbox, the default will be presented for the Guest insert form as well.

For data that is entered after the initial Registration process, the typical data entry procedures are available, using the Insert via default item in the context menus.

Defaults are not available for the Audio Video Needs, Transportation, Special Needs, Tourney, or Lodging data.

NA

Confirm on Delete

Insert/Update/Delete

The Events tables now respond to your setting regarding 'Confirm on Delete.'

Also, the Insert, Update and Delete buttons are enabled and disabled in accordance with your security permissions for the Events data tables.

E3092

Editing Registration

When the maintenance form for an existing Registration row is accessed, if the Registrant already has a linked Guest row, the Create Guest Row for this Registrant checkbox will be disabled. If there is no such linked Guest row, the checkbox will be enabled and will default to checked.

NA

File

As part of the re-structuring of the display and maintenance screens, the File item has been removed from the action toolbar for Events. Most of the Event reports that were accessed via that item are now accessible from within the display.

E9.4.3.2

On-demand Reports

Several areas of Events include reports that execute 'on-demand, in contrast to the reports that are executed using the Millennium Reporter and its reporting Queue. The formatted results of executing any of these on-demand reports now display in a new instance of the browser, regardless of which interface you are using - Browser or Windows. This applies to the Registration Listing, Registrants with Guests, Attendance Listing, Event Correspondence, and Activity Correspondence.

E3132

Registrant Header

The header for the display of any of any of an Event Registrant's data now includes the constituent Id # along with the name, preferred year, and constituent type.

E3089

Registration

As you enter a new Registrant for an Event, the system will check to verify that the Registrant is not already the Guest of a different Registrant for the same Event. Likewise, as you enter Event Guest information, the system will verify that the Guest is not already a Registrant for the same Event.

Windows

Registration Process

Prior to this release, the Windows and Browser versions of the Registration process, though totally comparable in function, were controlled by separate behind-the-scenes software code. The Browser was dependent on JAVA applets, while Windows used OLE Control Extension (ocx) files. In connection with the general changes to the Data Display and Maintenance screens that are part of this release, the Registration process for Windows interface users now uses the same applet that was previously used only by Browser.

Issue #

Function

Database

Interface

Description

SS20044

Attendance List by Activity

SQL

Browser

The Attendance List by Activity report did not display the names of a Registrant's Guests if those Guests were entered via the Windows interface.

1/21/2003

M10095

Scrolling the Events display

SQL

Windows

When Event Guest was on long display and you scrolled such that the header correctly changed to Attendance, scrolling back up did not refresh the header to Event Guests.

6/19/2003

M10218

Deleting a Registrant

SQL

Both

When a Registration row was deleted, the Events fields Total Guests (evnttguest) and Total Attended (evnttattnd) were not updated accordingly.

M10015

Activity Items

Both

Windows

During the Registration process, the system prompted for the creation of Activity Items but the data was not saved.

M10035

Attendance

Both

Windows

When adding an Attendance row to an existing Event Guest via the Attendance header context menu, the list of available Activities did not reflect any existing Attendance rows for that Guest.

M10095

Event Display

Both

Browser

When the Event Registration and linked data was displayed and the display was scrolled so that the different table headers passed in or out of view, the display did not always refresh appropriately to show the correct table name.

SS20023

Event Income

Both

Windows

When entering Event Guest information and attempting to enter a Fee row when the Guest was only attending Activities that had no fee, the insert form defaulted to include 'stray' or mis-aligned data.

M10033

Event Guest

Both

Windows

When entering Event Guest information for a constituent, the system automatically pulls the constituent's Preferred Address info, but it was not including the Country information in that default behavior.

M10227

Event Log

Both

Windows

The data indicator for the Event Log only reflected the presence or absence of data in Event Correspondence.

M10165

Linked data rows

Both

Browser, Netscape 4.76 only

For any linked row, such as Items, or Expenses, if one of these linked rows does not have any data, there is a missing </TABLE> tag in the HTML, and this version of Netscape does not display anything on the page, including the Insert button, so you could not insert any data.

M10084

Search

Both

Windows

If the Event Search window is closed using the Windows 'X' control in the upper right corner rather than the Cancel button on the form, runtime errors occur when you attempted to use the buttons on the subsequent form.

M10178

Search

Both

Windows

In particular combinations of Event Searches without entering search criteria, and using the Last Search function,the search results display failed to display a listing.

M10179

Seating Assignments

Both

Windows

Select an existing Event with Activities and going to Seating Assignments then inserting a new Event with Activities, and going to Seating Assignments you will see that it takes the numbers from the previous Event Activity selected.

M10042

Speaker

Both

Browser

When the display and update HTML templates were edited to include the custom lookup fields, spkrlook1, spkrlook2, or spkrlook3, the update forms did not display the appropriate data in the pull-down list for those fields.

SS20030

Speaker

Both

Both

When inserting a constituent Speaker, the system defaulted the name and address info into the Speaker insert form. If the operator edited the name information and then inserted the row, the name edits were not preserved in the resulting Speaker row.

M10201

Tourney Needs

Both

Both

When a Tee Time was inserted (such as 8:00), the data was inserted but displayed as 'Invalid Field'.

M10113

Transportation

Both

Browser

When entering a Departure Time and using the format, '8:00 a.m.' an SQL error resulted.

Item #

Function

Description

NA

Criteria Tables

The length of the criteria2 field in all criteria tables has been lengthened to 1000 characters. The conversion to 7.3 will make this change in all existing criteria tables and all new ones will be created with the lengthened field. This was done in part to accommodate the longer Prompting Text for Prompted Reply criteria statements. In addition, position 470-476 of the criteria2 fields have all been set to RESERV in anticipation of future enhancements. (This is a 'behind-the-scenes change that will not alter your use of the Millennium Reporter.)

E3509

Event Tables in Reporting

There are two types of reporting criteria that may be constructed in the Millennium Reporter - Profiles, and Events. Profiles reports select data rows based on the constituent id contained in each. Event reports select data rows based on the Event code, which is contained in each Event table. Some of the Event tables also contain constituent ids and some do not. Previously, most but not all of those which did were available for use in the construction of both Profiles and Events reports.

With this release, the Events table Attendance has had an Id field added and both it and the Speaker table have been added to the list of the Event tables which are also available for Profile report criteria. Previously, those tables were only available for the creation of Events report criteria but are now available to both.

NA

Express Reports

A major, new, standard component, Express Reports, has been added to the Reporting World, providing a means for any user to gain greater independence in running reports designed for his or her own needs. It offers a way to make use of the Millennium Reporter, without the need for extensive training in every aspect of report writing or report processing. When any set of report criteria is created and then run in the Millennium Reporter, it may be saved as an Express Report for any user - the current user or for someone else. This allows a reporting specialist to set up Express Reports for others, or for him or herself.

When that is done and the report has been executed, the owner can use the Express Reports area of the Reporting World to access either the published report results, or the new FasTab display of the report variables that were used the last time the report was run. This is a new, separate area of the Reporting World, intended to insulate a user from the sophistication of the Millennium Reporter, while still making use of its powerful functions. From the FasTab display in Express Reports, the owner can change prompt or parameter values,certain run options (if desired), and launch the run of the report.

One way in which Express Reports are distinguished from simply running the report criteria from the Millennium Reporter, is that the Express Reports module remembers the last set of variables that were used that last time that the report was run for the owner. This includes such things as the values chosen for prompted replies, the parameter choices, and certain run options, such as the choice of Queue. The system will use the same set of variables for that report again and again, until or unless the owner changes those variables.

To accommodate this functionality, a new system table, Express_Reports, was added to MILLREPORTS.

NA

Interactive Reports/My Millennium

In the Windows interface, the set of drill-down reports that were accessible via the Interactive Reports heading in the Reporting World Explorer have been moved. They are now accessible as On-Demand Reports in My Millennium. In the Browser interface, that heading is shown in the Explorer, and in the Windows interface it is accessible via the round Home button just above the Explorer. Therefore, the Interactive Reports item has been removed from the Reporting World Explorer. In addition, the Crystal report viewer is no longer in use, and therefore, the information in this set of reports is all still available, but in as flat report (rather than a drill-down.)

E3214

Print Criteria

When the Print Criteria function is activated with the run of a report, the output now includes the responses that were made to prompted reply criteria statements for the report.

NA

Prompted Replies

The length of the Prompting text for a <Prompted Reply> has been increased from 45 to 145 characters. To accommodate this change and to allow for future enhancements, the criteria2 field in all new and existing criteria has been lengthened to 1000 characters.

NA

Queue Management

The Queue Management display page periodically refreshes automatically, but a link has now been added to that page that also allows you to refresh the display on demand. The sentence reads, 'Click here to refresh this page.' It is shown below the links to the Queue History display.

Also, the link to clear the Queue History has been removed from the Queue Management display page for all users other than the system administrator.

Issue #

Function

Database

Interface

Description

M10072

Create Criteria

Both

Both

The system gave an error and failed to save a set of report criteria, if the criteria name began with a numeral.

SS20018

Create Criteria

Both

Both

When a user was in a security group with no lookup access, that user was prevented from creating Filters or Sorts, or from creating reports in the Millennium Reporter using lookup tables.

M10214

Criteria Display

Both

Windows

When using a screen resolution of 800x600, and displaying a lengthy set of criteria, if you scrolled the display of the criteria statements, the function buttons above were suppressed from the display.

M10203

Edit Criteria

Both

Both

When opening an existing report and going to File, Save As and changing the name you would get the error that you couldn't delete the criteria table.

M10163

Event Criteria

Both

Both

When an Event report using criteria based on the Event Action field eactactvty was run, an 'Invalid field name' error resulted.

M10159

Event Code Criteria

Both

Both

When running a report on events and using a prompted reply for the Event code (evntcd) so that you can get a list of events to choose from, if you selected an event with an event code of more than 6 characters, the tmp file carried only the first 6 characters of the evntcd so the report selected 0 records.

M10195

Gift Criteria

Both

Both

When constructing new criteria statements using the giving field, giftacdprt, the system did not provide a display of the entries in the Department lookup table.

M10066

New Criteria

Both

Windows

The tooltip description of the available report templates included extraneous information following the report description.

M10309

New Criteria

Both

Both

When running a report that includes the spouse relationship of "spnm" and "sp"and selecting the Remove Spouse and Combine when Either Selected options, it was combining the "sp" and dropping the "spnm" from the final list. This was correct functionality, the same has been added if you include spouse in the Totals section as well. The "spnm" will be removed from both sections.

This is the same for the relationship of "lpnm".

M10145

New Criteria, Basic Data

Both

Both

The corepublsh field name was not included in the list of Basic Data field names, which prevented its use in the construction of criteria statements.

SS20002

Print Criteria

Both

Both

When using the File, Print command, the Report Format name was not included in the report info.

M10153

Print Criteria

Both

Both

When using the Print Criteria option when running the report, the Remove Spousal Records information was not correct.

6303

Profile Report

Oracle

Both

When you attempted to run a profile report which had Event_Guest as the only line of selection criteria, and which had a Gift Total, the run of the report failed.

NA

Queue as a Service

Both

Both

When running the Queue as service, attempts to print a report run via that queue were not successful. A correction within runrepor.exe has eliminated this problem.

SS20047

Queue

Both

Both

When running multiple reports at once, all reports were running simultaneously with out regard to the priority they were set to.

M10171

Totals

SQL

Both

If a report containing a Gift Total was run by a user in a security group that had no select rights to the Dues table, an error was shown in the Queue's Report History. This was the case even though neither the criteria nor format referenced the Dues table.

Item #

Function

Descriptions

NA

Address Formula

The cityline formula in the standard report formats has been refined. It now includes the condition 'if addrcntry=USA' (rather than 'if country value = USA'), and it also checks for null or blank values. These changes are in effect for all standard formats which include a constituent's address.

NA

Biographical Reports

The Biographical Report library includes three new standard report templates and the associated formats. These are:

Mini-Biographical Export - This report generates an export file of biographical information.

Multiple Preferred Address Exception Report - This diagnostic report examines the Address table, looking for constituents who have multiple preferred Addresses and prepares a consolidated list, also showing the months in which the Addresses are valid.

Multiple Spouse Exception Report - This diagnostic report examines the Relationship table, looking for constituents who have multiple spousal types of Relationships and prepares a consolidated list.

NA

Optimized Reports

A subset of fourteen of the standard reporting templates have been updated and condensed into eight new standard templates, to accomplish several goals. This effort is part of a periodic review of our standard reports for usability, ease of editing, and relevance. In addition, these revisions serve to optimize the templates for use with the new Express Report functions, also introduced in this release. The optimized versions also serve as enhanced replacement templates for standard reporting use.

While the prior templates typically contained a skeleton of criteria statements (the minimum needed to allow the report to execute) and were constructed with the assumption that sites would add criteria statements to them, the new versions will include more selection criteria with many Prompted Reply objects, parameters and other options built in. You may still edit a report definition based on one of these new templates in any way you want, but the optimization lessens your need to do so.

In most cases, the enhanced templates will be named the same as the former versions which they are replacing. But in order to allow you to preserve the old standard formats that you may have been using up to this time, the new standard formats that will be installed with the templates have been named with 'MILL' at the end of the name.

For example, there is an enhanced template, Roster Single Line, which uses an enhanced format named Roster Single Line MILL.rpt) This means that the former versions of the formats will not be overwritten by the installation of Release 7.3, and you may continue to use the former versions of those formats (as if they were custom formats), if desired. The former versions will not be distributed in this or future releases.

It is planned that future releases will continue to include replacement, optimized report templates and formats.

The optimized templates and formats are:

Biographical - Mini-Biographical Report with Gift Totals
Biographical - Roster Single Line
Biographical - Single Line with Gift Totals
Comparison - Annual Comparison
(Replaces Annual Comparison by Account Name, Annual Comparison by Campaign, Annual Comparison by Constituent Type, Annual Comparison by Preferred Year, Annual Comparison by Solicitation, )
Financial - Giving Changes by Constituent
(Replaces LYBUNT by Constituent Type, and LYBUNT by Preferred Year)
Mailing - Label 3 Across 1 x 2.625
Prospect - Prospect Management List
(Replaces Prospect Management List by Manager and Prospect Management List by Prospect Name)
Prospect - Prospect Profile

Issue #

Library

Report Name

Database

Interface

Description

NA

Daily

Daily Report - Dues

SQL

Both

This release includes a new version of this standard format. The Matched By and Matched For subreports were incorrectly linked in the prior version.

SS20011

Pledge

Pledge Status by Donor

Both

Both

The first constituent's information was not correct in the report.

1426

Events

Registrants with Guests

Both

Both

Gave the Page not Found error.

This report has been removed from the software.

M10232

Mailing

Label Two Across, 1.33 x 4

Both

Both

The parameter option to sort alphabetically did not do so.

Issue

Function

Description

E1.4.4

Campaigns

Constituent Types

A field was added to each of these lookup tables, to support the ability of an institution to flag certain entries for use with the new, optional, Online Constituent Directory module of Millennium. In each table, the field is named table_ecom.

Also, a field named table_ack was added to the Campaigns lookup table to hold wording for an email message to be sent in acknowledgement of an online donation made via the new, optional, Online Constituent Directory module of Millennium. This allows you to customize the text of the messages based on the Campaign to which the donation was designated.

E8.1.10

Both

Countries Lookup Table

Columns were added to the Countries lookup table to support the new, automatic population of the District, Region, Territory, and Zone fields in the Address data table, when a non-USA Country is chosen. These fields are:
table_dist
table_regn
table_terr
table_zone

3106

Both

Customizer

Enhancements have been made to the Customizer.

The field lists now display the data field names rather than the aliases.

The Caption text box is now called Label.

An information button appears when you select a specialized data field or a calculated field. When you pass your mouse pointer over that button, a tooltip explains the special circumstance.

A new radio button is available for the option of defining the new, system-wide option of Mini display mode.

In previous versions, Campaign Year and Solicitation fields were not part of the default payment form, but the parent record information for those fields flowed down to the child records automatically. Now, the Campaign Year and Solicitation fields were added to the default payment form.

Both

Generic Import Utility

Some enhancements have been made to the Generic Import Utility.

The new item, Preference/Save Settings, on the menu bar for the utility allows you to save the current set of variables to be used as the defaults, the next time that you open the utility interface.

The new item, Preferences/Unattended Mode Settings, allows you to save an ODBC DSN, a user name and password, and a log file name, to be used as the utility is run in Unattended mode.

The unattended mode of running the utility is now enabled. You may launch the run of the utility in ways such as via a command prompt or third party scheduling software. When you do so, the utility will use the Preferences/Unattended Mode Settings, rather than prompt you for that information as it does when the import process is launched from the utility interface.

Both

Group Maintenance

A new check box has been added to the form used to create and edit the settings for database groups, allowing you to grant (or withhold) access to the tables used in the optional Millennium component, Online Constituent Directory. This appears on the form just below the list box for the options for Membership Processing. When this is checked, members of the group have full permissions to all of the pending data tables used in Online Constituent Directory. It does not affect the group's rights to the associated primary data tables.

Both

HTML Templates

To accom modate the new Mini display mode for those institutions who use the HTML templates to define the display area of the Profiles World, a set of 74 new, standard template files are included in the installation of Release 7.3. These may be modified as described in the topic, HTML Templates.

Windows

Lookup Table Maintenance

Lookup Table Maintenance in the Windows interface now uses the same 'behind-the-scenes' programming code as that used by the Browser interface. This primarily affects the way that you access a lookup table for maintenance functions. Previously, Windows interface users would select a set of lookup tables (Profiles, Membership, Events, Custom) and from the alphabetic header, click on the letter corresponding to the lookup table name. With this release, the display area will show an alphabetic index, and at the same time will show a scrolling list of the lookup tables. You may use the index to jump to that place in the list, or simply scroll to the desired table name.

The techniques for editing the individual rows in the lookup table will conform to the new techniques for performing the same kinds of tasks in the Profiles World.

NA

Membership Type

Two new options have been added to the standard list of Renewal Setup options within the Membership Type lookup table. They are:

RB - Rolling, End of Month Backward
RW - Rolling, End of Month, Forward.

See Memberships for the added functionality.

8.2.12

MergeId - Browser

When using this utility in the Browser interface and you identify constituents to be merged, the utility now displays the Name along with the Id Number, as you confirm your choices of constituents whose data is to be merged.

E8.2.1

Summaries Utility

In response to the addition of multiple custom fields to the Summaries data table, the Assign Summary Definition utility has been enhanced to allow you to assign any of those additional fields to a numeric Summary definition. This is done using a series of pop-up dialog windows, one for each type of custom field - money, dates, yes/no flags, comments, free text, and lookup table-driven. These pop-ups are accessible via the new Map Additional Summary Fields item in the menu bar of the Assign Summary Definitions utility.

NA

System Options

An option has been added to the Millennium System Settings section of the System Options page where an institution may specify which of two techniques it will use to control the Screen Layout of the display area of Millennium. The options are: Customizer, or Millennium Internet Templates. See Screen Layouts for more info.

3197/3168

System Info

A new category of settings has been added to the System Info page, called Millennium System Options. This category includes Assignment Frequency (relocated from the Millennium System Settings) and the new options for Screen Layouts, Super Delete, Matching Tender Default, and the Degrees of Separation.

7.1

System Info

The System Info page now includes a heading and display for the system Registration Information. This includes a site-specific Serial Number and Registration Number. The installation of Release 7.3 will include the entry of those numbers (which will be provided to the system administrator). This information will allow your system to function in accordance with your contractual agreement with Community Brands regarding the number and types of servers, the number and categories of users (regular, regular plus, executive), and number of constituents that your institution will use with Millennium. If the system detects that you are out of compliance, warning messages will be given to all users as they log in, prompting them to contact the system administrator to address the situation. A sufficient grace period will allow those users to continue to use Millennium as compliance is re-established. However, if the warnings are ignored beyond the initial grace period, the users will be prevented from creating new constituents, users, or servers. If the situation still persists, the system will ultimately be locked to any user other than the system administrator until compliance is re-established.

NA

System Users

The software now allows for as many as 2000 users per site instead of the previous limit of 100. This is an enhancement to the capability and potential of the software. It does not supplant your institution's contractual agreement with Community Brands regarding the number of Millennium users at your institution.

NA

User Security

The Security maintenance area of the Tools World has been updated to correspond to the new Appearance options available to each user.

In addition, it was previously the case that separate behind-the-scenes software controlled the Windows and Browser versions of the Security Maintenance display screens and maintenance forms. With this release, that control has been merged to a unified set of software. The appearance and access to the Group Maintenance and User Maintenance functions will be consistent with the new style of context menus used in the Profiles and Events Worlds which are accessed by passing the mouse pointer over the edit button to the left of a data row.

The maintenance applets which were previously used in the Browser interface to insert, edit, or delete Groups and Users and the applet for the View Generator are also now in use in the Windows interface. Now therefore, in the Windows interface when you click on Security in the Explorer you will immediately be shown the display of the Groups and Users (rather than a listing of the Security functions as was previously the case.) The View Generator is accessed via the context menu from the Group Maintenance header. The Windows interface's View Permission function is no longer available.

In response to these changes, the Help files on these topics have been merged into a single file for each topic rather than having Browser and Windows specific files.

NA

User Security,

Deleting a User

Previously, if you attempted to delete a UserId from the system when that user 'owned' saved criteria or worktables, the system prevented the deletion. Functionality has been added to this situation that will allow you to automatically transfer the ownership of such tables from the UserId that is to be deleted to another, existing UserId and continue with the deletion.

Issue #

Function

Database

Interface

Description

M10005

Add Attribute Utility

Both

Both

When the Add Attribute Utility is used in a replicated environment, the utility attempted to create the Attributes on the replicated database, rather than the primary database.

SS20022

Add Data Utilities

Both

Both

Several utilities which run through the Millennium Reporter used system information for the Create Userid, causing the usergroup to be null in the resulting data rows. They now use the User Id and usergroup of the person executing the utility for the data rows that were being created. This was the case for the Add Attribute, Add Correspondence, Add Quid Pro Quo, and Write Off utilities.

M10144

Chart of Accounts

SQL

Both

When the Value for an entry in the Chart of Accounts was edited, the chart_sort field (the sorting version of the value) was not automatically edited accordingly.

M10226

Chart of Accounts

SQL

Both

If the custom field chart_dte1 was added to the update HTML template, the system did not accept a null for that field during data entry and instead gave the field the value of Jan 1, 1990.

If the custom field chart_chck was added to the update HTML template, the system did not register edits made to the status of the field.

M10031

Customizer

Both

Windows

When a custom comment field is added to the display and a label is defined for it, the label did not appear in the display if no data was present.

M10032

Customizer

Both

Windows

When the CAE Use row is highlighted, if the radio button below was changed to Value (rather than Code), the field used was changed to Display Amount.

6309

Customizer

Both

Windows

When a line was added above the Comment to the definition of the long display of a data row, the actual data display showed that row below the Comment.

M10096

Customizer

SQL

Windows

When labels for fields were created using an apostrophe, the system suppressed the display of that row.

M10149

Customizer - Attribute

Both

Windows

When the line containing Source, Change Date + User Id was edited to remove the Source, the display did not correctly display the Change Date and User Id.

SS20046

Customizer - Education

Both

Windows

When adding or editing any fields to the Education display the fields would overlap.

M10137

Customizer - Tracking

Both

Windows

When the Custom Lookup1 field was added to the Tracking display and set to display the Value, the corresponding display showed the Code rather than the Value.

M10202

Customizer - Registration

Both

Windows

When Custom Lookup 1, 2, or 3 were added to the display, the label was truncated, removing the numbers.

M10094

Group Security

Oracle

Both

The system did not recognize security settings for a new group, if the group is named, using lower case alphabet characters.

M10157

Harris Utility

Both

Both

The utility only permitted the use of 4 characters for the Attribute Type Code, rather than the standard 6 characters.

M10175

Membership Types Lookup

Browser

Both

When a Membership Type was deleted from the lookup table, it remained in the display of Membership Type table entries until the IIS was next reset.

M10102

Summary Utility

Both

Both

A file needed by the AssignSummaryDefinition.exe portion of the Summary Utility was not included in the system installation. The PICCLP32.OCX will be included in the current and future installations.

M10138

System Info

Both

Both

The default export path that was specified in System Info, did not populate that option in the Run Report screen.

SS20019

System Info

Both

Oracle

When changing the millennium_admin password, the system did not appropriately verify the old password before allowing the operator to change to a new password.

SS20020

System Info

Both

Both

When attempting to change the Millennium Admin Password, if an error is made entering the password, the resulting error message contained a grammatical typo.

M10115

Users

Both

Both

When more than 100 users had logged onto a system an IWAN error resulted. This occurred whether all of the users were logged on concurrently or not.

M10034

View Generator

Both

Both

If a Where clause was created without adding a space before the clause, an Incorrect syntax error results.

M10155

View Generator

Both

SQL

If a security Group was constructed using a different View for Select, than for Update, Delete, and Insert permissions, when a user from that Group attempted to make data edits, an error message was given saying that the user had no Select permission.

M10162

Years Utility

Both

Both

When attempting to use the Campaign Year as the 'Year to Process', in the Years Utility, the Queue on the server gave an 'Invalid field name' error 207.

Issue #

Function

Database

Interface

Description

M10246

Advisories

Both

Both

When creating a new Prospect Tracking / Rating or Prospect Tracking / Research assignment, the advisory hyperlink that was displayed would not link to the constituent's data.

M10135

Easy Ask

Both

Windows

When asking a question that is a sentence fragment (not using the word 'list'), Easy Ask did not correctly identify constituents.

M10166

Easy Ask

Both

Windows

When asking a question such as, 'List people who live in CT' followed by 'Which people work in NY' as an Extend, runtime errors resulted. To work around this reported issue within Easy Ask, you will instead receive the message 'Unable to find a primary data table in the results returned. You will not be able to link back to data.' When you OK that message, the names of the constituents will be shown as a simple list - not as search results which show the information as links to the Profile display.

M10136

Easy Ask - Mapping

Both

Windows

When the answer to a question did not include Address information (for example, 'Which people played football?'),when you clicked on the mapping icon, no map could be generated. The system now returns address information to the behind-the-scenes file, even when you have not asked for it and it is not displayed. This allows the mapping function to locate addresses for the selected constituents.
The exception to this behavior is when you have asked a question that does not select constituent rows. (for example, 'Count the people who played football.') In that case, a message will remind you that you may not link back to data from this data.

NA

PDA

Both

Both

If your institution uses SSL security settings and also have users with PDAs using the Palm Pilot operating system, you must have valid SSL certificates.

M10143

PDA Options

Both

Windows

Following the use of the PDA/Create item (under the main menu bar item, Options), future attempts to log in to Millennium resulted in a runtime error, or following a reboot of the machine, a message prompting you to rename the program file. (Work around was to delete the Program folder - NOT the Program Files folder.) The problem has been corrected.

File Name

Description

Millennium Explorer

In the Browser interface's Millennium Explorer, the Reference, Millennium Help item has been updated to reflect the changes in the items in the Explorer in this release.

All data table descriptions

The custom number fields (addrnum1, addrnum2, for example) should have been shown with a length of 10,0. Some were incorrectly listed with a length of 13,0.

automated_membership_process.html

References to the use of the Gifts file in connection with Membership process have been removed. The Membership process may be associated with the Dues table only.

batch_file.html

A sentence fragment was removed from the end of the first paragraph.

bookmarks.html

This file has been renamed favorites.html.

chart_of_accounts_and
_solicitations_applet.html

This file was deleted due to redundancy.

context_menuswindows.html

sspcontext_menuswindows.html

Prior to Release 7.3, context menus were only used by the Windows interface but with this release, they are integrated into both types of interfaces (Windows and Browser) and both types of screen definitions (HTML and Customizer). Therefore, there is no longer a need for a Help topic specific to that interface and they have been removed.

custom_display_
designer.html

Information was added regarding 'System fields' and the fact that they may be used in designing a display for a table, but they will be suppressed in any insert or update maintenance form.

data_display.html

data_display_-_windows.html (removed)

Prior to Release 7.3, there were several variations in the display of data based on whether you were using the Browser or Windows interface, and there were two Help topics on this subject. With this Release, the control of the display area is not dependent on the interface. Therefore, the Data_Display.html topic has been edited to reflect the display changes that came about as a part of this enhancement, and the topic, Data_Display_-_Windows.html has been removed.

dues_detail.html

The chart showing the default values for NPV and Asset Amounts was changed to indicate that Bequest transactions have an Asset Value = the face value of the transaction.

In the description of the duesmrcvd field, the list of transaction types for which this field is set to 'M' was expanded to include credits issued as a result of a match pledge payment being applied to an individual's pledge balance.

The descriptions for duesrschfl and duesrschky have been removed. These fields were present in earlier versions of Millennium but are not part of the current database.

email.htm

Since this function has been incorporated into the My Millennium component, email.htm has been removed from the Help files.

employment.html

Wording was added to emphasize the fact that Relationship rows are automatically created based on Employment rows with a status of Active, No Longer at the Job, or Retired ('act','no','ret').

explorer_windows.html

Descriptions were added for the functionality of the Profiles Reports and the Event Reports (web reports).

financial_reports.html

The description of the VSE Survey was changed to indicate that the definition of a deferred gift is not based on Class1, but rather on Acct CAE Codes 'U', 'V', and 'W'.

giving_detail.html

The chart showing the default values for NPV and Asset Amounts was changed to indicate that Bequest transactions have an Asset Value = the face value of the transaction.

The description for the giftamtplg was edited to emphasize that this field does not include the joint amount and that it is not a total for all allocations.

In the description of the giftmrcvd field, the list of transaction types for which this field is set to 'M' was expanded to include credits issued as a result of a match pledge payment being applied to an individual's pledge balance.

The descriptions for giftrschfl and giftrschky have been removed. These fields were present in earlier versions of Millennium but are not part of the current database.

In the giving_detail.html for 7.2.2 documentation, the section Gift Transaction Field Descriptions, had some gift fields listed that were intended for future versions, but were not implemented. They were: giftjamnt (now giftjntamt), giftjasset, giftjamtpl, giftjnetpv, giftjdeduct, giftjmny1, giftjmny2, giftorigpl, giftpend, giftpubfl

giving_tree.html

M10185

The description of the Giving Tree contained inadvertent references to the Giving Tree. Those references have been corrected.

group_maintenance-browser.html

group_maintenance-windows.html

Due to the convergence of the Browser and Windows components for User Security, the need for separate help topics for the two interfaces was eliminated. Therefore, the two files, group_maintenance-browser.html and group_maintenance-windows.html have been replaced by a single file named group_maintenance.html. In addition, the coordinating Site-Specific files were replaced by a single file named sspgroup_maintenance.html.

import_utility.html

In the import file layout, the start position of Institution, School, and Concentration 1 was corrected.

lookup_layout.html

For the Chart of Accounts, the length of the chart_cred and chart_debt fields was corrected to read '30'.

For the Dues Batch Number and Gift Batch Number, the length of the table_val field has been corrected to read '10'.

For Solicitations, clarification was added to emphasize that the 'Account' field is unrelated to the Chart of Accounts.

lookup_table_maintenance.html

The description of the use of the Access security settings for lookup table entries has been corrected to say that all users may view data rows using lookup entries to which they do not have Access, including the display of that lookup entry. (They may not edit a data field in an existing data row or create a data row using an entry to which their Access is restricted.)

lookup_table_maintenance_
windows.html and ssplookup_table_maintenance.html

Due to the software changes to consolidate the handling of Lookup Table Maintenance between the Browser and Windows interfaces, there is no longer a need for separate Help topics on this subject for the different interfaces. Therefore, the file, lookup_table_maintenance_windows.html and ssplookup_table_maintenance_windows.html have been eliminated from the Help files.

lookups.html

The description of the Dues Batch Number has been corrected to indicate that the length of the Value field is ten characters.

The list of required entries in the CAE Categories lookup table now includes the following:
FS - Faculty and Staff
GP - Grandparent
ST - Student
N - Fund-raising Consortia
PF - Personal/Family Foundation

lookups_2.html

The description of the Gift Batch Number has been corrected to indicate that the length of the Value field is ten characters.

lookups3.html

For the ZIP Code lookup table, the source of our standard information was corrected to read 'USPS' (rather than the Melissa Data Corporation.)

mergeid.html

The instructions for the cleanup step of the merge process have been changed to indicate that when you delete the Basic Data row, the Death and Tracking rows will automatically be deleted.

new_assignment.html

A cross reference hyperlink was added from Assignment Frequency to System Info.

proposals.html

The label information for propdistr was changed to non-displaying as this field is not applicable to Proposals'

relation_tree.html

The file describing the Relation Tree was missing from the Help system.

relationships.html

The description of reldnrflag was changed to 'Not in use at the present time.'

The description of reltyp for a non-constituent was corrected to read 'non' (rather than 'blank'.)

run_criteria.html

A notation was added cautioning that you should not attempt to run reports when logged in as the system administrator.

Search.html
search-windows.html

A notation was added cautioning that you should not attempt to perform searches and then save the search results when logged in as the system administrator.

standard_lookups.html

Information on additional standard entries was added for Quid Pro Quo Items and Seating Shapes.

Quid Pro Quo Items
Code: q8020, Value: System-Generated 80/20 Quid Pro Quo

Seating Shape
Code: oval Value:Oval
Code: rec Value: Rectangular
Code: row Value: Row
Code: rnd Value: Round
Code:sqr Value: Square

CAE Categories
Code: FS Value: Faculty and Staff
Code: GP Value: Grandparent
Code: ST Value: Student
Code: N Value: Fund-raising Consortia
Code: PF Value: Personal/Family Foundation

system_info.html

The description of the use of the Printers.exe utility to assist in the setup of Printers on the System Info page has been changed to indicate that copies of the utility are found on the IIS and in the Queue directory of each Queue machine.

Table of Contents

The table of contents for the Help System was edited to include all of the available utilities for the Browser interface, and to reflect the new and re-configured elements of the software for this release.

tasks.html

The field description for taskactfil was completed.

tender_data_maintenance.html

A notation has been added to the procedures for entering a Credit Card, Gift in Kind, or Securities data row, reminding that these secondary data rows are not available as links to a transaction with a Type of 'Credit'.

totals.html

The description of the Total Option, Include spouse has been modified to the following:

Include spouse - for each constituent selected, will include the spouse's portions of joint transactions as well as all transactions made solely by the spouse that also meet the criteria. For this calculation, the system will look for a spousal relationship (types sp, spnm, lp, and lpnm) and if one is found, that constituent's giving information will be included.

Previously, this description stated that the system would search for a deceased spouse if a spouse was not found. It does not do so.

tracking.html

The field descriptions for the custom fields for this table had a typographical error. All of the custom field names begin with 'donr', not 'donor' as they were shown in the documentation prior to this release.

tracking_reports.html

The documentation for the standard Tracking Report templates was missing the link to the images showing the formatted results of the Donor Research Report by Prospect Manager and Donor Research Report by Prospect Name. That link has been fixed.

user_maintenance-browser.html

user_maintenance-windows.html

Due to the convergence of the Browser and Windows components for User Security, the need for separate help topics for the two interfaces was eliminated. Therefore, the two files, user_maintenance-browser.html and user_maintenance-windows.html have been replaced by a single file named user_maintenance.html. In addition, the coordinating Site-Specific files were replaced by a single file named sspuser_maintenance.html.

Information was added indicating that the Userid must begin with an alphabetic character and may not contain dashes.

user_options.html

A notation was added to clarify that the User Display Option to show linked data in Short display mode is only shown on the form when the institution is using the Customizer to define the display. Institutions who use Templates may achieve the same results by editing the individual display templates for short display.

user_security.html

The hyperlinks to the topics Group Maintenance, User Maintenance, and View Maintenance were adjusted to match the new configuration of those topic files.

value_based_lookups.html

A significant amount of information was added to clarify the process the system uses to identify matching entries in a lookup table during data entry.

view_maintenance-browser.html

view_maintenance-windows.html

Due to the convergence of the Browser and Windows components for User Security, the need for separate help topics for the two interfaces was eliminated. Therefore, the two files, view_maintenance-browser.html and view_maintenance-windows.html have been replaced by a single file named view_maintenance.html. In addition, the coordinating Site-Specific files were replaced by a single file named sspview_maintenance.html.

writeoff_utility.html

The (invalid) example in the first paragraph of Using the Writeoff Utility was removed.

Interface

Table or Directory

Description

Both

actions

This table now includes the following:

actjntid
actjntkey (indexed as action07)

Both

attachments

This table now includes the following:

docdesc
docjntkey

Both

attendance

This table now includes the following:

attid

Both

attribute

This table now includes the following:

attrjntid
attrjntkey (indexed as attribut06)

Both

benefits

This table now includes the following:

bendate1
bendate2
benmny1
benmny2
bennum1
bennum2
benyesno
benlook1
benlook2
benlook3
bentext

Both

benefitslevel

This table now includes the following:

benldate1
benldate2
benlmny1
benlmny2
benlnum1
benlnum2
benlyesno
benllook1
benllook2
benllook3
benltext

Both

campaigns

This table now includes the following:

table_ack

Both

comments

This table now includes the following:

commjntid
commjntkey (indexed as comment04)

Both

contactinfo

This data table was added to store corporate contact information. It includes the following:

contkey
contid
contdoc
contdate
contuserid
contugroup
conttitle
contfirst
contmiddle
contlast
contsuffix
contsalut
contsortnm
contntype
contjobttl
contaddrl1
contaddrl2
contaddrl3
contcity
contplace
contcntry
contzipcod
contregion
contdstrct
contterrit
contzone
contphone
contfaxph
contemail
contsource
contlnkfil
contlnkkey
contdate1
contdate2
contmny1
contmny2
contnum1
contnum2
contyesno
contlook1
contlook2
contlook3
conttext
contfnum
contcrdate
contcomm

Both

corebio

This table now includes the following:

coreuserec
corepwdec
corejoint
corespcrd
coreothcrd
coreretmfl
corespmfl
corempkey
corebrthyr
corebrthmn
corebrthdy
corehintec
coreanswec

The length of the corettlbar field has been increased from 30 to 60 characters.

Both

criteria_name1000

(for example)

The length of the criteria2 field in all criteria tables has been lengthened to 1000 characters. The conversion to 7.3 will make this change in all existing criteria tables and all new ones will be created with the lengthened field. This was done in part to accommodate the longer Prompting Text for Prompted Reply criteria statements. In addition, position 470-476 of the criteria2 fields have all been set to RESERV in anticipation of future enhancements to the Millennium Reporter.

Both

demogrph

This table now includes the following:

demojntid
demojntkey (indexed as demo03)

Both

donor

This table now includes the following:

donrjntid
donrjntkey (indexed as donor03)

Both

dues

This table now includes the following:

duesorigpl

Both

finance

This table now includes the following:

finjntid
finjntkey (indexed as finance03)

Both

font_names

This lookup table was added to register the font styles that individual users may use to adjust the appearance of their display. This table varies from the standard layout for lookup tables in that it does not utilize Codes. The Font Name is stored in the Value field in the table.

The standard Values are:

<blank>
Arial
Comic Sans MS
Courier
Courier New
Garamond
Letter Gothic
Lucinda Console
Lucinda Sans Unicode
Microsoft Sans Serif
Tahoma
Times New Roman
Verdana

Both

gifts

This table now includes the following:

giftorigpl

Both

Lookup tables

The following lookup tables have been added:

Benefits_Lookup1
Benefits_Lookup2
Benefits_Lookup3
Benefitlevel_Lookup1
Benefitlevel_Lookup2
Benefitlevel_Lookup3
Contactinfo_Lookup 1
Contactinfo_Lookup 2
Contactinfo_Lookup 3
Memories_Lookup 1
Memories_Lookup 2
Memories_Lookup 3
Membership_Lookup1
Membership_Lookup2
Membership_Lookup3
Membershipcards_Lookup1
Membershipcards_Lookup2
Membershipcards_Lookup3
Subscription_Lookup1
Subscription_Lookup2
Subscription_Lookup3
Subscriptionlevel_Lookup1
Subscriptionlevel_Lookup2
Subscriptionlevel_Lookup3

Both

matchfoundation

This data table was added to support the optional Millennium component, Correct GM. It includes the following:

mfparname
mftitle_2
mffname_2
mfmiddle_2
mflname_2
mfsuffix_2
mfadmin_2
mforgname2
mfaddr1_2
mfaddr2_2
mfcity_2
mfstate_2
mfzip5_2
mfzip4_2
mfphone_2
mftitle_3
mffname_3
mfmiddle_3
mflname_3
mfsuffix_3
mfadmin_3
mforgname3
mfaddr1_3
mfaddr2_3
mfcity_3
mfstate_3
mfzip5_3
mfzip4_3
mfphone_3
mftitle_4
mffname_4
mfmiddle_4
mflname_4
mfsuffix_4
mfadmin_4
mforgname4
mfaddr1_4
mfaddr2_4
mfcity_4
mfstate_4
mfzip5_4
mfzip4_4
mfphone_4
mfdate
mfcrdate
mfcruser
mfsource
mfsmashd
mfsmashd_2
mfsmashd_3
mfsmashd_4

Both

matchparent

This data table was added to support the optional Millennium component, Correct GM. It includes the following:

mpkey
mporgname
mpaka
mpfundname
mptitle
mpfname
mpmiddle
mplname
mpsuffix
mpadmtitle
mpaddr1
mpaddr2
mpcity
mpstate
mpzip5
mpzip4
mpphone
mpphoneext
mpminimum1
mpminimum2
mpminimum3
mpmaximum1
mpmaximum2
mpmaximum3
mpannmax
mpratio1
mpratio2
mpratio3
mpfiscalyr
mpallelig
mpfullelig
mpsalelig
mppartelig
mpretelig
mpspelig
mpboarddir
mpfouryear
mpgradschl
mpcommun
mpseminary
mpsecondry
mpelemschl
mptechschl
mpdonrform
mpinstform
mpdonorphn
mpemprecpt
mpdonorweb
mpreceipt
mpacklettr
mpathletic
mpathlschl
mpathlbld
mpalumni
mpgradreg
mpfamily
mpmembreq
mppatient
mphealth
mpmuseum
mpsocserv
mpperfarts
mppubradio
mpreligion
mpeviron
mpcultural
mpcharity
mpfratsor
mphospital
mpcontine
mpmonthly
mpquartrly
mpannual
mpsemiann
mpqmonth1
mpqmonth2
mpqmonth3
mpqmonth4
mpsemim1
mpsemim2
mpannmonth
mpemail
mpcompurl
mpcomment1
mpcomment2
mpcomment3
mpcomment4
mpdate
mppassword
mpfndname
mpgiftform
mpgifturl
mpdeadline
mpprior
mpcrdate
mpcruser
mpsource
mpsmashd

Both

match subsidiary

This data table was added to support the optional Millennium component, Correct GM. It includes the following:

mskey
mssubname
msdate
msmpkey
mscrdate
mscruser
mssource
mssmashd

Both

membership

This table now includes the following:

membdate1
membdate2
membmny1
membmny2
membnum1
membnum2
membyesno
memblook1
memblook2
memblook3
membtext

Both

membershipcards

This table now includes the following:

carddate1
carddate2
cardmny1
cardmny2
cardnum1
cardnum2
cardyesno
cardlook1
cardlook2
cardlook3
cardtext

Both

memories

This table now includes the following:

memlookup1
memlookup2
memlookup3
memcampyr
memmny1
memmny2
memmny3
memmny4
memmny5
memmny6
memmny7
memmny8
memmny9
memmny10
memmny11
memmny12
memmny13
memmny14
memmny15
memdate1
memdate2
memdate3
memdate4
memdate5
memdate6
memdate7
memdate8
memdate9
memdate10
memyesno1
memyesno2
memyesno3
memyesno4
memcomm
memtext1
memtext2

Both

other_info

This table now includes the following:

oinfoid

Both

plannedgifts

This table now includes the following:

planjntid
planjntkey (indexed as plangift05)

Both

proposal

This table now includes the following:

propjntid
propjntkey (indexed as proposal05)

Both

rating

This table now includes the following:

ratejntid
ratejntkey (indexed as rate04)

Both

relation

This table now includes the following:

relcontfl
relothcrd
reljntid
reljntkey (indexed as rel09)

Both

subscription

This table now includes the following:

subdate1
subdate2
submny1
submny2
subnum1
subnum2
subyesno
sublook1
sublook2
sublook3
subtext

Both

subscriptionlevel

This table now includes the following:

subldate1
subldate2
sublmny1
sublmny2
sublnum1
sublnum2
sublyesno
subllook1
subllook2
subllook3
subltext

Both

sysinfo

This table now includes the following:

site_license
site_code
site_replicate
site_repl_server
match_tender_default
super_delete_warning

Both

Templates

The Templates directory (\inetpub\wwwroot\Mill\Template) includes 74 new template files, named xxxxx_mini.mit, where xxxxx is the table name or prefix.

In addition, the following new templates have been added:

Galloc_up.mit
alloc_up.mit
Galloc2_up.mit
Dalloc2_up.mit

Both

userlist

This table now includes the following:

user_crdate

Interface

Table or Directory

Description

Both

address

This table now includes the following:

addrpend
addrpubfl

Both

address_pending

This table has been added to hold data as entered by a constituent via the optional Millennium Online Constituent Directory module. This table exactly mimics the layout of the data table with which it is associated. Information is held in this table until it is processed into the primary data table. See Online Constituent Directory.

Both

attribute

This table now includes the following:

attrpend
attrpubfl

Both

attribute_pending

This table has been added to hold data as entered by a constituent via the optional Millennium Online Constituent Directory module. This table exactly mimics the layout of the data table with which it is associated. Information is held in this table until it is processed into the primary data table. See Online Constituent Directory.

Both

campaigns

This table now includes the following:

table_ecom

Both

constituent_types

This table now includes the following:

table_ecom

Both

corebio

This table now includes the following:

corepub00
corepub01
corepub02
corepub03
corepub04
corepub05
corepub06
corepub07
corepub08
corepub26
corepub28

Both

corebio_pending

This table has been added to hold data as entered by a constituent via the optional Millennium Online Constituent Directory module. This table exactly mimics the layout of the data table with which it is associated. Information is held in this table until it is processed into the primary data table. See Online Constituent Directory.

Both

ecommerce_pending

This table has been added to hold data as entered by a constituent via the optional Millennium Online Constituent Directory module. This table is used to hold information from a visitor to the institution's Web site, who is not already a constituent, but who wants to make a donation. This table holds information which will be used to create a Basic Data, Name, Address, Phone, and Gift data row for the donor when the data from the pending table is processed and incorporated into the data database. See Online Constituent Directory.

Both

jobs

This table now includes the following:

jobspend
jobspubfl

Both

jobs_pending

This table has been added to hold data as entered by a constituent via the optional Millennium Online Constituent Directory module. This table exactly mimics the layout of the data table with which it is associated. Information is held in this table until it is processed into the primary data table. See Online Constituent Directory.

Both

membership

This table now includes the following:

membpend
membpubfl

Both

name

This table now includes the following:

namepend
namepubfl

Both

name_pending

This table has been added to hold data as entered by a constituent via the optional Millennium Online Constituent Directory module. This table exactly mimics the layout of the data table with which it is associated. Information is held in this table until it is processed into the primary data table. See Online Constituent Directory.

Both

phone

This table now includes the following:

phnpend
phnpubfl

Both

phone_pending

This table has been added to hold data as entered by a constituent via the optional Millennium Online Constituent Directory module. This table exactly mimics the layout of the data table with which it is associated. Information is held in this table until it is processed into the primary data table. See Online Constituent Directory.

Both

relation

This table now includes the following:

relpend
relpubfl

Both

relation_pending

This table has been added to hold data as entered by a constituent via the optional Millennium Online Constituent Directory module. This table exactly mimics the layout of the data table with which it is associated. Information is held in this table until it is processed into the primary data table. See Online Constituent Directory.

Both

school

This table now includes the following:

schlpend
schlpubfl

Both

school_pending

This table has been added to hold data as entered by a constituent via the optional Millennium Online Constituent Directory module. This table exactly mimics the layout of the data table with which it is associated. Information is held in this table until it is processed into the primary data table. See Online Constituent Directory.

Both

sysinfo

This table now includes the following:

ecomm_pub_00
ecomm_upd_00
ecomm_pub_01
ecomm_upd_01
ecomm_pub_02
ecomm_upd_02
ecomm_pub_03
ecomm_upd_03
ecomm_pub_04
ecomm_upd_04
ecomm_pub_05
ecomm_upd_05
ecomm_pub_06
ecomm_upd_06
ecomm_pub_07
ecomm_upd_07
ecomm_pub_08
ecomm_upd_08
ecomm_pub_26
ecomm_upd_26
ecomm_pub_28
ecomm_upd_28