icon is located to the left of each header
on the System Options page. Click the icon to access the relevant Help
topic. See Data Display, Help
for further details on how context-sensitive Help behaves in Abila Millennium.The System Options page provides access to the forms and components that are used to set:
A Help icon is located to the left of each header
on the System Options page. Click the icon to access the relevant Help
topic. See Data Display, Help
for further details on how context-sensitive Help behaves in Abila Millennium.
The System Display Options are maintained on the System Display Options page. Refer to the System Display Options topic for complete details for accessing and setting System-wide display options.
System Options are institutional customizations of Abila Millennium's system behavior. Some System Options pertain to how data is entered and maintained in Abila Millennium, or pertain to setting system-wide data entry default values for all users. Some options turn on special data integrity checks. Others serve as flags to instruct the Abila Millennium database triggers to behave in a certain way. The options that are set here apply to all of the users at your site.
The complete list of System Options are as follows:
These options tell the system to remove tabs, line feeds, and carriage returns from comments and text boxes as they are inserted and/or updated, and then store the comment text in its unformatted state in the data table in which it is inserted and/or updated. The user also has the option to not remove formatting, which is the default.
To change the Format Comments/Text Boxes options:
located below and to the left of the System Options header.Set this option to Yes to tell the system to keep a record of every successful and unsuccessful attempt to log on to Abila Millennium.
If this option is on, then the following will be recorded for every attempt to log on:
To set the Audit user login attempts option to Yes:
located below and to the left of the System Options header.These options tell the system to keep track of how many failed log on attempts that a user has made, to lock the user out of Abila Millennium after a specified number of failed attempts are made, and to keep the user locked out until either a specified time interval has passed or until a system administrator unlocks the locked out user.
If you do not want the system to lock out users for failed log on attempts, then set the Number of login failures to 0 and set the Duration of lockout in minutes to 0.
The system can be set to allow locked out users another chance to log on to Abila Millennium after a certain time period has passed. Or, you can make it a system requirement that only a system administrator can unlock a locked out user. A system administrator can unlock a locked out user by using the View Users tool. If you want to make it a system requirement that only a system administrator can unlock a locked out user, set the Number of login failures to a number greater than 0, and then set the Duration of lockout in minutes to 0.
To set the Log In Lockout options:
located below and to the left of the System Options header.The system uses the login_audit system table to record failed log on attempts. Each record will include the User ID of the user who was logging on, the IP address of the computer or device that was attempting to access the system, the date and time that the user attempted to log on, and a flag to indicate that the user was logging on to Mobile Millennium to access the system.
Each user can choose a time interval for the Assignments that he or she creates. This time interval will determine how often the Millennium Assignment Service will check for that assignment against the database.
The system administrator can also set an institutional limit on this time interval for all assignments for all users, so that no matter what time interval that an individual user selects for an assignment, the Millennium Assignment Service will not check that assignment against the database more frequently than what is set by the system administrator.
The system administrator sets the Assignment Frequency to 60 minutes. A user creates one assignment set to check every 5 minutes, and another assignment set to check every 20 minutes. But, the system setting limits checking to a 60 minute interval, so both assignments will be checked every 60 minutes.
The system administrator sets the Assignment Frequency to 5 minutes. A user creates one assignment set to check every 5 minutes and second assignment set to check every 20 minutes. The checking for the first assignment would occur, then, every 5 minutes, and the checking for the second assignment would occur every 20 minutes because the system's frequency setting is at or lower than the user's frequency settings.
It is possible to edit the System Options setting here to a larger amount of time than is already set in users' existing assignments. The new System Options setting will not override the users' current individual assignment settings.
To set the Assignment Frequency option:
located below and to the left of the System Options header.The Assignments component of My Millennium can be set up so that the system will generate email messages to notify users when Advisories have been posted. If your site wants these notifications to have a return email address, then enter it here.
To assign a return address to Advisory Notifications that are sent by email:
located below and to the left of the System Options header.The hyperbolic Relation Tree displays are constructed based on the number of 'degrees of separation' that each user specifies, via each tree that he or she accesses for display. Abila Millennium allows for seven degrees. To preserve system resources, the system administrator can use this option to restrict that limit. When a user accesses the hyperbolic tree display and then the pull-down list showing the degrees of separation to be used, the list will include only the numbers of degrees that are acceptable according to your system setting here.
To set the Degrees of Separation Limitation option
located below and to the left of the System Options header.When set to Yes, the system will warn users during data entry that the constituent for whom they are inserting or updating a name record will either have no preferred name or will have multiple preferred names after that name record is inserted or updated.
To set the Check preferred names option
located below and to the left of the System Options header.When set to Yes, the system will warn users during data entry that the constituent for whom they are inserting or updating an address record will either have no preferred address or will have multiple preferred addresses after that address record is inserted or updated.
To set the Check preferred address option
located below and to the left of the System Options header.This option tells the system to allow users to delete constituents who own Giving or Dues Transaction data rows. If this option is set to Yes, then a user who attempts to delete a constituent who owns Giving or Dues data by using the constituent's Basic Data row (known as Super Delete) will be allowed to do so. If this option is set to No, then a user who attempts to delete a constituent who owns Giving or Dues data will not be allowed to do so.
To set the option to allow constituents who have giving or dues data to be deleted
located below and to the left of the System Options header.This option tells the system what month to use as the start of the Fiscal Year when performing functions and calculations in several areas in Abila Millennium (for examples, Visual Analyzer, Giving Trends, and Dues Trends). Some sites begin their fiscal year in January, others in June, and still others may begin their fiscal year in an entirely different month.
To set the Fiscal Year Begin Month option
located below and to the left of the System Options header.This option tells the system what Tender Type to use as the default value for the Tender on insert forms that are presented for the creation of a matching gift transaction.
To set the Matching Tender Default option
located below and to the left of the System Options header.This option tells the system to allow users to create a pledge payment schedule for Matching Pledges that differs from the default payment schedule (one payment) that is otherwise automatically inserted by the system.
To set the Display Matching Payment Schedule option
located below and to the left of the System Options header.This option tells the system to use the matching
company or the matching company's 
Match Through
constituent as the donor for any match pledge or match potential transaction.
If the option is set to Yes, the system will use the matching company.
If the option is set to No, the system will use the Match Through constituent.
When unchecked, this system-wide option is set to 'No'. Abila Millennium will use the 'Match Through' constituent, not the matching company, as the matching entity for any match pledge or match potential transaction. In addition, when this option is set to 'No', any updates made to the 'Match Through' constituent's matching information (for example, match ratios, match minimum and maximum levels) will be made to the matching company as well. Finally, when set to 'No', when updating the matching company's 'Match Through' id field (coremtchid) for the first time, a company/match through company constituent relationship is created.
To set the Pull the Matching Ratios from the Corporation
located below and to the left of the System Options header.When this option is set to No, any matching information (for example, match ratios, match minimum and maximum levels) updates that are made on the Match Through constituent's Basic Data row will be made to the matching company as well. And, when updating the matching company Match Through id (coremtchid) field on its Basic Data row for the first time, a company/match through company constituent relationship will be created.
This option tells the system to automatically journal all of the Credit and Honor Transactions that are linked to a primary transaction when the primary transaction is journaled.
To set the Automatically Journal Credits and Honors option
located below and to the left of the System Options header.This option tells the system to automatically update of all linked Credit and Honor transactions that link to a primary transaction with the same changes that are made to the primary transactions, and at the time the primary transaction is updated.
To set the Update Credits and Honors option
located below and to the left of the System Options header.This option tells the system to automatically update the Purpose (giftrest), Campaign (giftcamp), Class1(giftclass1) and Class2 (giftclass2) fields on the payment when those fields are updated on the pledge allocation for which the payment was made.
To set the Update Payment Transactions option
located below and to the left of the System Options header.If the Gift Ledger Flag on the payments is set to Yes, or if Gift Batch Number on the payments has been closed, then those payments will not be automatically updated.
This option tells the system to automatically fill in the Delivery Date for a Membership Benefit. If this option is set to Yes, when a benefit is inserted as part of automated Membership processing, or inserted manually, the Benefit Delivery Date will default to the Membership Renewal Date. If this option is set to No, the Delivery Date will not be populated and the user will need to fill the date in manually if a Delivery Date is desired.
To set the Default the Benefit Delivery Date option
located below and to the left of the System Options header.This option tells the system to allow users to save the ID numbers from the results of a constituent Profile Search, to the Clipboard. The id numbers will be saved as a string and will be delimited by tab, comma or return (carriage-return/line feed), depending on what delimiter option that the user picks.
If this system option is set to Yes, the Search Results page will include the Copy to Clipboard link. The user points to the link to see the delimiter options, and clicks on option that he or she wants to use. If this option is set to No, then the Copy to Clipboard link will not show.
The Search Results Display must include the ID Number field from the Basic Data table so that the Copy to Clipboard feature can properly work.
To set the Allow ID number's to be Copied from the Search Results Screen to the Clipboard option:
located below and to the left of the System Options header.This option tells the system to allow users to integrate Tasks with Microsoft Outlook (Outlook). If Outlook integration is allowed, it can be either manual or real time. If it is set to Manual, then users must initiate the integration or tell the system precisely when to do it. If it is set to Real-time, then as users add, update, and delete Tasks by using My Millennium > Tasks, they are automatically added, updated and deleted in Outlook. See Tasks and Outlook Integration.
To set the Task Integration with Outlook option
located below and to the left of the System Options header.This option tells the system to allow users to upload Constituent contact information - name, addresses, phone numbers , email addresses, and so forth - to Microsoft Outlook (Outlook). If allowed, then users can initiate the upload process from each constituent's data display or from My Millennium > Contact Upload.
To set the Allow Contacts to be Uploaded to Outlook option
located below and to the left of the System Options header.Set this option to Yes to display Death information with Basic Data. The Death item will be removed from the Millennium Explorer and users will access a constituent’s Basic Data display in order to view a Death record. Note that if a constituent does not have a death record, then the Death section header will not be shown. If this option is set to Yes, users can insert a Death record directly from the Basic Data display page by using either the or Link > Death via Default menu item on the Edit button 
that is located to the left of the constituent's Basic Data record.
To set the Display Death with Basic Data option
located below and to the left of the System Options header.This option allows you to append a date and time stamp to the report name, so that specific runs of a report can be saved. Setting this option allows you to run comparison versions of a report. If the option is not set, each run of a report overwrites the previous run.
If one of the active entries in the Institutions lookup table represents your organization, you can identify that entry as your home institution. Then, when constituent Education records are viewed in Millennium Drive, the system will highlight the records that have an Institution equal to your organization's home institution.
To set your home institution
located below and to the left of the System Options header.
.
to retry the search.Abila Millennium can audit and log all data modifications made to constituent tables, such as data inserts, edits, and deletes. Millennium system administrators or the database administrator configure audit logging options. After audit logging has been configured, Abila Millennium performs audit logging in the background, and the audit logging process is transparent to Abila Millennium users. For more information about audit logging, see Audit Log.
To configure audit logging options
located below and to the left of the Auditing header.Password options lay out the guidelines that a user must follow when changing the password that he or she uses to log on to Abila Millennium.
Abila Millennium does not check to verify that the password rules set here apply to the 'sa' or the 'MILLORA' system administrator user accounts.
A user's password can not be re-used until four password changes have occurred. Assigning the password to a user when the user is created counts as the first password 'change'. On the fifth password change, the first password can be re-used, on the sixth password change, the second password can be used, and so on.
located below and to the left of the Password Options header.If you want to allow all users the ability to change their own password, click on Y in the Allow users to change their password list. If you do not want to allow all users the ability to change their own password, then click on N instead.
If this option is set to Y, then the other options on this form are available and can be set as you desire.
If this option is set to N, then the other options on this form are not available.
Check this box to force any new user, or any current user who does not have a password that conforms to the password requirements that are set forth here, to change his or her password the next time that they log on to Abila Millennium. The user_passchngnow field in the userlist system table will be set to 'Y' for these users. A user with a password that conforms to the password requirements will not be required to change his or her password. Once a user who is required to change his or her password does in fact do so, the user_passchngdt field in the userlist table will be set to the date and time the password is changed. A password change will not again be required unless the password expires.
Important! If users are allowed to change their own passwords and if the system administrator makes any changes in required password length, expiration, minimum number of alphabetic characters, upper case characters, special characters, and/or minimum number of numeric characters required, and if the system administrator wants to insure that each user's password conforms to the new requirements, the Administrator must also select this option before saving the password options changes.
Situations may arise where the system administrator would like to turn off Force all Users to change password at next login. Check this box to set the user_passchngnow field in the userlist system table to 'N' for all Abila Millennium users. When any user next logs on to Abila Millennium, then he or she will not be required to change his or her password.
Abila Millennium will automatically tally the required minimum lengths of alphabetical, uppercase, numeric, and special characters and adjust the required password length accordingly. To take advantage of this functionality, you will want to enter the password requirements in the following order:
Enter a minimum required length for user passwords. This length cannot exceed 30. If you do not require a minimum password length, then enter 0. If a minimum password length is required, then you must enter a number equal to or greater than the sum of the minimum number of alphabetical, special, and numeric characters that you are entering. The number of alphabetic (and uppercase), numeric, and special character fields do not have to add up to the minimum password length, but they cannot exceed it.
Enter the number of days before a user must change his or her password. An entry of 0 means that the password does not expire and a user will never have to change his or her password. The number of days entered here can be up to, and include 999.
Enter the minimum number of alphabetic characters that a user must incorporate into his or her new password. If you do not require a minimum number of the password characters to be alphabetical, then enter 0.
Of the required minimum number of alphabetic characters, how many are required to be uppercase? Enter this number here. If you do not require a minimum number of the password characters to be uppercase, then enter 0.
Enter the minimum number of numeric 'characters' that a user must incorporate into his or her new password. If you do not require a minimum number of the password characters to be numeric in nature, then enter 0.
Enter the minimum number of special, or non-alphanumerical, characters that a user must incorporate into his or her new password. If you do not require a minimum number of the password characters to be special characters, then enter 0.
Users must have a password that is at least 10 characters in length, contain at least 1 special character, 2 numbers, and 2 upper case alphabetical characters.
The password options could be set as follows:
A password of AB123_4567 would meet the password criteria. AB123_abcd would also meet the password criteria. Passwords of aB123_4567 or aB_123_abcd would not meet the password criteria.
If your site subscribes to Abila Fundraising Online (AFO), you can integtrate your AFO account with Millennium. After you enter the AFO account information, you can map AFO forms to your Millennium data, so that gifts and other transactions processed in AFO forms are entered into the Millennium constituent database. You can also use AFO forms on the Millennium website for your Millennium campaigns.
Note: For more information about Abila Fundraising Online, visit the solution page at http://www.abila.com/support/abilafundraisingonline/ to download the Abila Fundraising Online User's Guide.
To create a new connection with Abila Fundraising Online:
located to the right of the AFO Accounts header.To edit an existing connection with Abila Fundraising Online:
located below and to the left of the AFO Accounts header.If your site subscribes to Sage Payment Solutions (SPS), this option group will be enabled. Once the merchant account information (provided to you by Sage Payment Solutions) has been entered, Abila Millennium will automatically use Sage Payment Solutions to process all future credit card and bank draft transactions.
Your site may have only one Sage Payment Solutions merchant account, or your site may maintain multiple merchant accounts. An entry must be made for each SPS merchant account that your site uses.
One merchant account must be designated as the default merchant account. This will be the account through which SPS will process any donations that are made to a purpose (restriction from the Chart of Accounts) that is not associated with a particular merchant account. Only one merchant account can be the designated as the default merchant account.
If your site collects event registration fees, one merchant account must be designated as the Events merchant account - the account through which SPS will process these fees. Only one merchant account can be designated as the Events merchant account.
Sage Payment Solutions can store a constituent's credit card or bank draft account information (credit card numbers, bank account numbers, expiration dates, routing numbers, and so forth) so that they are available to the Abila Millennium user when a constituent makes another donation or pays another fee by credit card or bank draft. If a constituent's account information is saved for future use, the Credit Card and Bank Draft insert forms for that constituent will display a drop list box that contains a list all of his or her accounts that have been previously saved for future use.
Your site can choose to make this functionality available, or not. If it is available, then the Credit Card and Bank Draft insert forms will display the drop list box that lists all of the previously saved accounts, as well as the Save for Future Use? check box. If this functionality is not available, then these components will not be display on the Credit Card and Bank Draft insert forms.
button located to the right of the Sage Payment Solutions header. The Sage Payment Solutions insert form
displays.The Merchant Account information and settings are entered on the System Options page, but they are stored in the merchant_account system table.
Sage Payment Solutions, through Sage Exchange, is making available to all Abila Millennium sites a Vault Service Only Merchant Key and Merchant ID. No payment processing is possible, but card numbers and their expiration dates can be stored in the Vault. Once the Vault Only account information (provided to you by Sage Payment Solutions) has been entered, Abila Millennium will automatically use SPS Vault Only Account to store all future credit card information. Your site may have only one SPS Vault Only account.
You can use the SPS Vault Only account to store a constituent's credit card numbers and their expiration dates for record keeping purposes. If a constituent's account information is saved for future use, the Credit Card insert forms for that constituent will display a drop list box that contains a list all of his or her accounts that have been previously saved for future use.
Your site can choose to make this functionality available, or not. If it is available, then the Credit Card insert forms will display the drop list box that lists all of the previously saved accounts, as well as the Save for Future Use? check box. If this functionality is not available, then these components will not be display on the insert forms.
button located to the right of the SPS
Vault Only Account header. The form to create the new account displays.Sage Payment Solutions allows you to upgrade your existing Vault Only account to a SPS subscription with full account functionality. Contact Sage Payment Solutions for details, and to receive an new Service Key and Service ID. Be sure to let SPS know you are upgrading from a Vault Only Account.
Displays the default Sage Payment Solutions Virtual Terminal URL. You can select the edit button to enter a Custom URL to be used to Access the SPS Virtual Terminal or leave the field blank to use default setting.
When you purchase Instant Address, you will receive a URL from Initium Software. Enter the URL into the Initium Setup page to configure the Instant Address service for use with Abila Millennium.
button located to the right of the Initium Software
header.To configure serialized tax receipting for use at your site, use the following steps.
located to the right of the Serialized
Tax Receipting heading.Once Serialized Receipting is enabled, Abila Millennium system administrators or the database administrator must specify Serialized Tax Receipting permissions for users. See User Maintenance, Configuring Serial Receipts for more information.
The WealthEngine Information page is used to configure access to the wealth research component of WealthEngine (FindWealth). Users can then connect to WealthEngine through Abila Millennium and view and import WealthEngine data.
To configure access to WealthEngine:
button. From this point forward, your configuration will depend on how your site accesses WealthEngine.
Note: Clicking Proxy service account will remove information that may already be entered in the controls (below) that are used to set up named account access to WealthEngine.
The number of Abila Millennium users who can access WealthEngine depends on your subscription license with WealthEngine.
icon on the right of the Import and Search check boxes for that user.Named account access:
Note: Clicking Named accounts will remove information that may already be entered in the controls (above) that are used to set up proxy service account access to WealthEngine.
icon on the right of the Import and Search check boxes for that user. The user will no longer be able to access WealthEngine directly through Abila Millennium.An Abila Millennium user who has been assigned to a WealthEngine account name must first create and then maintain his or her WealthEngine password through the WealthEngine website. The user will then record the password in Abila Millennium on the My Millennium WealthEngine Information page. Abila Millennium can then give the user access to WealthEngine without prompting the user for his or her WealthEngine log on credentials. For more information, see the My Millennium topic, Wealth Engine.
After access to WealthEngine has been configured for your site, a Millennium system administrator (or the database administrator) must configure WealthEngine import settings before users can import WealthEngine data into the constituent records. For more information, see Configuring WealthEngine Import Settings.
About Millennium Drive: