Ellucian Advance

Release Notes
Release 9.9.0
December 2013
Banner, Colleague, PowerCampus, and Luminis are trademarks of Ellucian Company L.P. or its affiliates and are registered in the U.S.
and other countries. Ellucian, Ellucian Advance, Ellucian Degree Works, Ellucian Course Signals, Ellucian SmartCall, and Ellucian
Recruiter are trademarks of Ellucian Company L.P. or its affiliates. Other names may be trademarks of their respective owners.

2013 Ellucian Company L.P. and its affiliates.

Contains confidential and proprietary information of Ellucian and its subsidiaries. Use of these materials is limited to Ellucian licensees, and is
subject to the terms and conditions of one or more written license agreements between Ellucian and the licensee in question.

In preparing and providing this publication, Ellucian is not rendering legal, accounting, or other similar professional services. Ellucian makes no
claims that an institution's use of this publication or the software for which it is provided will guarantee compliance with applicable federal or
state laws, rules, or regulations. Each organization should seek legal, accounting and other similar professional services from competent
providers of the organization's own choosing.

Prepared by: Ellucian

4375 Fair Lakes Court
Fairfax, Virginia 22033
United States of America

Revision History
Publication Date Summary
December 2013 New version that supports Advance 9.9.0 software.
 Contents
Executive Summary ........................................................................................................ 7

Database Installation Overview ..................................................................................... 16

New Features and Functionality ................................................................................... 17

Community Source Initiatives ....................................................................................... 17

Additional Donor Information...............................................................................................................17
Granularity and Precision on the List of Entity Telephone Numbers and Addresses ...................................18
Enhanced Address Table with Geo-Coding ............................................................................................19
Report Filtering ..................................................................................................................................19

Biographic Improvements ............................................................................................. 21

Status Date on Entity Detail .................................................................................................................21
Active Emails on the Entity Overview ....................................................................................................22
VCR Functionality Added to Committee Header Overview and Detail .......................................................23
Employment Data Validation for Business Addresses ..............................................................................24
Email Start and Stop Dates ..................................................................................................................25
Same Home Telephone Prompt on Marital Information ..........................................................................26
Class Agent Code Length Increase .......................................................................................................26
Preferred Email and Telephone ............................................................................................................27
Preferred Telephone Numbers with the Same Type ...............................................................................28
Major Added to the Entity Overview Header ..........................................................................................28
Alternate ID Warning for Duplicate IDs .................................................................................................29
Telephone Information on Entity Update ..............................................................................................30

Gift/Pledge Improvements ............................................................................................ 32

Batch Defaults....................................................................................................................................32
Streamlined Gift and Pledge Entry ........................................................................................................34
Transaction List and Donor Transaction List ..........................................................................................36
Keyboard Shortcuts ............................................................................................................................36
Matching Gift Receipt Number on Matching Gift Entry ............................................................................37
Proposal ID Default on Pledge Payments ..............................................................................................38
Soft Credit on Associated Donors List ...................................................................................................39
Transaction List Sort ...........................................................................................................................40
Associated Donor Information in Pledge Drop-Down ..............................................................................41
Receipt Date Added to One-Line - Simple Transaction List ......................................................................42
Prevention of a New Pledge Payment to the Pledge in the Same Batch as the Pledge Modification .............43

Ellucian Advance | 9.9.0 Release Notes 3

 Prevention of Duplicate Matching Gifts .................................................................................................44

Prospect Tracking Improvements .................................................................................. 45

Contact Report Sort on Tasks ..............................................................................................................45
Prevention of Duplicate Assignments ....................................................................................................46

Membership Improvements .......................................................................................... 47

Membership and Dues Payment Summary Navigation ............................................................................47
Prevention of Duplicate Memberships ...................................................................................................48

Lookup Improvements ................................................................................................. 49

Gift, Pledge and Matching Gift Lookup Additions ....................................................................................49
Associated Code Renamed on Gift Lookup ............................................................................................49

System Improvements ................................................................................................. 50

Upgrade Planner ................................................................................................................................50
Go To ................................................................................................................................................50
Audit Information ...............................................................................................................................51

DataLoader Improvements ........................................................................................... 53

Display Current Telephone for Add operations .......................................................................................53
Select Telephone for All Telephone Types .............................................................................................53
Display Current Email for Add Operation ...............................................................................................53
Select Email for all Email Types ...........................................................................................................53
Display Primary Employment for Add Operation ....................................................................................53
New System Option to Link Address and Employment ............................................................................54
Batch Status with Errors after Posting ..................................................................................................54
Override a Duplicate Entity Error ..........................................................................................................54

Gift/Pledge Loader Improvements ................................................................................. 55

Auto Claim Received Functionality ........................................................................................................55

Configuration Utility Improvements ............................................................................... 55

Forms and Controls Maintenance .........................................................................................................55

iModules Encompass Connector Improvements .............................................................. 56

Recurring Pledges/Payments & Perpetual Giving ....................................................................................56
Encompass Connector and Web Services 2.1.........................................................................................58
Automatically Archiving Push Details ....................................................................................................58
Multi-Allocation Gifts and Pledges.........................................................................................................59
Donor Allocation Instructions ...............................................................................................................59
Duplicate Transactions Pulled from Encompass .....................................................................................59
Gift Batch Separation ..........................................................................................................................59
Display of Additional Encompass Online Transaction Information ............................................................60
Online Giving Report ...........................................................................................................................60

Ellucian Advance | 9.9.0 Release Notes 4

 Support Changes ......................................................................................................... 60
Advance Windows, AdvLoader, Advance Web Community and Advance Web Reporting ............................60
Event Management and Data Movement...............................................................................................63
Encompass Connector with Tomcat 7 and Java 7 ..................................................................................63
Microsoft Exchange Server 2013 ..........................................................................................................63
Crystal Reports 2011 (64-bit)...............................................................................................................64
Microsoft Internet Explorer 10 on Windows 7 ........................................................................................64
Adobe RoboHelp 10 ............................................................................................................................64
Advance Mobile ..................................................................................................................................64
iPad and Mac Operating System...........................................................................................................65
Sybase PowerBuilder ..........................................................................................................................65

Support ......................................................................................................................... 66

Browsers..................................................................................................................... 66
Client Operating Systems ............................................................................................. 66
Databases ................................................................................................................... 66
Oracle Database Access Components (ODAC) ................................................................ 67
Web Servers................................................................................................................ 67
Online Help ................................................................................................................. 67
Application Development .............................................................................................. 67
Other.......................................................................................................................... 68

Compatibility................................................................................................................. 70

Advance Configuration Utility ........................................................................................ 70

SmartCall / Advance Synchronization ............................................................................. 70
SmartCall Integration Utility (SIU) ................................................................................. 70
Pledge Integration Utility (PIU) ..................................................................................... 70
Site Help Integration Utility........................................................................................... 70
Advance Export (AdvExport) ......................................................................................... 71
Banner Student ........................................................................................................ 71
Upgrade Planner .......................................................................................................... 71
Encompass Connector .................................................................................................. 71

System-wide Changes................................................................................................... 72

Database Tables and Indexes ....................................................................................... 72

Table Changes ...................................................................................................................................72
New Indexes ......................................................................................................................................80

Ellucian Advance | 9.9.0 Release Notes 5

 Modified Indexes ................................................................................................................................81

TMS Views .................................................................................................................. 82

New TMS Views..................................................................................................................................82
Modified TMS Views ............................................................................................................................82

System Options ........................................................................................................... 82

New Advance System Options .............................................................................................................83

Defect Fixes .................................................................................................................. 84

Ellucian Advance | 9.9.0 Release Notes 6

Executive Summary

Through its Ellucian Advance suite of software products, Ellucian provides institutions and
organizations with a robust platform of products, services, and processes, including the following new
functionality in Advance 9.9.0.

Additional Donor Information

The Additional Donor Information pane in Gift and Pledge Entry now displays the entity's Record
Type and the date their Active Preferred address was most recently updated. Having the Record Type
available during gift entry decreases the likelihood of gift entry operators accidentally creating new
duplicate entities instead of crediting the correct existing entities, which can happen when working
with common names. While the Record Type aims to prevent duplication of entities, the date the
Preferred Active address was most recently updated aims to allow the gift entry operator to ensure the
address was recently updated or validated.

Granularity and Precision on the List of Entity Telephone Numbers and Addresses
Previously, when viewing an entitys list of telephone numbers via the Telephone or Addresses
application, records sorted by Status Code. This is helpful for institutions that maintain a limited
amount of codes. In order to assist institutions that utilize numerous Status Codes, the Status Code
field in the list now integrates the hierarchy order values associated with the codes in the status code
TMS views. This enables you to more precisely and logically view the list of telephone numbers or
addresses for an entity.

Enhanced Address Table with Geo-Coding

There is a one-to-one relationship between an address and its geo-coding attributes, including the
latitude and longitude. Therefore, new fields are now included in the address table that offer
flexibility in the process and storage of geocoded address information. In addition, a new field is also
available in the geo code database table that can be used to enable searching and filtering for locations
within a specific geographical region.
These new fields are not available on the Address or Geo Code forms, as they aim to provide you
with the ability to more easily geo-code addresses through a site-specific process, which can be
performed by each institution or organization at their discretion, separate from this new functionality.

Report Filtering
A new filtering mechanism allows you to filter the Report List. When you select Reports from the
Main Menu, the Report List appears and you can enter a word or phrase in the new Keyword field.
When you enter a value, Advance will filter the list and only display reports that contain the keyword
text anywhere in the row.
Additionally, new functionality allows you to add links to the page tree, which provide access to
reports that are grouped together. Once you group reports together, selecting that link from the Page
Tree on the Reports page will display all of the reports associated with that group.

Ellucian Advance | 9.9.0 Release Notes 7

 Status Date on Entity Detail
The Status Date field now displays on the Entity Detail form for both person and organization
entities. No schema changes were made in order to support this new functionality, as this field was
present in the Advance database prior to this release.

Active Emails on the Entity Overview

Email addresses will only display on the Entity Overview when the preferred check box is checked
and the Email Status is set to Active, which is the same way that address and phone information
displays on the Entity Overview. This allows you to set the row with the preferred indicator on the
email to a value other than Active while keeping the preferred check box checked and preventing the
email address from displaying on the Entity Overview.

VCR Functionality Added to Committee Header Overview and Detail

VCR functionality was expanded to include Committee Header records, which can be viewed via the
Committee Overview and Committee Details forms in the Committee Application. When Committee
records are copied to the Committee Header Clipboard and you access the Committee Header
Application, you can select VCR from the Actions Menu and navigate through the Committee Header
records on the clipboard.

Employment Data Validation for Business Addresses

A new validation on the Address form allows you to indicate whether you wish to use the Title and/or
Employer Name associated with the entitys business address or their employment record. The new
validation appears when the Title and/or Employer Name in the business address doesn't match the
Title and/or Employer Name in the entitys employment record and you attempt to link the business
address with the employment by selecting the employment record from the Employment Link drop-
down.

Email Start and Stop Dates

Start and stop dates are now available on the Email form in order to allow you to indicate the dates
for which email addresses are valid. These fields were also added to the Email Lookup in the
Advanced Lookup application.

Same Home Telephone Prompt on Marital Information

The Same Home Telephone prompt on the Marital Information form now appears and allows you to
indicate which telephone number to use when the Same Home Telephone check box is checked for
a marital record when each spouse has a different home telephone record, regardless of the value of
system option 28. This prompt appears when you select the Same Home Telephone check box, prior
to clicking Save.

Class Agent Code Length Increase

The class agent field was increased from 3 to 15 characters. This increase aims to allow institutions
and organizations with numerous class agents to create more meaningful codes and not need to create
codes with special characters due to a finite number of available codes given the 3 character code
constraint.

Preferred Email and Telephone

Advance now automatically sets the preferred indicator on new email or telephone record, when a
new email or telephone record is added, and there are currently no active email or telephone records
for the entity. If there are inactive telephone records (Status = Inactive), regardless of how many

Ellucian Advance | 9.9.0 Release Notes 8

 inactive records exist, and you add a new active (Status = Active) telephone record, Advance will set
the preferred indicator for that record. The same logic applies to email records.

Preferred Telephone Numbers with the Same Type

When a new telephone record is added and there isnt already a telephone record with that type, the
preferred check box will be checked automatically for the new record. If there is already a preferred
telephone record of that type and a new telephone record for that type is added, the preferred check
box on the new record will be checked automatically and the preferred check box on the previous
record of that type will be unchecked automatically.

Major Added to the Entity Overview Header

In addition to displaying the entitys degree information in the Entity Overview header, the entitys
Major now displays directly to the right of the degree information. If there is one degree with multiple
majors, only the first major (Major 1) will display for the degree.
If there are multiple degrees with multiple majors, as many degrees as possible will display, along
with the first major of each degree. If there are additional degrees and majors that do not display, a
hyperlink will appear at the end, which allows you to drill-down to the Degrees form to view the
additional records.

Alternate ID Warning for Duplicate IDs

A new warning on the IDs form indicates whether the specified ID Type and ID Number combination
is already associated with a different entity. This warning appears after you enter an identical ID Type
and ID Number combination on a second entity and click Save.
This warning aims to serve as an indication that perhaps the wrong number was entered, or that
additional research is necessary in order to confirm the number is accurate. Since this is a warning
and not an error, the save will continue and all other validations will be performed.

Telephone Information on Entity Update

With Advance 9.9.0, the Entity Update application includes three new forms, which allow you to add
and/or maintain telephone information, independent of address information. New telephone forms on
the Entity Update include the Home Telephone, Business Telephone and Other Telephone forms.

Gift and Pledge Batch Defaults

A new gift batch defaults application, named My Defaults List, provides gift entry operators with the
flexibility to create a set of defaults that can be re-used with any gift batch. Whereas the batch
defaults on Gift Batch Control allows you to create a set of defaults for use with the transactions in
that batch, this new application allows you to create and save a set of defaults, which includes a much
larger range of values that can be set as defaults. Once a set of defaults is established it can be applied
to a batch using an updated version of the Batch Control form. An unlimited number of defaults can
be created in order to fit the needs of each user. Default rows are tied directly to each user in order to
provide an appropriately configured user-experience. Public default rows can also be created in order
to provide all gift entry operators with access to standard default rows for use at your institution. In
addition to the new defaults application, numerous batch defaults were added to the Batch Control
form in order to expedite, simplify, and streamline the gift and pledge entry transaction process.
These batch default changes apply to classic gift and pledge entry as well as the new streamlined gift
and pledge entry.

Ellucian Advance | 9.9.0 Release Notes 9

 Streamlined Gift and Pledge Entry
Streamlined gift and pledge entry provides gift entry operators with a new user friendly and
simplified process for entering gift and pledge transactions, which includes the ability to create
associated donor rows on the main gift and pledge entry form, thereby eliminating the need to save
the primary row and associated donor rows individually. In addition to introducing a new avenue that
allows operators to quickly and efficiently enter gift and pledge transactions, streamlined gift and
pledge entry provides flexibility, easy entry of transactions with multiple donors and/or allocations,
and new defaults for expediting the entry process. When additional tender details are needed, entry is
performed via a pop-up box, eliminating the need to scroll down as in classic gift and pledge entry.
The new streamlined gift and pledge entry process does not aim to replace the previous gift entry
process, known as classic gift entry, which is still available. Each institution can determine whether
they wish to continue to use classic gift and pledge entry forms or the new streamlined gift and pledge
entry form. Each user can determine, at their discretion on a batch-by-batch basis, whether they wish
to accept the default setting set by the institution, or toggle to the other method.
This design attempts to organize fields into appropriate sections and displays sections in a logical
order providing more efficient keyboard navigation. Fields that are required and are often/always
used are near the top of the form, while fields that are less often populated and/or usually default are
located lower down on the form. As with all other forms and applications in Advance, streamlined
gift and pledge entry forms and applications can be modified using the Configuration Utility.

Transaction List and Donor Transaction List

Previously, after drilling down on a transaction and returning to the Transaction List report in Gift
Batch Control, you would be returned to the top of the Transaction List report. In order to facilitate
more efficient review of transactions when drilling down on a transaction, the transaction will open in
a separate tab. When returning to the Transaction List after drilling down on a transaction, the icon of
the last transaction selected will be highlighted, which enables you to more precisely and logically
view and drill-down on the transactions in the Transaction List.
Additionally, if System Option 192 was enabled, a Transaction List was displayed at the bottom of
Gift Batch Control. In addition to using System Option 192, this Transaction List now appears on the
Gift Batch Control Page Tree and is known as Transaction Donor List and includes numerous new
fields.
After drilling down on a transaction using the Transaction Donor List on the Gift Batch Control
navigation tree, the icon of the last transaction selected will be highlighted, which enables you to
more precisely and logically view and drill-down on the transactions in the Transaction Donor List.
An Action menu was also added to the Transaction List, which provides the ability to Sort, Filter,
Print, and Export the data on the form. These new features for Transaction List and Transaction
Donor List apply to classic gift and pledge entry as well as the new streamlined gift and pledge entry.

Keyboard Shortcuts
Several keyboard shortcuts were revised in order to support new browser versions. These keyboard
shortcuts apply to all supported browsers.

Matching Gift Receipt Number on Matching Gift Entry

The Matching Gift Receipt # field was added to the Match Donor Gift form in order to allow you to
view the number during Matching Gift Entry. Previously, this number was only visible on the Batch
Proof Report. The new field appears during matching gift entry of the match donor gift information.
When the information is saved, the number appears in inquiry only.

Ellucian Advance | 9.9.0 Release Notes 10

 Proposal ID Default on Pledge Payments
A new system option (system option 349) allows you to indicate whether you want the Proposal ID to
default into the Proposal field when making a payment on a pledge. When this system option is
enabled and you make a payment on a pledge that is linked to a proposal, the Proposal ID will
automatically appear in the Proposal ID field. By default this new system option is disabled, which
means Proposal IDs linked to pledges will not automatically default into this field when payments are
made against those pledges.

Soft Credit on Associated Donors List

In order to allow gift entry operators to view the Soft Credit amounts of associated donors without
needing to select each row in the list to view the amounts below in the detail record, the Soft Credit
amount was added to the list portion of the Associated Donors master detail form.

Transaction List Sort

New fields on the Sort Order prompt in the Transaction List allow you to sort the transaction list
using the donors Preferred Name Sort and/or Report Name. After transactions are saved in a batch
during gift entry, the transaction list can be accessed via the Page Tree. When the list appears,
selecting Sort from the Actions menu will yield the sort prompt.

Associated Donor Information in Pledge Drop-Down

When entering a pledge payment, the Pledge drop-down now includes additional donor information
that indicates the donor's association to the pledge. This includes whether the association is primary,
joint, covering account, group, etc. This new functionality aims to assist gift entry operators in
determining which pledge to select, in the event there are multiple pledges for the donor, and thus
decrease the likelihood of selecting the incorrect pledge.

Receipt Date Added to One-Line - Simple Transaction List

In order to allow users to more easily reconcile giving information when communicating with donors,
the One-Line - Simple Transaction List was enhanced to include the Receipt Date for all financial
transactions (Gifts, Pledges, Matching Gifts, Pledge Payments, etc.). When you access the Giving
Summary form and select Views from the Giving branch of the Page Tree, the One-Line - Simple
Transaction List can be selected from the Views form. When the transaction list appears, the new
Receipt Date field appears directly to the right of the Credit Amount field.

Prevention of a New Pledge Payment to the Pledge in the Same Batch as the Pledge
Modification
Advance now prohibits the entry of a new Pledge Payment to the Pledge in the same batch as a
modification to that pledge. This validation aims to decreases the likelihood of incorrect payment
schedules.

Prevention of Duplicate Matching Gifts

A new warning message prevents the entry of duplicate matching gifts that contain the same
Organization ID and Check #. If you enter a matching gift for an organization with a check number,
then attempt to add a second matching gift for the same organization with the same check number,
Advance will display a warning message that the check number is already assigned to an existing
Matching Gift Number.
If this occurs, the Organization ID will be removed from the Matching Gift Details form and you
must re-enter the Organization ID, then select the correct Matching Gift # from the drop-down and

Ellucian Advance | 9.9.0 Release Notes 11

 complete entry of the matching gift transaction before submitting it for processing

Contact Report Sort on Tasks

Previously, the Contact Report drop-down on Task forms (Entity Tasks, Prospect Tasks, Proposal
Tasks, Program Prospect Tasks, Program Proposal Tasks and Contracts and Grants Tasks) sorted the
list of available Contact Reports using the Report ID. This made it difficult to view, locate and select
the correct Contact Report when multiple contact reports were available for selection.
Effective with Advance 9.9.0, the Contact Report drop-down on all of the aforementioned task forms
sorts in date order by the Contact Report Date, with the most recent Contact Reports at the top of the
list.

Duplicate Checking for Assignments

Effective with Advance 9.9.0, a staff member can have multiple assignments per assignment type, per
entity, as long as one and only one status per assignment type is active. This validation applies to the
various types of assignments include Entity, Prospect, Proposal, Program and Program Proposal
Assignments.

Membership and Dues Payment Summary Navigation

Navigation refinements aim to streamline the process of locating and viewing membership summary
information. The Dues Payment form in the Dues Payment Profile application now includes a link
directly to the Membership and the Payments form in the Membership Profile application now
includes the Payment ID field, along with the ability to drill-down to the Dues Payment Detail.

Prevention of Duplicate Memberships

New functionality in Membership Entry prevents you from entering the same membership, for the
same entity. A duplicate membership is defined as one that has the same ID Number, Membership
Type, Rate, Payment Plan, and Start and Stop dates as an existing membership.
This validation occurs for both Standard Membership Entry and Fast Key Membership Entry (via
System Option 334).
This error message aims to alert the membership entry operator that the membership information
must be reviewed for accuracy and either corrected or deleted before the batch can be closed and
submitted for processing. Membership entry operators cannot proceed until the necessary action is
taken when this scenario occurs

Gift, Pledge and Matching Gift Lookup Additions

For consistency purposes, fields were added to the Gift, Pledge and Matching Gift lookups.

Associated Code Renamed on Gift Lookup

The Associated Code label on the Gift Lookup was renamed from Code to Associated Code in order
to help identify the field.

Upgrade Planner
The Upgrade Planner is an adjunct utility for Ellucian Oracle database applications that generates
information about the cumulative set of changes that would occur in the application database between
the current site release of a product and a later target release.
The Upgrade Planner analyzes the data dictionary and source code of the current site product release,
and compares it to a data set of information about the data dictionary and source code of a chosen

Ellucian Advance | 9.9.0 Release Notes 12

 target release of the product. The Planner looks at the data dictionary and in-database source code. It
does not analyze other application artifacts such as out-of-database source code artifacts, or
application server mid-tier artifacts.
The Upgrade Planners purpose is to assist institutions and organizations in the process of planning
for an upgrade of an Ellucian product, by providing comprehensive information about the database
changes that would be expected in an upgrade, without the need to download or install any of the
upgrade releases.

Go To
Previously, when you accessed the Go To application the ID (entity, prospect, program, proposal,
allocation, etc.) that was most recently accessed appeared in the Open with ID field. This occurred in
order to allow you to easily navigate to a different application for the same ID. This behavior
occurred regardless of whether you had an application open with a different ID in context and
regardless of whether any applications (tabs) were open. Effective with Advance 9.9.0, the Open with
ID field in the Go To application will default the ID of the current and active application (tab). If no
applications are open, an ID will not default into the Open with ID field.

Audit Information
Audit Information, accessible via the Actions Menu, allows you to view information that indicates
when the current record was first added, most recently updated, the name of the operator that most
recently updated the record and the user group associated with the user that most recently updated the
record. Effective with Advance 9.9.0, Audit Information now includes the full name of the operator in
addition to their username. Previously only the username displayed

Display Current Telephone for Add operations

If an entity has an existing telephone row of the same type that is being added, DataLoader will
display the current telephone in the Current column when viewing an individual Add transaction. If
there is more than one row that qualifies, DataLoader will display the one that is preferred, if the
preferred telephone is of the same type. If not, DataLoader will display the most recently maintained
telephone row of that type

Select Telephone for All Telephone Types

While viewing a telephone transaction in DataLoader (Add, Mod, Delete) a new Select Telephone
menu item appears in the Actions menu. Selecting this action displays a list of active phone numbers
that can be used to replace the one displayed in the Current column.

Display Current Email for Add Operation

If an entity has an existing email row of the same type that is being added, DataLoader will display
the current email in the Current column when viewing an individual Add transaction. If there is
more than one row that qualifies, DataLoader will display the one that is preferred, if the preferred
email is of the same type. If not, DataLoader will display the most recently maintained email row of
that type.

Select Email for all Email Types

While viewing an email transaction in DataLoader (Add, Mod, Delete), a new Select Email menu
item appears in the Actions menu. Selecting this action displays a list of active emails that can be
used to replace the one displayed in the Current column.

Ellucian Advance | 9.9.0 Release Notes 13

 Display Primary Employment for Add Operation
If an entity has a primary employment row, DataLoader will display in the Current column when
viewing an individual Add transaction.

New System Option to Link Address and Employment

When System Option 380, Link Business Address and Employment in DataLoader, is turned on, and
there is an Add transaction for a business address and an Add transaction for an employment row for
the same entity in a single batch, DataLoader will link the two of them together automatically. This
works for bulk posting and single transactions if the employment row is posted after the address row.

Batch Status with Errors after Posting

The DataLoader Batch Maintenance form allows you to maintain the details of a batch. Processed
with Errors is an existing, system-delivered and system-required DataLoader Batch Status, which
appears in the Status drop-down. Effective with this release, upon the completion of a single or bulk
posting operation, if there are any Active or Deferred transactions that have non-warning errors, the
status of the batch will be automatically changed to Processed with Errors. The batch will remain at
that status until you manually change it to something else, or the batch status becomes Complete (all
non-Discarded transactions are posted).

Override a Duplicate Entity Error

System Option 57, Use Enhanced Entity Duplicate Check for DataLoader, is used to detect name
collisions when adding new Entities in DataLoader. This prevents a duplicated entity from being
added. Effective with this release, a new check box named Override Duplicate Name allows you to
override this behavior on a transaction-by-transaction basis. If a duplicate is detected and the check
box is checked, the validation based on option system option 57 will be skipped for that transaction
and the entity will be added. This allows you to proceed with the load process and not have to return
later after youve disabled system option 57 in order to load the transactions, as in previous releases.

Auto Claim Received Functionality

Gift/Pledge Loader was enhanced and now supports the creation of matching claims when the donor
works for a matching gift company.

Forms and Controls Maintenance

The Database field in the Forms and Controls Maintenance window is now a required field. If you do
not select a value, ora_foo will be selected for you when you click Save.

Recurring Pledges/Payments & Perpetual Giving

The Encompass Connector, for pushing and pulling data to-and-from Advance, was enhanced to
include new functionality that allows you to transfer recurring and perpetual gift information from
Encompass to Advance. Recurring and perpetual gifts allow donors to contribute an amount that's
paid on a regular basis.

Encompass Connector and Web Services 2.1

Ellucian is providing a new connector that utilizes Web Services 2.1 due to iModules planned
retirement of Web Services 2.0. This is necessary in order to provide institutions and organizations
using Advance and the Encompass Connector the ability to upgrade to a new connector while
decreasing the likelihood of a service interruption when iModules officially retires Web Services 2.0.

Ellucian Advance | 9.9.0 Release Notes 14

 Automatically Archiving Push Details
Depending on the volume of records pulled from Encompass to Advance, it is possible that the
Advance database tables that contain the records from Encompass can grow quite large very quickly.
In order to assist institutions in the cleansing of historical data, a new database table,
data_transfer_push_archive, is utilized by a new automated process that archives records. When a
new transfer is initiated, records will be automatically archived from the data_transfer_push_detail
table to the new data_transfer_push_archive table with no user intervention.

Multi-Allocation Gifts and Pledges

As with one-time gifts, Advance allows single and multiple allocation transactions that originated in
Encompass. Since institutions process multiple gift transactions in several distinct ways, either as a
single transaction with multiple allocations or a single transaction for each allocation, Advance allows
for each of these scenarios by allowing you to set system option 368 to meet the needs of your
institution.
When this system option is disabled, Encompass transactions (One-time Gifts, Recurring Gifts and
Perpetual Gifts) with multiple allocations will be processed in Advance as one transaction with
multiple allocations. When this system option is enabled, transactions will be split between multiple
transactions.

Donor Allocation Instructions

Included in the additional information pane in the Gift Entry Ledger is a section that displays
comments about the donor's wishes on how they want their donation applied. This is useful for donors
that want to make a donation to an allocation or allocations that are not available on the Encompass
campaign form.
In order to allow donors entering one-time, recurring, and perpetual gift transactions that have a mix
of allocation information or when a donor doesnt specify an allocation code, Advance system option
369 provides you with the ability to specify a stand-in allocation code. This temporary stand-in
allocation code will be automatically associated with a transaction when a donor enters instructions
instead of selecting an allocation in Encompass during transaction entry. Advance batches that
contain this temporary allocation code on any transaction in the batch cannot be closed. During
review of the transaction in the gift entry ledger, the gift entry operator must select the appropriate
allocation code(s) in order to close the batch and submit it for processing.

Duplicate Transactions Pulled from Encompass

Prior to this release of Advance, when a transaction was identified as being previously pulled from
Encompass, these duplication transactions would be created in a duplicate transaction batch. With
this release, System Option 370 allows you to control how Advance will handle duplicate online
transactions and either output these transactions to a report or place them in a duplicate transaction
batch. When using the report output option, the online report can be accessed on the Gift Batch Page
Tree.

Gift Batch Separation

The Encompass Connector was enhanced to include new functionality that allows you to create
separate gift batches based on the Campaign ID, Gift Type, In Honor/In Memory/Joint, and dollar
threshold values. System Options 371-374 control whether separate batches are created.

Display of Additional Encompass Online Transaction Information

With Advance 9.9.0, a new form is available on the Gift Profile and Pledge Profile that displays

Ellucian Advance | 9.9.0 Release Notes 15

 Online Transaction information. Additionally, Joint Donor, Matching Company, In Honor/In
Memory information, Billing Information and Allocation Request data coming from Encompass will
be displayed in the Right Pane in the Gift Ledger when reviewing transactions pulled from
Encompass.

Online Giving Report

A new Online Giving Report is available from the Reports Menu for reconciling online transactions
processed in Advance with reports you receive from your financial institution.

Advance Windows, AdvLoader, Advance Web Community and Advance Web Reporting
Advance 9.9.0 includes support for and compatibility with a myriad of new versions of Ellucian and
third party products.

Database Installation Overview

The following chart describes the supported Advance database upgrade paths. If your database
configuration is not described below, or if you have any questions, please contact
[email protected] prior to beginning the database upgrade or installation.
Please refer to the Advance 9.9.0 Database Installation Instructions for additional information.
Current Version Upgrade Instructions
Advance prior to 9.8.1.0 Upgrade to Advance 9.8.1.0, then apply the Advance 9.8.1.1 patch, then
upgrade to Advance 9.9.0
Advance 9.8.1.0 Apply the Advance 9.8.1.1 patch, then upgrade to Advance 9.9.0
Advance 9.8.1.1 Upgrade directly to Advance 9.9.0
Advance 9.8.2.1 Upgrade directly to Advance 9.9.0
Advance 9.8.2.2 Upgrade directly to Advance 9.9.0
No Advance database installed Install a new Advance 9.9.0 database

Ellucian Advance | 9.9.0 Release Notes 16

New Features and Functionality

This section describes new features and functionality in Advance 9.9.0.

Community Source Initiatives

As a customer, you benefit from the Community Source Initiative. These enhancements were created
by your customer peers, solving business needs that you may have at your institution. The
Community Source Initiative enables customers to share what theyve developed with each other. In
the community source model, solutions are developed at other institutions, but are packaged and
delivered to you by Ellucian as part of a normal software release and supported by Ellucian. These
new features are provided to all Ellucian customers under the terms of the maintenance agreement.

Additional Donor Information

The Additional Donor Information pane in Gift and Pledge Entry now displays the entity's Record
Type and the date their Active Preferred address was most recently updated. Having the Record Type
available during gift entry decreases the likelihood of gift entry operators accidentally creating new
duplicate entities instead of crediting the correct existing entities, which can happen when working
with common names. While the Record Type aims to prevent duplication of entities, the date the
Preferred Active address was most recently updated aims to allow the gift entry operator to ensure the
address was recently updated or validated.

Ellucian Advance | 9.9.0 Release Notes 17

Granularity and Precision on the List of Entity Telephone
Numbers and Addresses
Previously, when viewing an entitys list of telephone numbers via the Telephone or Addresses
application, records sorted by Status Code. This is helpful for institutions that maintain a limited
amount of codes. In order to assist institutions that utilize numerous Status Codes, the Status Code
field in the list now integrates the hierarchy order values associated with the codes in the status code
TMS views. This enables you to more precisely and logically view the list of telephone numbers or
addresses for an entity.

Ellucian Advance | 9.9.0 Release Notes 18

Enhanced Address Table with Geo-Coding
There is a one-to-one relationship between an address and its geo-coding attributes, including the
latitude and longitude. Therefore, new fields (latitude, longitude, geocode_geometry,
geocode_address, geocode_failure_ind and geocode_quality) are now included in the address table
that offer flexibility in the process and storage of geocoded address information. In addition, a new
field is also available in the geo code database table that can be used to enable searching and filtering
for locations within a specific geographical region.
These new fields are not available on the Address or Geo Code forms, as they aim to provide you
with the ability to more easily geo-code addresses through a site-specific process, which can be
performed by each institution or organization at their discretion, separate from this new functionality.

Note

These new fields are not supported for use with DataLoader or the Entity Transfer utility
when transferring records from the secondary schema to the primary schema for
advancement records.

Report Filtering
A new filtering mechanism allows you to filter the Report List. When you select Reports from the
Main Menu, the Report List appears and you can enter a word or phrase in the new Keyword field.
When you enter a value, Advance will filter the list and only display reports that contain the keyword
text anywhere in the row.

The Keyword field automatically appears on the Report List. No additional setup is necessary.

Ellucian Advance | 9.9.0 Release Notes 19

 Note

If you wish to disable the Keyword field, you can override the Keyword form control on
the Report List form (form_id = 50465) via the Advance Configuration Utility. For
additional information on overriding form controls, please refer to the Advance
Configuration Examples.
Additionally, new functionality allows you to add links to the page tree, which provide access to
reports that are grouped together. Once you group reports together, selecting that link from the Page
Tree on the Reports page will display all of the reports associated with that group.
To group reports together and display grouped reports via a new link on the Page Tree:
1. In Advance, open the TMS Maintenance application (TMSC or TMST).
2. Locate the TMS Report Sub Type view (tms_report_sub_type).
3. Add a new code for the report sub type (grouping). Make note of the code, as you will need it
later in the procedure.
4. Open the Advance Configuration Utility.
5. From the Web Menu select Pages.
6. When prompted, select the profile to which the changes will apply.
7. Scroll through the list on the left and locate the Reports page (page ID = 50032).
8. Select the Navigation tab on the right-side of the window.
9. Click New Nav Item or Insert Subnav Item, depending on your preferences, to insert the new
item on the Page Tree.
10. Add the new entry with the following attributes. Additional attributes can be added as
necessary:
a. Type = Tree
b. Destination Page = Reports (50032)
c. Destination App = Report List (5051)
d. URL Page = Action.aspx?reportsubtype=AAA
where AAA represents the Sub Type code you added in step 3.
11. Click Save.
12. From the Web Menu select Reports.
13. Scroll through the list and locate the report you wish to associate with the sub report type.
14. In the right-side of the window, select the new report sub type (from step 3) from the Sub
Type drop-down.
15. Click Save.
16. Repeat steps 13-15 for all reports you wish to associate with this group.
17. Purge the cache on the server.
18. Log into Advance and click Reports from the Main Menu.
Notice how the new report sub type appears on the Page Tree. When you select the hyperlink,
all reports associated with this group appear. If the list is large, you can also use the new
Keyword(s) filter at the top to filter the list further.

Ellucian Advance | 9.9.0 Release Notes 20

Biographic Improvements

Status Date on Entity Detail

The Status Date field now displays on the Entity Detail form for both person and organization
entities. No schema changes were made in order to support this new functionality, as this field was
present in the Advance database prior to this release.

Ellucian Advance | 9.9.0 Release Notes 21

Active Emails on the Entity Overview
Previously, email addresses with the preferred check box checked displayed on the Entity Overview
unless the Status was Inactive. This meant non-active email addresses, whose status was anything
other than Inactive, would always display on the Entity overview. In some cases, changing the status
to inactive in order to prevent the email from displaying on the Entity Overview was not desired, as
the status was valid (non-active) as well as preferred.
Effective with Advance 9.9.0, email addresses will only display on the Entity Overview when the
preferred check box is checked and the Email Status is set to Active, which is the same way that
address and phone information displays on the Entity Overview. This allows you to set the row with
the preferred indicator on the email to a value other than Active while keeping the preferred check
box checked and preventing the email address from displaying on the Entity Overview.

Ellucian Advance | 9.9.0 Release Notes 22

VCR Functionality Added to Committee Header Overview
and Detail
Selecting VCR from the Action Menu displays the VCR command buttons in the upper right corner
of the page. If you copied items to the clipboard, and those items are compatible with the form being
displayed, you can display the information for the current form and scroll through the list of items on
the clipboard by utilizing the VCR controls (Forward, Back, First and Last).
Effective with Advance 9.9.0, VCR functionality was expanded to include Committee Header
records, which can be viewed via the Committee Overview and Committee Details forms in the
Committee Application. When Committee Header records are copied to the Committee Header
Clipboard and you access the Committee Header Application, you can select VCR from the Actions
Menu and navigate through the Committee Header records on the clipboard.

Ellucian Advance | 9.9.0 Release Notes 23

Employment Data Validation for Business Addresses
A new validation on the Address form allows you to indicate whether you wish to use the Title and/or
Employer Name associated with the entity's business address or their employment record. The new
validation appears when the Title and/or Employer Name in the business address doesnt match the
Title and/or Employer Name in the entitys employment record and you attempt to link the business
address with the employment by selecting the employment record from the Employment Link drop-
down.

You have the following options when the prompt appears:

Click OK to overwrite the business address Title and/or Employer information on the address
form with the Title and/or Employer information on the employment record.
Click Cancel to keep the information on the business address and not use the information on
the employment record.

Ellucian Advance | 9.9.0 Release Notes 24

Email Start and Stop Dates
Start and stop dates are now available on the Email form in order to allow you to indicate the dates
for which email addresses are valid.

These fields were also added to the Email Lookup in the Advanced Lookup application.

Ellucian Advance | 9.9.0 Release Notes 25

Same Home Telephone Prompt on Marital Information
The Same Home Telephone prompt on the Marital Information form now appears and allows you to
indicate which telephone number to use when the Same Home Telephone check box is checked for
a marital record when each spouse has a different home telephone record, regardless of the value of
system option 28. This prompt appears when you select the Same Home Telephone check box, prior
to clicking Save.

You have the following options when the prompt appears:

Click Use Entity Telephone to update the spouses telephone record to match the telephone
number of the entity on which you are current.
Click Use Spouse Telephone to update the current entitys record to match the telephone
number of the spouse.

Class Agent Code Length Increase

The class agent field was increased from 3 to 15 characters. This increase aims to allow institutions
and organizations with numerous class agents to create more meaningful codes and not need to create
codes with special characters due to a finite number of available codes given the 3 character code
constraint.
In order to support this new code length, the tms_class_agt view in the TMS Code and Table
applications now accepts codes up to 15 characters in length. All database tables capable of storing
this code were also increased to allow codes with a maximum of 15 characters in length.

Ellucian Advance | 9.9.0 Release Notes 26

Preferred Email and Telephone
Advance now automatically sets the preferred indicator on new email or telephone record, when a
new email or telephone record is added, and there are currently no active email or telephone records
for the entity. If there are inactive telephone records (Status = Inactive), regardless of how many
inactive records exist, and you add a new active (Status = Active) telephone record, Advance will set
the preferred indicator for that record. The same logic applies to email records.

Ellucian Advance | 9.9.0 Release Notes 27

Preferred Telephone Numbers with the Same Type
Previously, when a new telephone record was added and a record with the same telephone type
already existed, the preferred check box was not checked automatically on the new record. Effective
with Advance 9.9.0, when a new telephone record is added and there isnt already a telephone record
with that type, the preferred check box will be checked automatically for the new record. If there is
already a preferred telephone record of that type and a new telephone record for that type is added,
the preferred check box on the new record will be checked automatically and the preferred check box
on the previous record of that type will be unchecked automatically.

Major Added to the Entity Overview Header

In addition to displaying the entitys degree information in the Entity Overview header, the entitys
Major now displays directly to the right of the degree information. If there is one degree with multiple
majors, only the first major (Major 1) will display for the degree.

If there are multiple degrees with multiple majors, as many degrees as possible will display, along
with the first major of each degree. If there are additional degrees and majors that do not display, a
hyperlink will appear at the end, which allows you to drill-down to the Degrees form to view the
additional records.

Ellucian Advance | 9.9.0 Release Notes 28

Alternate ID Warning for Duplicate IDs
A new warning on the IDs form indicates whether the specified ID Type and ID Number combination
is already associated with a different entity. This warning appears after you enter an identical ID Type
and ID Number combination on a second entity and click Save.
This warning serves as an indication that perhaps the wrong number was entered, or that additional
research is necessary in order to confirm the number is accurate. Since this is a warning and not an
error, the save will continue and all other validations will be performed.

Ellucian Advance | 9.9.0 Release Notes 29

Telephone Information on Entity Update
Previously, the Entity Update application allowed you to update an entity's Home and/or Business
Telephone number via the Home Address and Business Address Entity Update forms, respectively.
Additionally, you could only add a Home or Business Telephone number if you were also adding
Address data. Effective with Advance 9.9.0, the Entity Update application includes three new forms,
which allow you to add and/or maintain telephone information, independent of address information.
New telephone forms on the Entity Update include the following:
Home Telephone
Business Telephone
Other Telephone
In conjunction with this new functionality, the following telephone changes were made to Entity
Update:
Telephone information is no longer available on the Home Address and Business Address
forms in Entity Update.
A new type of data, Entity Updates Telephone, now appears in the Web Entity Update Batch
Type in DataLoader- Batch from Tables.
This functionality applies when DataLoader is used to review changes entered through Entity Update,
when System Option 260 is enabled. This new functionality does not apply when system Option 260
is disabled and Entity Updates are emailed to designated individuals for review.

Home Telephone
When you select the Home Telephone branch on the Page Tree you will be allowed to add and
maintain home telephone information. The Home Telephone page consists of three forms, which
include the display-only header at the top, the detail record below, and the current telephone records
on the right. In the form on the right, the telephone numbers display as hyperlinks, which if selected,
will navigate you to the Telephone application for the entity. An existing home telephone number for
the entity will automatically display in the detail form. Regardless of whether the home telephone
number exists, when this telephone number is reviewed through DataLoader the action will be Add.

Ellucian Advance | 9.9.0 Release Notes 30

 Business Telephone
The same functionality for Home Telephone records also applies to Business Telephone records.

Other Telephone
The same functionality for Home and Business Telephone records also applies to Other Telephone
records. Other Telephone records are defined as non-home and non-business telephone numbers.
When you enter information in this form, you must select a Telephone Type from the drop-down. The
drop-down contains all current telephone types except for Home, Business, Past Home, and Past
Business. TMS security is not applied to this drop-down. You may change the Telephone Type after
saving, however there can only be one 'Other' telephone record maintained through this form. Unlike
the Home Telephone and Business Telephone forms, an existing non-Home or non-Business will not
default into this form. This occurs because there can be multiple Other Telephone records and
Advance will not know which one to display.

Ellucian Advance | 9.9.0 Release Notes 31

Gift/Pledge Improvements

Batch Defaults
A new gift batch defaults application, named My Defaults List, provides gift entry operators with the
flexibility to create a set of defaults that can be re-used with any gift batch. Whereas the batch
defaults on Gift Batch Control allows you to create a set of defaults for use with the transactions in
that batch, this new application allows you to create and save a set of defaults, which includes a much
larger range of values that can be set as defaults. Once a set of defaults is established it can be applied
to a batch using an updated version of the Batch Control form. An unlimited number of defaults can
be created in order to fit the needs of each user. Default rows are tied directly to each user in order to
provide an appropriately configured user-experience. Public default rows can also be created in order
to provide all gift entry operators with access to standard default rows for use at your institution. In
addition to the new defaults application, numerous batch defaults were added to the Batch Control
form in order to expedite, simplify, and streamline the gift and pledge entry transaction process.
These batch default changes apply to classic gift and pledge entry as well as the new streamlined gift
and pledge entry.

Ellucian Advance | 9.9.0 Release Notes 32

 Once a user creates a set of defaults via the My Defaults List, the established defaults can be applied
to any batch, regardless of whether the batch is for use with classic gift or streamlined gift. As with
the My Defaults List, the only defaults that appear in the drop-down are those that were created by the
same user, and those marked as public. As with other areas in Advance, supervisors (where the
Supervisor check box is checked in the Users Security window in the Advance Configuration Utility)
can see all rows.

In conjunction with this new functionality, the Gift Batch Control application was enhanced to
include new fields that allow you to establish additional defaults for the batch, prior to entering gift
and pledge transactions. These batch default changes apply to classic gift and pledge entry as well as
the new streamlined gift and pledge entry.
The updated Gift Batch Control application contains the following components:
Batch Details
Batch Defaults
Common Gift & Pledge Defaults
Tribute Defaults
Gift Defaults
Pledge Defaults
Associated Donor Defaults
Premium Defaults
Giving Codes Defaults
For additional information on My Defaults List or Batch Control Defaults, please refer to the Advance
Gift and Pledge User Guide.

Ellucian Advance | 9.9.0 Release Notes 33

Streamlined Gift and Pledge Entry
Streamlined gift and pledge entry provides gift entry operators with a new user friendly and
simplified process for entering gift and pledge transactions, which includes the ability to create
associated donor rows on the main gift and pledge entry form, thereby eliminating the need to save
the primary row and associated donor rows individually. In addition to introducing a new avenue that
allows operators to quickly and efficiently enter gift and pledge transactions, streamlined gift and
pledge entry provides flexibility, easy entry of transactions with multiple donors and/or allocations,
and new defaults for expediting the entry process. When additional tender details are needed, entry is
performed via a pop-up box, eliminating the need to scroll down as in classic gift and pledge entry.
The new streamlined gift and pledge entry process does not aim to replace the previous gift entry
process, known as classic gift entry, which is still available. Each institution can determine whether
they wish to continue to use classic gift and pledge entry forms or the new streamlined gift and pledge
entry form. Each user can determine, at their discretion on a batch-by-batch basis, whether they wish
to accept the default setting set by the institution, or toggle to the other method.
This design attempts to organize fields into appropriate sections and displays sections in a logical
order providing more efficient keyboard navigation. Fields that are required and are often/always
used are near the top of the form, while fields that are less often populated and/or usually defaulted
are located lower down on the form. As with all other forms and applications in Advance, streamlined
gift and pledge entry forms and applications can be modified using the Configuration Utility.
Depending on the value of system option 375, the Batch Control form will appear with the new
Streamlined Gift check box checked or unchecked. When system option 375 is enabled, the check
box will be checked by default and when the system option is disabled, the check box will not be
checked by default. You can toggle the check box to fit the particular needs of that batch, if they
differ from other batches. Once a transaction is saved in the batch, the check box cannot be changed.

When the box is checked, the streamlined gift and pledge entry process can begin by clicking Gift &
Pledge Entry from the Page Tree. The Gift & Pledge Entry form consists of the following sections:
Primary Donor Details
Transaction Type Details

Ellucian Advance | 9.9.0 Release Notes 34

 Associated Donor Defaults
Associated Donors
Transaction Details
Premiums

In addition to the various attributes that can be entered on this new form, when you save the record,
you can access additional forms by clicking the appropriate hyperlink from the Page Tree or the Gift
Summary form above.
For additional information on new Association Donor Defaults in the TMS Association View, please
refer to the Advance TMS User Guide.
At this time, Streamlined Gift Entry is not for use with entering Matching Gifts, Reversals,
Modifications, Foreign Currency and iModules Encompass Gift transactions.
For additional information on Streamlined Gift and Pledge Entry, please refer to the Advance Gift and
Pledge User Guide.

Ellucian Advance | 9.9.0 Release Notes 35

Transaction List and Donor Transaction List
Previously, after drilling down on a transaction and returning to the Transaction List report in Gift
Batch Control, you would be returned to the top of the Transaction List report. In order to facilitate
more efficient review of transactions when drilling down on a transaction, the transaction now opens
in a separate tab. When returning to the Transaction List after drilling down on a transaction, the icon
of the last transaction selected will be highlighted, which enables you to more precisely and logically
view and drill-down on the transactions in the Transaction List.
Additionally, if System Option 192 was enabled, a Transaction List was displayed at the bottom of
Gift Batch Control. In addition to using System Option 192, this Transaction List now appears on the
Gift Batch Control Page Tree and is known as Transaction Donor List.
The following additional fields appear on the form in order to reduce having to drill-down to
see additional details: Appeal, Pledge Payment Indicator, Pledge Initial Payment Date, Pledge
Payment Frequency, Pledge Pay Amount, Tender Type, Check#, Anonymous Indicator, Open
Pledge Indicator.
The following transaction counts are displayed: # Transactions, Total Amount, Gift Total,
Gift Count, Pledge Total, Pledge Count, Matching Gift Total, Matching Gift Count and
Donor Count.
After drilling down on a transaction using the Transaction Donor List on the Gift Batch Control Page
Tree, the icon of the last transaction selected will be highlighted, which enables you to more precisely
and logically view and drill-down on the transactions in the Transaction Donor List. An Action menu
was also added to the Transaction List, which provides you with the ability to Sort, Filter, Print, and
Export the data on the form. These new features for Transaction List and Transaction Donor List
apply to classic gift and pledge entry as well as the new streamlined gift and pledge entry.

Keyboard Shortcuts
The following keyboard shortcuts were revised in order to support new browser versions, as indicated
in the Support section of this document. These keyboard shortcuts apply to all supported browsers.
Description Previous Shortcut New Shortcut

Accessing the Associated Donors Ctrl + O Ctrl + I

form during Gift and Pledge
entry.

Accessing the Giving Codes form Ctrl + N Ctrl + U

during Gift, Pledge and Matching
Gift entry.

Accessing the Securities form Ctrl + T Ctrl + E

during Gift and Matching Gift
entry.

For a complete list of keyboard shortcut utilized by Gift and Pledge, please refer to the Advance Gift
and Pledge User Guide.
For a complete list of system keyboard shortcuts, please refer to the Advance Navigation Guide.

Ellucian Advance | 9.9.0 Release Notes 36

Matching Gift Receipt Number on Matching Gift Entry
The Matching Gift Receipt # field was added to the Match Donor Gift form in order to allow you to
view the number during Matching Gift Entry. Previously, this number was only visible on the Batch
Proof Report. The new field appears during matching gift entry of the match donor gift information.
When the information is saved, the number appears in inquiry only.

Ellucian Advance | 9.9.0 Release Notes 37

Proposal ID Default on Pledge Payments
A new system option (system option 349) allows you to indicate whether you want the Proposal ID to
default into the Proposal field when making a payment on a pledge. When this system option is
enabled and you make a payment on a pledge that is linked to a proposal, the Proposal ID will
automatically appear in the Proposal ID field.
By default this new system option is disabled, which means Proposal IDs linked to pledges will not
automatically default into this field when payments are made against those pledges. For information
on enabling system options, please refer to the Advance System Options Reference.

Ellucian Advance | 9.9.0 Release Notes 38

Soft Credit on Associated Donors List
In order to allow gift entry operators to view the Soft Credit amounts of associated donors without
needing to select each row in the list to view the amounts below in the detail record, the Soft Credit
amount was added to the list portion of the Associated Donors master detail form.

Ellucian Advance | 9.9.0 Release Notes 39

Transaction List Sort
New fields on the Sort Order prompt in the Transaction List allow you to sort the transaction list
using the donor's Preferred Name Sort and/or Report Name. After transactions are saved in a batch
during gift entry, the transaction list can be accessed via the Page Tree. When the list appears,
selecting Sort from the Actions menu will yield the sort prompt. After you select the sort options in
the Sort Order - Batch Gift Entry List by dragging them from the left side of the prompt to the right
side of the prompt, click OK and the transactions in the list will appear in the new specified order.

Ellucian Advance | 9.9.0 Release Notes 40

Associated Donor Information in Pledge Drop-Down
When entering a pledge payment, the Pledge drop-down now includes additional donor information
that indicates the donor's association to the pledge. This includes whether the association is primary,
joint, covering account, group, etc. This new functionality aims to assist gift entry operators in
determining which pledge to select, in the event there are multiple pledges for the donor, and thus
decrease the likelihood of selecting the incorrect pledge.

Ellucian Advance | 9.9.0 Release Notes 41

Receipt Date Added to One-Line - Simple Transaction List
In order to allow users to more easily reconcile giving information when communicating with donors,
the One-Line - Simple Transaction List was enhanced to include the Receipt Date for all financial
transactions (Gifts, Pledges, Matching Gifts, Pledge Payments, etc.). When you access the Giving
Summary form and select Views from the Giving branch of the Page Tree, the One-Line - Simple
Transaction List can be selected from the Views form. When the transaction list appears, the new
Receipt Date field appears directly to the right of the Credit Amount field.

Ellucian Advance | 9.9.0 Release Notes 42

Prevention of a New Pledge Payment to the Pledge in the
Same Batch as the Pledge Modification
Advance now prohibits the entry of a new Pledge Payment to the Pledge in the same batch as a
modification to that pledge. This validation aims to decreases the likelihood of incorrect payment
schedules.

Ellucian Advance | 9.9.0 Release Notes 43

Prevention of Duplicate Matching Gifts
A new warning message prevents the entry of duplicate matching gifts that contain the same
Organization ID and Check #. If you enter a matching gift for an organization with a check number,
then attempt to add a second matching gift for the same organization with the same check number,
Advance will display a warning message that the check number is already assigned to an existing
Matching Gift Number.
If you accidentally attempt to add the same information twice, Advance will yield the warning and the
Organization ID will be removed from the Matching Gift Details form. This means you must re-enter
the Organization ID, then select the correct Matching Gift # from the drop-down and complete entry
of the matching gift transaction before submitting it for processing.

Ellucian Advance | 9.9.0 Release Notes 44

Prospect Tracking Improvements

Contact Report Sort on Tasks

Previously, the Contact Report drop-down on Task forms (Entity Tasks, Prospect Tasks, Proposal
Tasks, Program Prospect Tasks, Program Proposal Tasks and Contracts and Grants Tasks) sorted the
list of available Contact Reports using the Report ID. This made it difficult to view, locate and select
the correct Contact Report when multiple contact reports were available for selection.
Effective with Advance 9.9.0, the Contact Report drop-down on all of the aforementioned task forms
sorts in date order by the Contact Report Date, with the most recent Contact Reports at the top of the
list.

Ellucian Advance | 9.9.0 Release Notes 45

Prevention of Duplicate Assignments
Effective with Advance 9.9.0, a staff member can have multiple assignments per assignment type, per
entity, as long as one and only one status per assignment type is active. This validation applies to the
various types of assignments include Entity, Prospect, Proposal, Program and Program Proposal
Assignments.
This error message aims to alert the data entry operator that the information must be reviewed for
accuracy and either corrected or deleted before the record can be saved. If a new active record is
being added, the old record with the same assignment Type can be changed to Inactive by unchecking
the Active check box. Since only one active record can exist per staff member and assignment type,
un-checking the Active check box will allow you to retain all historic rows, while ensuring only the
current row has the Active check box checked.

Ellucian Advance | 9.9.0 Release Notes 46

Membership Improvements

Membership and Dues Payment Summary Navigation

The following navigation refinements aim to streamline the process of locating and viewing
membership summary information.
Dues Payment The Dues Payment form in the Dues Payment Profile application now
includes a link directly to the Membership.

The Payments form in the Membership Profile application now includes the Payment ID
field, along with the ability to drill-down to the Dues Payment Detail.

Ellucian Advance | 9.9.0 Release Notes 47

Prevention of Duplicate Memberships
New functionality in Membership Entry prevents you from entering the same membership, for the
same entity. A duplicate membership is defined as one that has the same ID Number, Membership
Type, Rate, Payment Plan, and Start and Stop dates as an existing membership.
If you attempt to add a duplicate membership, reversal or modification, a duplicate entry error will
appear at the top of the form when you click Save. This type of error will occur regardless of whether
the duplicate entry is in the same batch, a different unprocessed batch, or whether the other
transaction was previously processed.
This validation occurs for both Standard Membership Entry and Fast Key Membership Entry (via
System Option 334).

This error message aims to alert the membership entry operator that the membership information
must be reviewed for accuracy and either corrected or deleted before the batch can be closed and
submitted for processing. Membership entry operators cannot proceed until the necessary action is
taken when this scenario occurs.

Ellucian Advance | 9.9.0 Release Notes 48

Lookup Improvements

Gift, Pledge and Matching Gift Lookup Additions

For consistency purposes, the following fields were added to the Gift, Pledge and Matching Gift
lookups.

Gift Lookup:
Batch #
Check #
Reference 1
Reference 2

Matching Gift Lookup:

Reference 1
Reference 2

Pledge Lookup:
Anticipated Match Amount
Batch #
Reference 1
Reference 2

Gift-Transaction Template Lookup:

Batch #
Check #
Reference 1
Reference 2

Associated Code Renamed on Gift Lookup

The Associated Code label on the Gift Lookup was renamed from Code to Associated Code in order
to help identify the field.

Ellucian Advance | 9.9.0 Release Notes 49

System Improvements

Upgrade Planner
The Upgrade Planner is an adjunct utility for Ellucian Oracle database applications that generates
information about the cumulative set of changes that would occur in the application database between
the current site release of a product and a later target release.
The Upgrade Planner analyzes the data dictionary and source code of the current site product release,
and compares it to a data set of information about the data dictionary and source code of a chosen
target release of the product. The Planner looks at the data dictionary and in-database source code. It
does not analyze other application artifacts such as out-of-database source code artifacts, or
application server mid-tier artifacts.
This analysis identifies all new tables and views, changed tables and views, new other schema objects
and any source code objects (functions, packages, procedures, types) that have non-trivial changes in
their source. In addition, the Upgrade Planner identifies all site-specific tables and views, site-specific
additions to a product baseline table or view, and site-specific other schema objects, such as
functions, packages, or procedures.
The Upgrade Planners purpose is to aid institutions and organizations in the process of planning for
an upgrade of an Ellucian product, by providing comprehensive information about the database
changes that would be expected in an upgrade, without the need to download or install any of the
upgrade releases.
Institutions and organizations can use the information created by the Upgrade Planner to guide and
focus their efforts in implementing an upgrade to an Ellucian product.
For additional information, please refer to the Upgrade Planner Installation Instructions and User
Guide.
The Ellucian Support Center contains the pieces required by the Upgrade Planner installation, which
are separate from the Advance installation. If you have any questions, please contact
[email protected] prior to beginning the Upgrade Planner installation.

Go To
Previously, when you accessed the Go To application the ID (entity, prospect, program, proposal,
allocation, etc.) that was most recently accessed appeared in the Open with ID field. This occurred in
order to allow you to easily navigate to a different application for the same ID. This behavior
occurred regardless of whether you had an application open with a different ID in context and
regardless of whether any applications (tabs) were open. Effective with Advance 9.9.0, the Open with
ID field in the Go To application will default the ID of the current and active application (tab). If no
applications are open, an ID will not default into the Open with ID field.

Ellucian Advance | 9.9.0 Release Notes 50

Audit Information
Audit Information, accessible via the Actions Menu, allows you to view information that indicates
when the current record was first added, most recently updated, the name of the operator that most
recently updated the record and the user group associated with the user that most recently updated the
record. Effective with Advance 9.9.0, Audit Information now includes the full name of the operator in
addition to their username. Previously only the username displayed.

Prior to Advance 9.9.0:

Effective with Advance 9.9.0:

When Advance displays the Audit Information, it retrieves the full name from the users record
(zz_user.name). If the Name of the operator doesnt exist, because the user record was deleted from
zz_user instead of being inactivated for historical purposes, the text username not found will appear
in lieu of the Name.

Ellucian Advance | 9.9.0 Release Notes 51

 Both the full name of the operator (Name) and their username (User Name) are stored in the Users
Security window in the Advance Configuration Utility. Once a user is added their User Name cannot
be modified. The Name can be maintained by authorized personnel, per the rules of your institution or
organization. If a user leaves your institution or organization, the recommendation is to inactivate
their user record by un-checking the Active check box, and not to delete the user record in order to
retain audit information.

Ellucian Advance | 9.9.0 Release Notes 52

DataLoader Improvements
Advance 9.9.0 includes the following improvements to DataLoader.

Display Current Telephone for Add operations

If an entity has an existing telephone row of the same type that is being added, DataLoader will
display the current telephone in the Current column when viewing an individual Add transaction. If
there is more than one row that qualifies, DataLoader will display the one that is preferred, if the
preferred telephone is of the same type. If not, DataLoader will display the most recently maintained
telephone row of that type.

Select Telephone for All Telephone Types

While viewing a telephone transaction (Add, Mod, Delete) a new Select Telephone menu item
appears in the Actions menu. Selecting this action displays a list of active phone numbers that can be
used to replace the one displayed in the Current column.

Display Current Email for Add Operation

If an entity has an existing email row of the same type that is being added, DataLoader will display
the current email in the Current column when viewing an individual Add transaction. If there is
more than one row that qualifies, DataLoader will display the one that is preferred, if the preferred
email is of the same type. If not, DataLoader will display the most recently maintained email row of
that type.

Select Email for all Email Types

While viewing an email transaction (Add, Mod, Delete), a new Select Email menu item appears in the
Actions menu. Selecting this action displays a list of active emails that can be used to replace the one
displayed in the Current column.

Display Primary Employment for Add Operation

If an entity has a primary employment row, it will display in the Current column when viewing an
individual Add transaction.

Ellucian Advance | 9.9.0 Release Notes 53

New System Option to Link Address and Employment
When System Option 380, Link Business Address and Employment in DataLoader, is turned on, and
there is an Add transaction for a business address and an Add transaction for an employment row for
the same entity in a single batch, DataLoader will link the two of them together automatically. This
works for bulk posting and single transactions if the employment row is posted after the address row.

Batch Status with Errors after Posting

The DataLoader Batch Maintenance form allows you to maintain the details of a batch. Processed
with Errors is an existing, system-delivered and system-required DataLoader Batch Status, which
appears in the Status drop-down. Effective with this release, upon the completion of a single or bulk
posting operation, if there are any Active or Deferred transactions that have non-warning errors, the
status of the batch will be automatically changed to Processed with Errors. The batch will remain at
that status until you manually change it to something else, or the batch status becomes Complete (all
non-Discarded transactions are posted).

Override a Duplicate Entity Error

System Option 57, Use Enhanced Entity Duplicate Check for DataLoader, is used to detect name
collisions when adding new Entities in DataLoader. This prevents a duplicated entity from being
added. Effective with this release, a new check box named Override Duplicate Name allows you to
override this behavior on a transaction-by-transaction basis. If a duplicate is detected and the check
box is checked, the validation based on option system option 57 will be skipped for that transaction
and the entity will be added. This allows you to proceed with the load process and not have to return
later after youve disabled system option 57 in order to load the transactions, as in previous releases.

Ellucian Advance | 9.9.0 Release Notes 54

Gift/Pledge Loader Improvements
This section describes changes to Gift/Pledge Loader.

Auto Claim Received Functionality

Gift/Pledge Loader was enhanced and now supports the creation of matching claims when the donor
works for a matching gift company.

Configuration Utility Improvements

This section describes changes to the Advance Configuration Utility.

Forms and Controls Maintenance

The Database field in the Forms and Controls Maintenance window is now a required field. If you do
not select a value, ora_foo will be selected for you when you click Save.

Ellucian Advance | 9.9.0 Release Notes 55

iModules Encompass Connector Improvements

Recurring Pledges/Payments & Perpetual Giving

The Encompass Connector, for pushing and pulling data to-and-from Advance, was enhanced to
include new functionality that allows you to transfer recurring and perpetual gift information from
Encompass to Advance. Recurring and perpetual gifts allow donors to contribute an amount that's
paid on a regular basis.

Recurring Gifts
Encompass allows donors to establish recurring gift transactions by entering a specific amount and
indicating they want to spread the payments out over a specified period of time. When a donor
submits this type of gift, and the Encompass Connector is initiated to pull data from Encompass to
Advance, Encompass will send Advance an initial recurring gift transaction, and subsequent
transactions when each future payment is made.
When the initial transaction is pulled from Encompass, Advance will recognize the initial recurring
transaction and create a close-ended pledge with a corresponding initial payment and an applicable
payment schedule based on the amount and frequency specified by the donor. Some of the attributes
of the pledge, including the type of pledge assigned to the transaction, will depend on the settings of
system option settings, which are discussed in the system option sections below.

Perpetual Gifts
Encompass allows donors to establish perpetual gift transactions by entering a specific amount and
frequency. Whereas recurring gifts include information that specifies an amount of time for the gift
that leads to a close-ended schedule with an end date, perpetual gifts do not include an end date and
can be treated in a number of ways in Advance. When a donor submits this type of gift, and the
Encompass Connector is initiated to pull data from Encompass to Advance, Encompass will send
Advance an initial perpetual gift transaction, and subsequent transactions when each future payment
is made.
When a perpetual gift is pulled to Advance, you have the following options in regard to how to handle
the transaction:
Process the transaction as an open-ended pledge, with no expiration date. The pledge will
remain open until further notice.
Process the transaction as a close-ended pledge, with an expiration time specified by your
institution.
Process the transaction as a straight gift.

For additional information on Recurring Gift and Perpetual Gift Transactions, please refer to the
Advance Encompass Connector Reference.

Ellucian Advance | 9.9.0 Release Notes 56

 System Option Setup
The following system options are utilized by the recurring gift and perpetual gift functionality and
must be setup prior to pulling transactions from Encompass to Advance. For additional information
on system options, please refer to the Advance System Option Reference.

System Title Default Value

Option

360 Recurring Gift Pledge Type blank

361 Recurring Gift Pledge Payment Type blank

362 Perpetual Gift Processing Option 0

363 Perpetual Gift Close-Ended Pledge Length 0

364 Perpetual Gift Open-Ended Pledge Type blank

365 Perpetual Gift Pledge Payment Transaction Type blank

366 Perpetual Gift Org Defined Close-Ended Pledge Type blank

367 Perpetual Gift Gift Transaction Type blank

TMS Setup
In addition to the various system options utilized by the Recurring and Perpetual Gift functionality
described above, two TMS views, TMS Pledge Type (tms_pledge_type) and TMS Transaction Type
(tms_transaction_type), are relied upon heavily in order to enable this functionality. Please refer to
the Advance Encompass Connector Reference for a sample transaction type and pledge type setup.

Ellucian Advance | 9.9.0 Release Notes 57

Encompass Connector and Web Services 2.1
Ellucian is now providing a new connector that utilizes Web Services 2.1 due to iModules planned
retirement of Web Services 2.0. This is necessary in order to provide institutions and organizations
using Advance and the Encompass Connector the ability to upgrade to a new connector while
decreasing the likelihood of a service interruption when iModules officially retires Web Services 2.0.

Institutions and organizations that are using the Encompass Connector are strongly encouraged to
upgrade to Advance 9.9.0 as soon as possible in order to utilize the new Connector and Web Services
2.1. Failure to upgrade to Advance 9.9.0 and the Advancement Connector on Web Services 2.1 in a
timely manner will increase the likelihood of a service interruption in the event that iModules
officially announces a de-support date for Web Services 2.0 that doesnt meet your schedule. Please
contact your iModules representative for additional information on the timing of iModules planned
de-support of Web Services 2.0.

Note

In addition to Advance 9.9.0, the Encompass Connector that utilizes Web Services
2.1 is also available for use with Advance 9.8.1.1 and 9.8.2.2. If you wish to use the
Encompass Connector with either of these versions of Advance, please make sure
you download the applicable Encompass Connector from the Ellucian Client Support
Center.

For additional information on installing the Advancement Connector for Advance 9.9.0 that
runs on Web Services 2.1, please refer to the Advance Encompass Connector Administration
and Installation Guide.
For additional information on installing Advance 9.9.0, please refer to the Advance 9.9.0
Installation Instructions.
For additional information on upgrading your Advance database to Advance 9.9.0, please
refer to the Advance 9.9.0 Database Installation Instructions.

Automatically Archiving Push Details

Depending on the volume of records pulled from Encompass to Advance, it is possible that the
Advance database tables that contain the records from Encompass can grow quite large very quickly.
In order to assist institutions in the cleansing of historical data, a new database table,
data_transfer_push_archive, is utilized by a new automated process that archives records. When a
new transfer is initiated, records will be automatically archived from the data_transfer_push_detail
table to the new data_transfer_push_archive table with no user intervention.

Ellucian Advance | 9.9.0 Release Notes 58

Multi-Allocation Gifts and Pledges
As with one-time gifts, Advance allows single and multiple allocation transactions that originated in
Encompass. Since institutions process multiple gift transactions in several distinct ways, either as a
single transaction with multiple allocations or a single transaction for each allocation, Advance allows
for each of these scenarios by allowing you to set system option 368 to meet the needs of your
institution.
When this system option is disabled, Encompass transactions (One-time Gifts, Recurring Gifts and
Perpetual Gifts) with multiple allocations will be processed in Advance as one transaction with
multiple allocations. When this system option is enabled, transactions will be split between multiple
transactions.
For additional information, please refer to the Advance Encompass Connector Reference.

Donor Allocation Instructions

Included in the additional information pane in the Gift Entry Ledger is a section that displays
comments about the donor's wishes on how they want their donation applied. This is useful for donors
that want to make a donation to an allocation or allocations that are not available on the Encompass
campaign form.
In order to allow donors entering one-time, recurring, and perpetual gift transactions that have a mix
of allocation information or when a donor doesnt specify an allocation code, Advance system option
369 provides you with the ability to specify a stand-in allocation code. This temporary stand-in
allocation code will be automatically associated with a transaction when a donor enters instructions
instead of selecting an allocation in Encompass during transaction entry. Advance batches that
contain this temporary allocation code on any transaction in the batch cannot be closed. During
review of the transaction in the gift entry ledger, the gift entry operator must select the appropriate
allocation code(s) in order to close the batch and submit it for processing.

Duplicate Transactions Pulled from Encompass

Prior to this release of Advance, when a transaction was identified as being previously pulled from
Encompass, these duplicate transactions would be created in a duplicate transaction batch. With this
release, System Option 370 allows you to control how Advance will handle duplicate online
transactions and either output these transactions to a report or place them in a duplicate transaction
batch. When using the report output option, the online report can be accessed on the Gift Batch Page
Tree.

Gift Batch Separation

The Encompass Connector was enhanced to include new functionality that allows you to create
separate gift batches based on the Campaign ID, Gift Type, In Honor/In Memory/Joint, and dollar
threshold values. System Options 371-374 control whether separate batches are created.

Ellucian Advance | 9.9.0 Release Notes 59

Display of Additional Encompass Online Transaction
Information
With Advance 9.9.0, a new form is available on the Gift Profile and Pledge Profile that displays
Online Transaction information. Additionally, Joint Donor, Matching Company, In Honor/In
Memory information, Billing Information and Allocation Request data coming from Encompass will
be displayed in the Right Pane in the Gift Ledger when reviewing transactions pulled from
Encompass.

Online Giving Report

A new Online Giving Report is available from the Reports Menu for reconciling online transactions
processed in Advance with reports you receive from your financial institution.

Support Changes
This section highlights changes to support and compatibility for Advance 9.9.0.
For a complete list of non-Ellucian platforms and operating environments that Advance 9.9.0 was
tested against, please refer to the Support section of this document. For a complete list of Ellucian
applications that were tested with, and are compatible with Advance 9.9.0, please refer to the
Compatibility section of this document.

Advance Windows, AdvLoader, Advance Web Community and

Advance Web Reporting
Advance 9.9.0 is available for use on the Web via a browser. The Advance Windows client
application is not available. In conjunction with this change, the Advance Loader (AdvLoader),
Advance Web Community (AWC) and Advance Web Reporting (AWR) applications are also no
longer available.

Product Name Change

In conjunction with the aforementioned change for the various Advance suite products (Advance
Windows, AdvLoader, AWC and AWR), the Advance product was officially renamed from Advance
Web to Advance.
Previously, the distinction between Advance Windows and Advance Web was necessary in order
alleviate any confusion between the two platforms. Since Advance is now only available on the Web,
all references in the product and end-user product documentation were changed from Advance Web
to Advance, and from this point forward effective with Advance 9.9.0, unless specifically noted
otherwise, all references to Advance are for the browser based version of the product. All product
documentation refers to the product as Ellucian Advance on the cover page, while all other references
in the documentation will refer to the product as Advance. Please see the Documentation Changes
section below for additional documentation considerations.

Ellucian Advance | 9.9.0 Release Notes 60

 Upgrade Considerations
Before proceeding with the upgrade to Advance 9.9.0, please read and make sure you understand the
following information. If you have any questions, please contact [email protected] prior to
initiating the upgrade to Advance 9.9.0.
Institutions and organizations using a previous version of Advance Windows, AdvLoader,
AWC or AWR can continue to use their current versions of these products. However, since
no versions of these products are compatible with Advance 9.9.0, institutions and
organizations using any of these products, regardless of previous version, have two options:
o Upgrade to Advance 9.9.0 and use Advance without Advance Windows, AdvLoader,
AWC or AWR. Institutions that chose this option will no longer be able to use
Advance Windows, AdvLoader, AWC or AWR once the upgrade to Advance 9.9.0 is
complete. For a list of valid upgrade paths, please refer to the section of this
document entitled Database Installation Overview on p.16.
o Stay on the currently installed version of Advance (with Advance Windows,
AdvLoader, AWC and AWR) and do not upgrade to Advance 9.9.0. Institutions in a
hybrid environment using both Advance platforms (Web and Windows) that wish to
stay in a hybrid environment cannot upgrade to Advance 9.9.0 since Advance 9.9.0
is only available for use on the Web.
Institutions using Advance without Advance Windows, AdvLoader, AWC or AWR can
upgrade to Advance 9.9.0 at their discretion. For a list of valid upgrade paths, please refer to
the section of this document entitled Database Installation Overview on p.16.

Documentation Changes
The following documentation revisions were made in conjunction with these changes to support and
compatibility with Advance Windows, AdvLoader, AWC and AWR:
1. Advance Configuration Utility User Guide Functionality specific to these products was
removed. If an item remained because it was earmarked for removal at a future time, the
document was updated to indicate the item is no longer used and will be removed in a future
release. Changes made to the Advance Configuration Utility User Guide will be applied to the
Advance Configuration Utility Online Help in a future release.
2. Advance TMS User Guide Functionality specific to these products was removed. If an item
remained because it was earmarked for removal at a future time, the document was updated
to indicate the item is no longer used and will be removed in a future release.
3. Advance System Options Reference The descriptions of system options earmarked for
removal at a future time were updated to indicate the system option is obsolete as of Advance
9.9.0 and will be removed in a future release. The Advance TMS User Guide was also
updated to reflect which system options are obsolete and are earmarked for removal in a
future release.
4. Advance Data Elements Documents The descriptions of fields and tables earmarked for
removal at a future time were updated to indicate they are obsolete as of Advance 9.9.0 and
will be removed in a future release. While these items are identified in the Data Elements

Ellucian Advance | 9.9.0 Release Notes 61

 documents, these items are not noted on the Data Models. Any changes noted in the Data
Elements document also apply to the applicable Data Model counterpart.
5. Shared documentation Several documents, including all of the documents listed above,
were considered shared because they were available to users of both Advance Windows and
Advance Web. Since Advance is now only available for use on the Web, all shared
documents were renamed (filename) to include the Advance prefix. Additionally, all Advance
Windows-specific information was removed from these documents.
6. All other documents All product name references in the end-user product documentation
were changed from Advance Web to Advance and all Advance Web-specific documents were
renamed (filename) to include the Advance prefix, not the Advance Web prefix.

Advance Configuration Utility Changes

Since Advance Windows, AdvLoader, AWC and AWR are not supported for use with Advance 9.9.0,
all of the applicable windows in the Advance Configuration Utility that supported these products
were removed.
The Advance Configuration Utility continues to serve as the tool to configure the numerous forms,
applications and pages used throughout Advance. The Advance Configuration Utility client
application is available and can be installed as in previous releases.

Table Management System (TMS) View Changes

Drop-downs throughout Advance are controlled by the Table Management System (TMS)
application. In order to ensure Advance 9.9.0 functions as expected due to the aforementioned change
in support to Advance Windows, AdvLoader, AWC and AWR, several TMS views that supported
these products were updated to either remove drop-downs specific to those applications, or earmarked
for removal at a future time. Changes earmarked for removal at a later time are noted in the Advance
TMS User Guide.

System Option Changes

System options that control the behavior of Advance Windows, AdvLoader, AWC and AWR
continue to display in the list of system options in the System Options window in the Advance
Configuration Utility. In order to ensure institutions and organizations dont unnecessarily spend time
and resources setting these system options that are no longer used, these system options display with
a category of Obsolete (zz_adv_sysoptions.category_name = Obsolete). These system options are
earmarked for removal at a future time and are noted as such in the Advance System Options
Reference.

Schema Changes
In addition to the view and system option changes mentioned above, numerous packages, procedures,
database tables, and new IDs entries that are unique to Advance Windows, AdvLoader, AWC and
AWR continue to reside in the Advance schema. These items are earmarked for removal at a future
time.

Ellucian Advance | 9.9.0 Release Notes 62

 Note

A new database table in Advance 9.9.0 (zz_deprecated_objects) lists all objects

(packages, procedures, tables, views, system options and new IDs) that are earmarked
for removal at a future release.

Event Management and Data Movement

Event Management is not supported for use with Advance 9.9.0. Data Movement, which allows you
to move data back-and-forth between Advance and Event Management, is also not supported for use
with Advance 9.9.0.

Encompass Connector with Tomcat 7 and Java 7

The Encompass Connector for Advance 9.9.0 includes compatibility with Tomcat 7 and Java 7 and
requires the following software:
Java 7, update 17 or later
Apache Tomcat 7.0.40 or later within version 7
Oracle JDBC Drivers for Database 11g, available from Oracle

Note

The Oracle JDBC drivers for Database 11g are included with the Encompass
Connector distribution.
For additional information on the Encompass Connector, please refer to the Advance Encompass
Connector Installation and Administration Guide.

Microsoft Exchange Server 2013

Microsoft Exchange Task and Calendar Integration functionality allows the entry of tasks in
Advance to automatically generate updates for a corresponding Microsoft Outlook calendar or task
entry. Tasks then continue to be synchronized between Advance and Outlook as changes are made in
either application. This functionality supports the use of Advance as the main data entry point for
tasks while providing flexibility for you to view or update the information in Outlook or Advance.
This integration also allows institutional personnel to work more efficiently and allows institutions to
accurately and completely capture the necessary statistics to measure the work being performed by its
personnel.
Effective with Advance 9.9.0, this functionality includes support for use with Microsoft Exchange
Server 2013, and continues to be available for use with Microsoft Exchange Server 2010. No
functional changes were made to Advance in order to support this new environment and Advance
9.9.0 functions in the same manner as previous releases.
Microsoft Exchange Server 2007 is no longer supported for use with the Advance Task and Calendar
Integration functionality.

Ellucian Advance | 9.9.0 Release Notes 63

Crystal Reports 2011 (64-bit)
Advance 9.9.0 introduces support for the Crystal Reports 2011 viewer (Crystal Reports for Visual
Studio 2010). The primary benefit of this version is the ability to run Crystal Reports in either 32-bit
or 64-bit mode. The Crystal Reports XI viewer is no longer supported.

Note

This new functionality applies to the Crystal Reports 2011 viewer, not Crystal Reports
2011 Server. Crystal Reports 2011 Server is not supported for use with Advance
9.9.0.
Before using Advance to view your reports, you must modify the Advance Web.Config file in order
to indicate you are using the Crystal Reports 2011 viewer. Instructions on how to indicate you are
using the Crystal Reports 2011 viewer can be found in the Advance 9.9.0 Installation Instructions.
Instructions for installing Crystal Reports are not provided by Ellucian. Please refer to your Crystal
Reports documentation for instructions on installing Crystal Reports.

Microsoft Internet Explorer 10 on Windows 7

Advance 9.9.0 introduces support for Microsoft Internet Explorer 10 when Windows 7 is the
Operating System. Advance 9.9.0 is not supported for use with Windows 8, regardless of the browser.

Adobe RoboHelp 10
Advance 9.9.0 introduces support for creating Site Help using Adobe RoboHelp 10. RoboHelp 9
is no longer supported.

Advance Mobile
Advance Mobile is a scaled down version of Advance. Since the iPad has a larger screen and is
capable of supporting the full version of Advance in the web browser as opposed to the scaled down
version included with Advance Mobile, the Advance Mobile platform is delivered disabled. This
means iPad users will never be re-directed to the Advance Mobile platform.
Since mobile support no longer includes any BlackBerry or Palm Treo versions and most iPad users
wish to use the full version of Advance through the browser as opposed to Advance Mobile, Ellucian
no longer supports the Advance Mobile platform. For the purposes of Advance, the iPad is no longer
considered a mobile device. However, Advance Mobile is still included with Advance and the web
forms used by Advance Mobile are disabled by default. This means iPad users that access Advance
on an iPad will not be re-directed to the Advance Mobile site. When Advance Mobile is enabled,
whether the re-direct occurs to the Advance Mobile site is determined by IIS on the Web Server
where Advance is installed. It is not determined by Advance.
Although the Advance Mobile platform is still included with Advance, Ellucian does not recommend
using the Advance Mobile platform on an iPad since it is no longer tested or supported. Instead,
Ellucian recommends keeping the platform disabled, which will allow iPad users to always access the
full version of Advance through a web browser. If the Advance Mobile platform is not disabled, users
that access Advance through the iPad might be automatically re-directed to the Advance Mobile

Ellucian Advance | 9.9.0 Release Notes 64

 platform, per IIS. If you wish to allow users to always use the web browser on the iPad to access
Advance, you should keep the Advance Mobile platform disabled at your institution.

iPad and Mac Operating System

Advance 9.9.0 introduces support for the following Apple operating systems:
Mac OS X 10.9 (Mavericks), for Macintosh
iOS 7.x, for iPad
Mac OS X 10.8.3 (Mountain Lion) for the Macintosh, and iOS 6.x for the iPad, are no longer
supported.

Sybase PowerBuilder
The Advance Configuration Utility 9.9.0 is supported on Sybase PowerBuilder 12.1, build 7217.
PowerBuilder 12.1, build 7000 is no longer supported.

Ellucian Advance | 9.9.0 Release Notes 65

Support

The following non-Ellucian platforms and operating environments were tested against, and are
supported for use with, Advance 9.9.0.

Browsers
Microsoft Internet Explorer9
Microsoft Internet Explorer 10
Mozilla Firefox 25
Safari 7 (Mac, iPad)
Google Chrome 31

Client Operating Systems

Windows XP Professional, SP2
Windows 7 Enterprise
Windows Vista Enterprise
Mac OS X 10.9 (Mavericks), for Macintosh

Note

Mac OS X 10.8.3 (Mountain Lion) is no longer supported

iOS 7.x, for iPad

Note

iOS 6.x is no longer supported

Databases
Oracle 11g (11.1.0.7.0)
Oracle 11g R2 (11.2.0.3.0)

Ellucian Advance | 9.9.0 Release Notes 66

Oracle Database Access Components (ODAC)

11.2 Release 4 (11.2.0.3.0) for Windows

11.2 Release 4 (11.2.0.3.0) for Windows x64

Note

XCopy installations must use EZCONNECT vs. tnsname.ora for server names.

Web Servers
Microsoft Windows Server 2008 Enterprise with IIS7 on 32-bit hardware
Microsoft Windows Server 2008 Enterprise with IIS7 on 64-bit hardware in 32-bit or 64-bit
mode
Microsoft Windows Server 2008 R2 Enterprise with IIS7.5 on 64-bit hardware in 32-bit or
64-bit mode
Microsoft .NET Framework v4.0

Online Help
Adobe RoboHelp HTML 10.0.0.287

Note

Adobe RoboHelp 9 is no longer supported.

Application Development
Microsoft Visual Studio 2010 SP1 (for Advance)
Sybase PowerBuilder Enterprise 12.1, Build 7217 (for the Advance Configuration Utility)

Note

The PowerBulder Reporting DLL utilizes Build 6518.

Ellucian Advance | 9.9.0 Release Notes 67

Other

Crystal Reports Server 2008 (32-bit only)

Crystal Reports .NET Runtime:
o Crystal Reports 2008 (32-bit only)
o Crystal Reports for Visual Studio 2010 (32-bit or 64-bit)

Note

Crystal Reports XI .NET Runtime is no longer supported.

Pubcookie, ISAPI filter support
LDAP, Version 3.0 Compliant
MKS 9.1.0100 (32-bit only)
Cygwin 1.7.9-1
Microsoft Office 2003, 2007, 2010
Microsoft Exchange 2010 and 2013

Note

Microsoft Exchange 2007 is no longer supported.

Freedom Scientific JAWS 14.0.6005 (32-bit)
Experian QAS Pro Web 5.64 plus QAS for Advance 9.3 v1.0 integration files
iModules Encompass, Production Version
ASPOSE 8.1.0
Active Directory Microsoft Server 2008 and 2008 R2
SunGard Bi-Tech IFAS 7.9 w/Patch
SunGard EXP MACESS 3.4 SP4
EMC Documentum ApplicationXtender (32-bit only)
o Client: ApplicationXtender Desktop 6.52.056
o Server: ApplicationXtender Desktop, License Server 6.52.045, Rendering Server
6.52.056, Web Access 6.52.056

Note

ApplicationXtender does not support documents saved in Microsoft Office 2007

or 2010 format; it does support documents saved in earlier formats, e.g.,
Microsoft Office 2003 via lowest common denominator approach.
Quick Scan Pro 4.7.0.8554 (optional)
Hosted Checkout Page and PayPal PayFlow Link

Ellucian Advance | 9.9.0 Release Notes 68

 CyberSource Hosted Order Page
Java SE Development Kit7 Update 17
Apache Tomcat 7.0.40

Ellucian Advance | 9.9.0 Release Notes 69

Compatibility

The following Ellucian applications were tested with, and are compatible with, Advance 9.9.0.

Note
As noted earlier in this document, Advance Windows, Advance Web Community, Advance Web
Reporting, AdvLoader, Special Events and Data Movement are not supported for use with Advance
9.9.0.

Advance Configuration Utility

Version 9.9.0 (in 32-bit mode on 32-bit and 64-bit hardware)

SmartCall / Advance Synchronization

Version 9.7.0
Version 9.6.0 (contact [email protected] for possible critical fixes)

SmartCall Integration Utility (SIU)

Version 3.8 (for SmartCall 9.6.0 and 9.7.0)

Pledge Integration Utility (PIU)

Version 2.9 (for SmartCall 9.7.0)

Version 2.8 (for SmartCall 9.6.0)

Site Help Integration Utility

Version 3.0

Ellucian Advance | 9.9.0 Release Notes 70

Advance Export (AdvExport)

Version 9.9.0

Banner Student

Version 8.5.6

Upgrade Planner

Version 1.0.1

Encompass Connector

Version 9.9.0

Ellucian Advance | 9.9.0 Release Notes 71

System-wide Changes

Database Tables and Indexes

This section lists schema changes in Advance 9.9.0.

Table Changes
This section lists all table changes in Advance 9.9.0.
Key
new column Indicates the column(s) listed below are new to the table.
new table Indicates the entire table is new.
increased size Indicates the column increased in size. In these occurrences, the new
and old sizes are listed.
decreased size Indicates the column decreased in size. In these occurrences, the new
and old sizes are listed.

null/not null Indicates whether the column accepts a null value.

obsolete column Indicates the column is no longer used in the table.
obsolete table Indicates the table is no longer used.
renamed column Indicates the column name changed. In these occurrences, the new and
old names are listed.

address (new columns)

latitude varchar2(11) null
longitude varchar2(12) null
geocode_geometry mdsys.sdo_geometry null
geocode_address sdo_geo_addr null
geocode_failure_ind char(1) not null
geocode_quality varchar2(100) null

batch_control (new columns)

campaign_id_batch number(5) null
st_pp_batch char(1) null
ih_im_j_batch char(1) null
amt_threshold_batch varchar2(20) null

Ellucian Advance | 9.9.0 Release Notes 72

 streamlined_gift_ind char(1) not null
gift_ind char(1) not null
pledge_ind char(1) not null
transaction_reference varchar2(10) not null
transaction_reference2 varchar2(10) not null
prp_project_code varchar2(15) not null
transaction_anonymous char(1) not null
transaction_comment varchar2(255) not null
credit_card_type varchar2(2) not null
sponsorship_amt number(14,2) not null
binding_ind char(1) not null
recordable_ind char(1) not null
pledge_status char(1) not null
discounted_amt number(14,2) not null
reminder_addr_type varchar2(2) not null
alloc_dept_code varchar2(7) not null
alloc_division varchar2(7) not null
alloc_school varchar2(4) not null
premium_declined_ind char(1) not null
premium_code varchar2(5) not null
premium_amt number(14,2) not null
premium_xcomment varchar2(255) not null
giving_code_type char(1) not null
giving_code varchar2(20) not null
giving_code_amount number(14,2) not null
giving_codes_id_number varchar2(10) not null
giving_codes_id_name varchar2(60) not null
giving_codes_note_text clob null
giving_codes_comment varchar2(255) not null
tribute_type char(1) not null
tribute_id_number varchar2(10) not null
pay_date date null
giving_code_date date null

batch_control_defaults (new table)

batch_control_defaults_id number(10,0) not null
default_name varchar2(20) not null
default_description varchar2(60) not null
public_ind char(1) not null
active_ind char(1) not null

Ellucian Advance | 9.9.0 Release Notes 73

 gift_ind char(1) not null
pledge_ind char(1) not null
transaction_type varchar2(2) not null
pledge_type varchar2(2) not null
payment_type char(1) not null
appeal varchar2(15) not null
campaign varchar2(10) not null
allocation varchar2(16) not null
transaction_amount number(14,2) not null
reunion_campaign varchar2(6) not null
acknowledgment varchar2(3) not null
special_handling varchar2(3) not null
transaction_reference varchar2(10) not null
transaction_reference2 varchar2(10) not null
source_of_information varchar2(3) not null
prp_project_code varchar2(15) not null
transaction_anonymous char(1) not null
ledger_month_code varchar2(7 not null
reporting_code varchar2(2) not null
transmit_to_acctg_code varchar2(2) not null
transaction_comment varchar2(255) not null
cashier_tag varchar2(7) not null
check_number varchar2(10) not null
claim_form_received char(1) not null
credit_card_type varchar2(2) not null
charity_code varchar2(5) not null
sponsorship_amt number(14,2) not null
binding_ind char(1) not null
recordable_ind char(1) not null
payment_frequency char(1) not null
number_of_payments number(6,0) not null
pledge_status char(1) not null
discounted_amt number(14,2) not null
reminder_addr_type varchar2(2) not null
class_credit varchar2(4) not null
school_credit varchar2(4) not null
alloc_dept_code varchar2(7) not null
alloc_division varchar2(7) not null
alloc_school varchar2(4) not null

Ellucian Advance | 9.9.0 Release Notes 74

 program_credit_code varchar2(3) not null
purpose varchar2(5) not null
premium_declined_ind char(1) not null
premium_code varchar2(5) not null
premium_amt number(14,2) not null
premium_xcomment varchar2(255) not null
giving_code_type char(1) not null
giving_code varchar2(20) not null
giving_code_amount number(14,2) not null
giving_codes_id_number varchar2(10) not null
giving_codes_id_name varchar2(60) not null
giving_codes_note_text clob null
giving_codes_comment varchar2(255) not null
supervisor_operator varchar2(32) not null
supervisor_user_group varchar2(2) not null
supervisor_last_mod_date date null
owner_operator_name varchar2(32) not null
date_added date not null
date_modified date not null
operator_name varchar2(32) not null
user_group varchar2(2) not null
location_id number null

batch_gift_tender_type (increased size)

bg_valuation_amt from number(14,2) to number(18,6)
bg_revaluation_amt from number(14,2) to number(18,6)
bg_high_security_value from number(14,2) to number(18,6)
bg_low_security_value from number(14,2) to number(18,6)

campaign_agent_agent (increased size)

class_agt_code from varchar2(3) to varchar2(15)

data_transfer_push_archive (new table)

push_archive_id number(19,0) not null
thirdpty_column_name varchar2(100) not null
local_column_value varchar2(2000) null
transaction_id number(19,0) not null
id_number number(10,0) not null
batch_number number(19,0) null
concurrency_version number(19,0) not null

Ellucian Advance | 9.9.0 Release Notes 75

 data_origin varchar2(30) not null
date_modified date not null
operator_name varchar2(32) not null
location_id number null

email (new columns)

start _dt varchar2(8) not null
stop _dt varchar2(8) not null

entity (increased size)

class_agt_code from varchar2(3) to varchar2(15)

ep_participant (increased size)

prefix from varchar2(15) to varchar2(25)
suffix from varchar2(15) to varchar2(25)

geo_code (new columns)

geo_code_geometry mdsys.sdo_geometry null

gift_tender_type (increased size)

valuation_amt from number(14,2) to number(18,6)
revaluation_amt from number(14,2) to number(18,6)
high_security_value from number(14,2) to number(18,6)
low_security_value from number(14,2) to number(18,6)

gift_tender_type_reversal (increased size)

valuation_amt from number(14,2) to number(18,6)
revaluation_amt from number(14,2) to number(18,6)
high_security_value from number(14,2) to number(18,6)
low_security_value from number(14,2) to number(18,6)

imodules_download_gift (new columns)

location_id number null
pledge_batch_number varchar2(10) null)
billing_name varchar2(100) null
billing_email_address varchar2(320) null
billing_telephone varchar2(25) null
billing_last_four_digits varchar2(4) null
tribute_notify_prefix varchar2(25) null
tribute_notify_first_name varchar2(25) null

Ellucian Advance | 9.9.0 Release Notes 76

 tribute_notify_middle_namevarchar2(25) null
tribute_notify_last_name varchar2(25) null
tribute_notify_pers_suffix varchar2(25) null
tribute_notify_prof_suffix varchar2(25) null
tribute_notify_title varchar2(60) null
tribute_notify_addr_line1 varchar2(80) null
tribute_notify_addr_line2 varchar2(80) null
tribute_notify_addr_line3 varchar2(80) null
tribute_notify_city varchar2(50) null
tribute_notify_state varchar2(3) null
tribute_notify_zip varchar2(30) null
tribute_notify_country varchar2(50) null
allocation_instructions varchar2(4000) null
initial_transaction_id integer null
thirdpty_control_id number(5) null

imodules_download_gift_bk (new columns)

location_id number null
pledge_batch_number varchar2(10) null)
billing_name varchar2(100) null
billing_email_address varchar2(320) null
billing_telephone varchar2(25) null
billing_last_four_digits varchar2(4) null
tribute_notify_prefix varchar2(25) null
tribute_notify_first_name varchar2(25) null
tribute_notify_middle_namevarchar2(25) null
tribute_notify_last_name varchar2(25) null
tribute_notify_pers_suffix varchar2(25) null
tribute_notify_prof_suffix varchar2(25) null
tribute_notify_title varchar2(60) null
tribute_notify_addr_line1 varchar2(80) null
tribute_notify_addr_line2 varchar2(80) null
tribute_notify_addr_line3 varchar2(80) null
tribute_notify_city varchar2(50) null
tribute_notify_state varchar2(3) null
tribute_notify_zip varchar2(30) null
tribute_notify_country varchar2(50) null
allocation_instructions varchar2(4000) null
initial_transaction_id integer null

Ellucian Advance | 9.9.0 Release Notes 77

 thirdpty_control_id number(5) null

imodules_download_giftalloc (new columns)

batch_number varchar2(10) null
receipt_number varchar2(10) null
pledge_number varchar2(10) null
pledge_batch_number varchar2(10) null
alloc_xsequence integer null
allocation_pmt number(14,2) null
initial_transaction_id integer null
thirdpty_control_id number(5) null

imodules_download_giftalloc_bk (new columns)

batch_number varchar2(10) null
receipt_number varchar2(10) null
pledge_number varchar2(10) null
pledge_batch_number varchar2(10) null
alloc_xsequence integer null
allocation_pmt number(14,2) null
initial_transaction_id integer null
thirdpty_control_id number(5) null

ldr_batch_data (increased size)

col_21 from varchar2(2000) to varchar2(4000)

thirdpty_mail_control (increased size)

class_agent_id from varchar2(3) to varchar2(15)

yy_gp_gifts (increased size)

bg_high_security_value from number(14,2) to number(18,6)
bg_low_security_value from number(14,2) to number(18,6)

Ellucian Advance | 9.9.0 Release Notes 78

 yy_gp_matches_tender (increased size)
valuation_amt from number(14,2) to number(18,6)
revaluation_amt from number(14,2) to number(18,6)
high_security_value from number(14,2) to number(18,6)
low_security_value from number(14,2) to number(18,6)

zz_deprecated_objects (new table)

object_name varchar2(30) not null
object_type varchar2(20) not null
xcomment varchar2(300) null
drop_order number(5) not null

zz_gpl_gift_tender_type (increased size)

bg_high_security_value from number(14,2) to number(18,6)
bg_low_security_value from number(14,2) to number(18,6)

zz_mt_forms_controls (increased size)

control_data from varchar2(2000) to varchar2(4000)
control_field_name from varchar2(255) to varchar2(400)

zz_user (increased size)

domain_exchange_user_name from varchar2(25) to varchar2(60)

Ellucian Advance | 9.9.0 Release Notes 79

New Indexes
This section lists all new indexes in Advance 9.9.0.

Index Name Table Columns

batch_control_defaults_key0 batch_control_defaults batch_control_defaults_id

entm_ignore_tables_key0 entm_ignore_tables table_name

imodules_gift_bk_key2 imodules_download_gift_bk instance_id

imodules_gift_bk_key3 imodules_download_gift_bk receipt_number

imodules_gift_bk_key4 imodules_download_gift_bk transaction_id

imodules_gift_key2 imodules_download_gift instance_id

imodules_gift_key3 imodules_download_gift receipt_number

imodules_gift_key4 imodules_download_gift transaction_id

imodules_gift_key5 imodules_download_gift Initial_transaction_id

imodules_giftalloc_bk_key2 imodules_download_giftalloc_bk instance_id

imodules_giftalloc_bk_key3 imodules_download_giftalloc_bk receipt_number

imodules_giftalloc_bk_key4 imodules_download_giftalloc_bk transaction_id

imodules_giftalloc_key2 imodules_download_giftalloc instance_id

imodules_giftalloc_key3 imodules_download_giftalloc receipt_number

imodules_giftalloc_key4 imodules_download_giftalloc transaction_id

Ellucian Advance | 9.9.0 Release Notes 80

Modified Indexes
This section lists all modified indexes in Advance 9.9.0.

Index Name Old Columns New Columns

imodules_gift_bk_key0 imodules_download_gift_id imodules_download_gift_id

transaction_id transaction_id
instance_id instance_id
xsequence xsequence
initial_transaction_id
imodules_gift_key0 imodules_download_gift_id imodules_download_gift_id
transaction_id transaction_id
instance_id instance_id
xsequence xsequence
initial_transaction_id
imodules_download_giftalloc imodules_download_gift_id imodules_download_gift_id
_bk_key0
transaction_id transaction_id
instance_id instance_id
xsequence xsequence
allocation_code allocation_code
initial_transaction_id
imodules_download_giftalloc imodules_download_gift_id imodules_download_gift_id
_key0
transaction_id transaction_id
instance_id instance_id
xsequence xsequence
allocation_code allocation_code
initial_transaction_id

Ellucian Advance | 9.9.0 Release Notes 81

TMS Views
This section lists TMS view changes in Advance 9.9.0. For additional information on these views,
please refer to the Advance TMS User Guide.

New TMS Views

There are no new TMS Views in Advance 9.9.0.

Modified TMS Views

Modified views, in View Name order, along with their corresponding Table Codes and changes, are
as follows:

View Name Table Change

Code

tms_association IF New columns:

prim_donor_addl_allocs_sgl_ind
prim_donor_addl_allocs_mlt_ind
joint_donor_first_alloc_ind
joint_donor_addl_allocs_ind
multiple_donors_ind

tms_batch_type J1 New required value:

X Online Duplicate Transactions

tms_class_agt New maximum code length:

Increased from 3 to 15

System Options
This section contains information regarding system options changes in Advance 9.9.0. For a complete
list of system options and full descriptions, please refer to the Advance System Options Reference.

Ellucian Advance | 9.9.0 Release Notes 82

New Advance System Options
The following system options (zz_adv_sysoptions) are new in Advance 9.9.0.

System Title Default Value

Option

349 Default Proposal ID for Pledge Payment Transactions No

360 Recurring Gift Pledge Type blank

361 Recurring Gift Pledge Payment Type blank

362 Perpetual Gift Processing Option 0

363 Perpetual Gift Close-Ended Pledge Length 0

364 Perpetual Gift Open-Ended Pledge Type blank

365 Perpetual Gift Pledge Payment Transaction Type blank

366 Perpetual Gift Org Defined Close-Ended Pledge Type blank

367 Perpetual Gift Gift Transaction Type blank

368 Multiple Allocation Gift Processing Option No

369 Donor Defined Allocation blank

370 Duplicate Transactions Handling 0

371 Separate batch by Online Campaign ID. No

372 Separate batch by Gift Type No

373 Separate batch for In Honor/In Memory and Joint Donor No

374 Separate batch by Dollar Amount Threshold blank

375 Streamlined Gift Default No

376 Streamlined Gift Entry Tender Popup Box Yes

380 Link Business Address and Employment in DataLoader Yes

Ellucian Advance | 9.9.0 Release Notes 83

Defect Fixes

For a comprehensive and detailed list of defects resolved in this release, please refer to the
supplemental problem resolutions file (Advance_ 9_9_0_Resolutions.txt). The information in this file
is extracted directly from The Ellucian Support Center just prior to release of the product.
If you have any questions, please contact [email protected].

Ellucian Advance | 9.9.0 Release Notes 84