BANNER ADVANCEMENT RELEASE GUIDE. Release 8.4.1 June 2011

BANNER ADVANCEMENT RELEASE GUIDE Release 8.4.1 June 2011

Trademark, Publishing Statement and Copyright Notice SunGard or its subsidiaries in the U.S. and other countries is the owner of numerous marks, including SunGard, the SunGard logo, Banner, PowerCAMPUS, Advance, Luminis, DegreeWorks, fsaatlas, Course Signals, and Open Digital Campus. Other names and marks used in this material are owned by third parties. 2011 SunGard. All rights reserved. Contains confidential and proprietary information of SunGard and its subsidiaries. Use of these materials is limited to SunGard Higher Education licensees, and is subject to the terms and conditions of one or more written license agreements between SunGard Higher Education and the licensee in question. This PDF is certified for use with Adobe Reader, version 7.x and higher. Some elements of this PDF may not render properly when viewed using earlier versions of the Acrobat Reader or with other PDF viewing applications. In preparing and providing this publication, SunGard Higher Education is not rendering legal, accounting, or other similar professional services. SunGard Higher Education makes no claims that an institution's use of this publication or the software for which it is provided will insure 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: SunGard Higher Education 4 Country View Road Malvern, Pennsylvania 19355 United States of America Customer Support Center Website http://connect.sungardhe.com Documentation Feedback http://education.sungardhe.com/survey/documentation.html Distribution Services E-mail Address distserv@sungardhe.com Revision History Log Publication Date June 2011 Summary New version that supports Banner Advancement 8.4.1 software.

Banner Advancement 8.4.1 Contents Introduction........................................ 5 Section 1 imodules Encompass Integration - Functional Enhancements....................................................... 7 Scheduler......................................... 7 Scheduler tab....................................... 7 Adding a new scheduler record............................ 10 Modifying an existing scheduler record........................ 11 Deleting an existing scheduler record........................ 11 E-mail notification.................................... 11 Run History tab..................................... 12 Enhanced functionality for CSV file creation.................... 13 Processing and logic changes.............................. 13 Changes to the Initiation tab on AUAINIT....................... 15 Push and pull processing does not lock the AUAINIT form............ 15 Entry of end date and end time for push....................... 15 Running of push profile with update me value.................... 15 Best practice recommendations for Web Service pushes and CSV file creation.................................... 16 Use Web Service for incremental changes..................... 16 Use CSV file for large data sets............................ 16 Break up very large data sets into multiple files................... 17 Allocate sufficient memory to Java when writing large files............ 17 Section 2 imodules Encompass Integration - Technical Enhancements....................................................... 19 New table - Advancement Connector Scheduler Base Table (AUBSCHD).. 19 New connector properties............................... 20 June 2011 Banner Advancement 8.4.1 3 Contents

Section 3 Miscellaneous Enhancements - Functional....................... 23 Advancement Telemarketing Results Upload (AGPTLMK)........... 23 Constituent Identification view (AA_CONSTITUENT_IDENTIFICATION)... 23 Highlight alert for specific forms........................... 24 Modified triggers..................................... 24 Modified object...................................... 24 Section 4 Problem Resolutions................................................ 25 4 Banner Advancement 8.4.1 June 2011 Contents

Introduction This release guide describes the following enhancements: The addition of a new scheduling feature for the Advancement Connector Various form enhancements that have been made to the Advancement Connector forms Enhancements made to the Advancement Connector that address performance issues, specifically when very large CSV files were being created as the output format Miscellaneous enhancements Problem resolutions are summarized at the end of this release guide.the detailed description, impact, and resolution information for each problem resolution are delivered in a separate file named advanc80401resolutions.txt. June 2011 Banner Advancement 8.4.1 5

6 Banner Advancement 8.4.1 June 2011

1 imodules Encompass Integration - Functional Enhancements This section provides information on the functional enhancements made to Banner Advancement 8.4.1. Scheduler Banner Advancement 8.4.1 provides enhanced functionality for scheduling the transfer of data between Banner and imodules s Encompass product. This new functionality allows your institution to set predefined schedules for the automatic running of push and pull profiles. These Scheduler records then automatically initiate these runs at the requested dates and times, relieving your staff of having to initiate them manually. Scheduler tab The Scheduler tab is used to add, modify, and delete Scheduler records. This tab includes the following fields: Fields Active Profile Type Profile Code Descriptions Check box to indicate whether the scheduler record is active or inactive. This check box is unchecked by default. Selecting this field indicates that this scheduler record should be effective immediately. The Scheduler functionality would then automatically initiate the push or pull profile at the frequency indicated on the Scheduler record. Indicates whether the data transfer is pushing data from Banner to Encompass or pulling data from Encompass to Banner. Profile that should be used for data transfer. If the Profile Type is Push, only Push profiles are displayed. If the Profile Type is Pull, only Pull profiles are displayed. You can select the code from the list of values. June 2011 Banner Advancement 8.4.1 7 imodules Encompass Integration - Functional Enhancements

Fields Frequency Start Time Selection Begin Date Selection Begin Time Descriptions Desired frequency. You can select the frequency as daily or weekly from the dropdown list. The data elements displayed for frequency will vary based on the frequency selected. If you select the Daily frequency, the Exclude Weekends check box is displayed. Select or deselect the check box as per your requirement. If you select the Weekly frequency, check boxes for all the days in a week (Sunday to Saturday) are displayed. You can select the appropriate check boxes to indicate on which days you want the Scheduler record to be initiated. Time the scheduler initiates the push or pull. Use the HHMM format with valid values 0000 through 2359. For example, if the start time is 10:30 PM, enter 2230. Date that should be used for the initial run of this data transfer to select qualifying records to be pushed or pulled. If the user modifies the value in this field, the system automatically removes any values in the Last Successful Run Date and Time fields. Changes to the value in this field are considered a re-initialization of this Scheduler record. Time that should be used for the initial run of this data transfer to select qualifying records to be pushed or pulled. Use the HHMM format with valid values 0000 through 2359. If the user modifies the value in this field, the system automatically removes any values in the Last Successful Run Date and Time fields. Changes to the value in this field are considered a re-initialization of this Scheduler record. 8 Banner Advancement 8.4.1 June 2011 imodules Encompass Integration - Functional Enhancements

Fields Last Successful Run Date Last Successful Run Time User Activity Date Notification Email 1 Notification Email 2 Notification Email 3 Notification Email 4 Descriptions Last date when this profile was initiated successfully by this scheduler record. This field is display only. Each time a push/pull request is successfully initiated by this Scheduler record, the Last Successful Run Date and Time fields are populated. These values are then used as the Selection Begin Date and Time parameters for the subsequent push/pull requests for this Scheduler record. The Last Successful Run Date for a scheduler record reflects both the manual and the scheduled runs. When the user manually initiates a push or a pull request and it is completed successfully, the Last Successful Run Date for the scheduler record for this profile is updated. Last time when this profile was initiated successfully by this Scheduler record. This field is display only. Each time a push/pull request is successfully initiated by this Scheduler record, the Last Successful Run Date and Time fields are populated. These values are then used as the Selection Begin Date and Time parameters for the subsequent push/pull requests for this Scheduler record. The Last Successful Run Time for a Scheduler record reflects both the manual and the scheduled runs. When the user manually initiates a push or a pull profile and it is completed successfully, the Last Successful Run Time for the Scheduler record for this profile is updated. User who last maintained this record. This field is display only. Date when the record was last modified. This field is display only. The first e-mail that should be automatically notified when this scheduled job is executed. This field is optional. See the E-mail notification on page 11 section for additional details on this functionality. The second-mail that should be automatically notified when this scheduled job is executed. This field is optional. The third e-mail that should be automatically notified when this scheduled job is executed. This field is optional. The fourth e-mail that should be automatically notified when this scheduled job is executed. This field is optional. June 2011 Banner Advancement 8.4.1 9 imodules Encompass Integration - Functional Enhancements

Adding a new scheduler record You can add one Scheduler record per profile. This Scheduler record is either active or inactive. You are not allowed to add another Scheduler record for the same profile. If you try this, you get the following error message: *ERROR* Only one scheduler record for a profile is allowed. Use the following steps to add a new Scheduler record for a profile and initiate it from the Scheduler tab. 1. Access the Advancement Connector Initiation Form (AUAINIT). 2. Select the Scheduler tab. 3. Select Insert from the Record menu. 4. Indicate whether the Scheduler record is active or inactive. 5. Select a profile type from the Profile Type drop-down list. 6. Select the profile code from the Profile Code drop-down list. 7. Select the frequency from the Frequency drop-down list. 8. Enter the time you want to initiate the push or pull in the Start Time field. Note Please be sure that you refer to the published guidelines provided by imodules regarding the use of Web services. These will help your institution better understand imodules recommendations regarding record volume, time of day recommendations for larger transactions sets, configuration settings, etc. 9. Enter the date when you want the selection to begin in the Selection Begin Date field. 10. Enter the time when you want the selection to begin in the Selection Begin Time field. 11. If you want an e-mail notification about the status of the scheduled job, enter an e- mail id in one of the four e-mail notification fields, as required. 12. Save the changes. When the Scheduler record initiates a push request, the request selects the changes that occurred since the last time this process was successfully initiated by this Scheduler record. 10 Banner Advancement 8.4.1 June 2011 imodules Encompass Integration - Functional Enhancements

If there is no prior run for this Scheduler record that was successful, the entered Selection Begin Date and Time are used for selection purposes. Modifying an existing scheduler record You can modify a Scheduler record by modifying the information you entered on the Scheduler tab fields. However, you are not allowed to make any modifications for the profile code. If you need to change the profile code, delete the existing record and add a new one with the new profile code. Deleting an existing scheduler record Use the following steps to delete an existing Scheduler record. 1. Select the Scheduler record you want to delete. 2. Select Remove from the Record menu. You get the following message: Do you really want to delete this scheduler record? It is possible to inactivate this record instead of deleting it. 3. Click Yes. The selected record is deleted. E-mail notification The Scheduler provides automated e-mail notifications to the institutions to automatically communicate whether the scheduled jobs were run successfully or not. If there were any issues with the job running, the e-mail would prompt the appropriate personnel to look into and address the issue. The institutions can identify as many as four different e-mail addresses to which this notification should be sent for each scheduler record. The use of these four fields is optional. Certain format checks are performed when an e-mail address is entered. These include a warning message and automatic removal of spaces as well as an error if there is not at least one character prior to @ and before the. in the e-mail address. A sample e-mail notification looks like the following: To: Email 1, 2, 3, 4 From: Banner Advancement Scheduler June 2011 Banner Advancement 8.4.1 11 imodules Encompass Integration - Functional Enhancements

Subject: Scheduler Request Initiated STATUS: Completed PROFILE: Banner Push Email text: Request ID: 9999 Type: Push Date Run: 2/24/2011 Status: Completed Profile: Banner Push Frequency: Daily Error Info: only populated if error information was returned in the web service response Note When a push or pull request is submitted, that request id first moves to INITIATED status. When the request is fully processed, the status will then change to reflect whether or not it was completed successfully. This is the point at which e-mail notifications are generated. Therefore, if for some reason a request does not move from the INTITIATED status, e- mail notifications will not be generated. Any of these requests should be investigated as this most likely means something is wrong with the Connector installation or configuration. Run History tab Two new tabs, Results and Additional Information, were added to the Initiation Requests data block on the Run History tab. The default tab, Results, contains the information the users more frequently need to view such as Start Date/Time, Complete Date/Time, Constituent Count, and Initiated By. The information on the Additional Information tab such as User, File Name, and Selection Properties is supplemental and it is expected the users will need to view this information less frequently. Two new fields, Profile and Initiated By, were added Initiation Requests data block on the Run History tab. 12 Banner Advancement 8.4.1 June 2011 imodules Encompass Integration - Functional Enhancements

Field Profile Initiated By Description Indicates the profile used for the push or pull request. This allows the viewer to better understand which push or pull request they are viewing. Displays the user ID that initiated the push or pull request. For requests initiated by the new Scheduler function, a separate user ID is used specifically by the scheduler process. In this way, the person viewing this column can easily differentiate between the requests initiated by a real person's ID versus the ID associated with the scheduler functionality. Enhanced functionality for CSV file creation Enhancements have been made to the Advancement Connector to more efficiently handle the significant number of constituents that may be included in the creation of.csv files supported by the Push functionality. Of particular concern is the possible file size when creating a.csv file used to load all desired constituents into imodules. Numerous changes were made to ensure that efficient processing occurs for the push, regardless of whether the Output Format selected is Web Service or CSV file. Processing and logic changes The process and logic to select the changed data elements to include in the Push to Encompass has been modified in a few ways: In order to achieve efficiency for incremental data changes and efficiency for large data sets, the processing logic has been changed to employ two different strategies for finding data for the different output formats. Using two different strategies means that each output format performs efficiently for its intended purpose. The Best Practice Recommendations for Web Service Pushes and CSV File Creation section below gives more information on the differences between the two output formats. The logic for a push with an Output Format = Web Service expects smaller amounts of data, typically updates that would occur over a day or over a week. It has been designed to select incremental data changes throughout the collection of advancement individuals efficiently. June 2011 Banner Advancement 8.4.1 13 imodules Encompass Integration - Functional Enhancements

The logic for a push with an Output Format = CSV file expects significantly larger amounts of data, especially given the primary usage of creating the initial files for imodules for data conversions and loads to Encompass. The logic for this scenario is designed to select data from the entire collection of advancement individuals efficiently. Previously, this process was taking 24-36 hours to select the data and load it into the transfer out table for collections of 40,000 to 50,000 advancement individuals. The process is now twenty to thirty times faster. Once the qualifying profile data elements are selected to be included in the push, one processing step is to write these profile data elements to the transfer out table (AUBTROT). The logic for writing these records has been enhanced. Previously, every profile data element was written as a record in the AUBTROT table, even if there were no changes for that data element for a given advancement individual. Consequently, there were many records in the AUBTROT table where the AUBTROT_ELEMENT_VALUE column was empty. Now, profile data elements are written to the AUBTROT table only if the element contains data changes for an advancement individual. This substantially reduces the number of rows added to the table for each request. The reduced number of rows in the table improves the performance of the process and reduces the overall database resources required by the process. When the data in AUBTROT will be written to a CSV file, the CSV file writing process ensures that all of the data elements in the profile have a column in the CSV file, and that all records have appropriate empty values for profile data elements where there were no data changes. This ensures that the CSV file retains the correct format. Sometimes, data values in the Advancement database can contain characters that are reserved characters in the CSV format, primarily the comma(','), double quote ('"'), and return/newline characters. In the CSV format, commas separate values, double quotes enclose values that may contain commas, and return/newline characters signal the end of a row in the file. Previously, double quote characters and return/newline characters in the data values would create format issues for the CSV file. Now, the processing logic checks the data values coming from the Advancement database for these reserved characters. If a comma is present in the data value, the data value is enclosed in double quotes. Double quote characters in the data value are converted to single quote characters ('). Return/newline characters in the data values are removed, as are any leading or trailing spaces or tab characters. If a Push request receives a status of 'No Changes', this means that there are no updates that qualify to be included in the push. If the Output Format is CSV File, no.csv file will be created. Previously one was created but it did not contain any records. In this scenario, the 'No Changes' status communicates to the user that there were no updates to provide. 14 Banner Advancement 8.4.1 June 2011 imodules Encompass Integration - Functional Enhancements

Changes to the Initiation tab on AUAINIT Push and pull processing does not lock the AUAINIT form In prior releases when a user initiated a push or pull request from the Initiation form on AUAINIT, the form was locked and not released back to the user until the entire push or pull process was completed. This is now redesigned so that submitting the push or pull request no longer locks the user on the form. Instead the user is immediately provided with the assigned Request ID after they press the Run button and control of the form is returned to the user. This frees the user to navigate to other forms and to check on the Run History tab regarding the status of the submitted request. This enhancement is especially helpful when the user is submitting larger push requests that could take longer to complete. Users will know that a push or pull request has completed when its status in the Run History tab changes from Initiated to one of the end statuses of Complete, Review, No Changes, Complete with Errors, or Failed. Entry of end date and end time for push The Initiation form now allows users to enter an End Date and End Date time for push requests. Previously this was only allowed for Pull requests. This provides additional selection flexibility to institutions, particularly if they find they need to generate the.csv file to be used for the initial imodules load but the size of this file has become unwieldy. Let's say an institution has 100,000 constituents and the processing and resulting file size of the.csv file is too large. Instead of one large.csv file with a Begin Date of some early date (1950* in our example), the institution could break this up into a couple of requests with a series of stacked Begin and End Selection dates: 1/1/1950-12/30/1980 1/1/1981 - (no end date) This could be tested and rerun until the desired processing time and.csv file size is reached. Running of push profile with update me value When the Banner push profile is delivered, it has the value Update Me in six different Selection Value fields on the Advancement Connector Profile (AUACDEF). Institutions are instructed to replace the Update Me value with the valid value for their institution for the respective fields. Once these six fields are updated with the appropriate and valid values, the push profile has enough information to gather the appropriate records based on the valid selection value for that data element. Changes were made so that if a user executes a push and that push profile still contains the value Update Me in at least one of the selection values, a Failed status is assigned to that June 2011 Banner Advancement 8.4.1 15 imodules Encompass Integration - Functional Enhancements

request. The user can see the message, One or more Selection Values for this profile ='Update Me' Update Me. Please replace with a valid value, in the Response Summary for this request on AUAINIT. The Response Summary can be found in the Associated Batches datablock. Best practice recommendations for Web Service pushes and CSV file creation Use Web Service for incremental changes For incremental data changes, the push to Encompass using the web service is efficient for relatively small amounts of data, representing the collection of changes to advancement individuals' data over periods of a day or a week. Accepting incremental data changes the design and purpose of the web service offered for the Encompass product. Most incremental pushes using the web service should complete in under a minute. While the selection process for web service pushes is very efficient at collecting incremental data changes throughout the collection of advancement individuals, it is NOT efficient at collecting all of the data elements in a profile for every advancement individual in the collection. Therefore, your institution should not attempt to do a web service push with a profile containing many data elements where the date range selected would cause some or most of the data elements for every advancement individual in Banner Advancement to be selected for transfer to Encompass. Use CSV file for large data sets For initial data loads to Encompass, the push operation to create a CSV file is efficient for large amounts of data, representing all desired data elements for every advancement individual that will be transferred to Encompass. The total time to create a file with data for a large number of advancement individuals (51,000 individuals in SGHE's tests) ranges from 1 to 2 hours. Larger numbers of advancement individuals will take proportionally longer, and smaller numbers will take proportionally less time. The logic of the file creation operation is to check every single advancement individual in Advancement for data changes. Therefore, the total time to complete this operation is proportional to the number of advancement individuals in your institution's Advancement system, regardless of the number of data elements in a profile, and regardless of the expected number of data changes the selection would pick up. This means that for push requests where you expect only a small number of data changes to be collected into the file, the operation using the file creation will take substantially longer than the same operation done using the web service. In SGHE's tests, finding a few data changes in a collection of 51,000 advancement individuals takes a few seconds when done using the web service option, but takes 10-12 minutes when done using the output to file option. Therefore, your institution should expect that writing incremental data changes to a CSV file will take much longer than the web service operation, and the time it takes will be 16 Banner Advancement 8.4.1 June 2011 imodules Encompass Integration - Functional Enhancements

proportional to the number of advancement individuals your institution has, and will not be proportional to the expected amount of data that will be collected. Break up very large data sets into multiple files Based on the imodules' recommended CSV file size limit of 20MB, your institution may want to initiate multiple push requests, generating multiple CSV files for the initial data load. If this is necessary, two possible options are: Use the same push profile and initiate it multiple times, varying the Begin and End Date ranges to break the request into separate time periods. Use different push profiles that each address a certain set of data elements - bio, degrees, activities, spouse and children, etc., and collect this data for all advancement individuals. Allocate sufficient memory to Java when writing large files When writing CSV files, the Advancement Connector uses a form of memory on the connector server called heap space. It is an allocation of the server's memory to the Java virtual machine that is executing the code that creates the CSV file from the data in the transfer out table. The more records the process writes out, the more heap space the Java virtual machine needs. If, during the file writing operation, the virtual machine runs out of heap space, the file writing process will terminate, without writing some of the records to the file, and the Java virtual machine will log an out of memory exception. Therefore it is important to configure the connector OC4J container in the Oracle Application Server to allocate sufficient memory to the Java virtual machine. The installation instructions for this release increase the heap size for the connector's Java Virtual Machine (JVM) to 1536 Megabytes or 1.5 Gigabytes. In SGHE's tests, this memory allocation was sufficient to allow the connector to write out 51,000 advancement individual records to a CSV file, with some room for writing a larger number than that. Note For more information on adjusting the JVM heap size, refer to the Step 6 Increase the JVM heap size section in the p1-jg5hsb_alu8040001in.pdf. However, if your Advancement system has a substantially larger number of advancement individuals in it, you may need to allocate even more memory to the Java virtual machine, to get a successful file write, if you are writing the records out into one file. Once the large initial data load files have been generated, you can reduce the amount of memory allocated to the Java virtual machine. For normal incremental data change operations, a heap size between 512 and 1024 Megabytes should be more that sufficient. June 2011 Banner Advancement 8.4.1 17 imodules Encompass Integration - Functional Enhancements

18 Banner Advancement 8.4.1 June 2011 imodules Encompass Integration - Functional Enhancements

2 imodules Encompass Integration - Technical Enhancements This section describes the technical changes that support the functionality included in Banner Advancement 8.4.1. New table - Advancement Connector Scheduler Base Table (AUBSCHD) The new Advancement Connector Scheduler Base Table (AUBSCHD) table contains the following columns: Column Description Type AUBSCHD_CDEF_CODE AUBSCHD_TRANS_TYPE Profile code to be used with the scheduled job. Transaction type associated with the scheduled job, 1 = PUSH, 2 = PULL. VARCHAR2(30) VARCHAR2(1) AUBSCHD_ACTIVE_IND Status of the scheduled job. 0 = Active, 1 = Inactive. VARCHAR2(1) AUBSCHD_SCHEDULE_EXPR AUBSCHD_DATA_ORIGIN AUBSCHD_USER_ID AUBSCHD_ACTIVITY_DATE Formatted expression representing the schedule for the job. Expression format follows the format of a UNIX cron command expression. System maintained field that specifies the origin of the data. Oracle user who created or updated the record. System maintained field that specifies the date this record was created or updated. VARCHAR2(256) VARCHAR2(30) VARCHAR2(30) DATE June 2011 Banner Advancement 8.4.1 19 imodules Encompass Integration - Technical Enhancements

Column Description Type AUBSCHD_SURROGATE_ID Surrogate ID for AUBSCHD. NUMBER(19) AUBSCHD_VERSION AUBSCHD_VPDI_CODE AUBSCHD_SEL_START_DATE AUBSCHD_LAST_SUCCESS_DATE AUBSCHD_NOTIF_EMAIL_ADDR_1 AUBSCHD_NOTIF_EMAIL_ADDR_2 AUBSCHD_NOTIF_EMAIL_ADDR_3 AUBSCHD_NOTIF_EMAIL_ADDR_4 Optimistic lock token for AUBSCHD. 'BANNER' MEP institution code for AUBSCHD. Initial selection start date and time for the scheduled job. Last date that the scheduled job was run successfully. E-mail address where notification is sent after completion of scheduled job. Second e-mail address where notification is sent after completion of scheduled job. Third e-mail address where notification is sent after completion of scheduled job. Fourth e-mail address where notification is sent after completion of scheduled job. NUMBER(19) VARCHAR2(6) DATE DATE VARCHAR2(128) VARCHAR2(128) VARCHAR2(128) VARCHAR2(128) New connector properties The connector. properties file is used to hold configuration values used by the Advancement Connector regardless of which partner system it connects to. The following new properties support the automated e-mail notices that are sent after the Scheduler runs scheduled jobs. 20 Banner Advancement 8.4.1 June 2011 imodules Encompass Integration - Technical Enhancements

Property connector.scheduledjobclass connector.schedulervalidator connector.validatorjobclass connector.validatorrepeats connector.validatorfrequency connector.emailhost Description Scheduled job implementation that the Quartz Scheduler uses to push or pull information. Default value is com.sungardhe.banner.advancement.utility.scheduler.conn ectorscheduledjob. Indicator that determines whether the Connector should set up a simple Scheduler validator job that runs more frequently than regular Connector scheduled jobs, and determines whether the Scheduler is running in an easily verifiable way. true - Schedule validator job (default value). false - Do not schedule validator job. Remove the job from the Scheduler, if the job exists. Connector Scheduler validator job implementation that the Scheduler uses to report that it is running. Default value is com.sungardhe.banner.advancement.utility.scheduler.valid ator.connectorschedulervalidator. Number of times that the validation job should be run. 1 - Run the job once, as soon as the Scheduler is started. Any other numeric value - Run the job this number of times on the frequency set by the connector.validatiorfrequency property. * - Schedule the job to run indefinitely on the frequency set by the connector.validatiorfrequency property (default value). Frequency to run the validator job, in minutes. This value is meaningful only if the value of the connector.validatorrepeats property is an asterisk (*) or greater than 1. Delivered value is 60. Host address of the SMTP server that sends e-mail notices to designated e-mail addresses after the Scheduler runs scheduled jobs. Use either the FQDN (preferred) or the IP address. June 2011 Banner Advancement 8.4.1 21 imodules Encompass Integration - Technical Enhancements

Property connector.emailnotif connector.emailpersname Description E-mail address that is provided in e-mail notices as the sender address. Used with the connector.emailpersname to identify the message sender. Default value is connectornotifications@sungardhe.com. Personal name (friendly name) that is provided in e-mail notices as the sender. Used with the connector.emailnotif to identify the message sender. Default value is Banner Advancement Scheduler. 22 Banner Advancement 8.4.1 June 2011 imodules Encompass Integration - Technical Enhancements

3 Miscellaneous Enhancements - Functional This section describes the miscellaneous functional enhancements in Banner Advancement 8.4.1. Advancement Telemarketing Results Upload (AGPTLMK) This process uploads pledges into a temporary Banner table and uploads the phon-a-thon results from an automated telephone marketing system directly into Banner. The AGPTLMK process was modified to simplify the processing of records that are loaded from the third party data file. Previously, this process required a record in the Campaign Contact Repeating Table (AFRCTYP) in order to successfully load any records included in the data file. The logic in the AGPTLMK process was modified to do the following: Review the data file details. If the pledge date field is not null in the data file, the process assumes that a pledge response is being loaded. It does not validate the need for a record to exist in the Campaign Contact Repeating Table (AFRCTYP). All other records in the data file are processed as contacts with results which require a record in the Campaign Contact Repeating Table (AFRCTYP). The output report that contains the errors (if any) was modified to display the ID of the record in addition to the PIDM. This helps the user to easily locate the record in error and to troubleshoot the corrections needed to address the error condition. Constituent Identification view (AA_CONSTITUENT_IDENTIFICATION) A new column was added to the Constituent Identification view. The PREF_FIRST_NAME column allows you to retrieve the preferred first name for your reports and queries. The preferred first name allows your callers, advancement development officers, and other officials to be more personal in their correspondence and conversations. June 2011 Banner Advancement 8.4.1 23 Miscellaneous Enhancements - Functional

Highlight alert for specific forms The User Alert functionality in Banner Advancement has been enhanced to highlight alerts related to a specific form. Prior to this enhancement, the pop-up for user alerts was only displayed in a session the first time a user navigated to a form for a constituent that has a user alert associated with it. This worked fine when all the alerts for this constituent were general and were displayed on all the forms that support the User Alert functionality. Therefore, while viewing the list of alerts when this notification is initially presented, the user is aware of all the alerts for this constituent. However, when alerts existed for a constituent that was associated only with a specific form or set of forms, the user was unaware of this situation as there was no indication that they should select the User Alerts icon again to view these form-specific alerts. As a result of this enhancement, the user will now see the following message when a form has specific alerts associated with it: *Note* Please check User Alerts for this form. Specific alerts are associated with this form. Clicking the User Alerts icon will display all the alerts associated with that form. Modified triggers The A$_CHECK_USER_ALERTS trigger has been modified in the following ways for this enhancement: Added CHECK_CATEGORY_AURALRT_C cursor. Added code to check CHECK_CATEGORY_AURALRT_C regardless if the keyblock_id changed or not. Modified object The following object has been modified for this enhancement: aoqclib.fmb 24 Banner Advancement 8.4.1 June 2011 Miscellaneous Enhancements - Functional

4 Problem Resolutions This section summarizes the problem resolutions that are targeted for delivery with Banner Advancement 8.4.1. For comprehensive and detailed information for all problems resolved in this release, refer to the advanc80401resolutions.txt file delivered with this release guide. The information in this text file is extracted from the Customer Support Center immediately before release of the product. This text file may include additional defects that were resolved after this release guide was finalized. Object Name Defect Number Summary ADPFEED 1-F05791 The drop-down values for parm 8 on GJAPCTL for ADPFEED are incorrect. Adv Connector 8.3.2 Installation and Administration Guide 1-NBHH5I Pg 47-4.2 needs to mention to "include the cleartext password in encompassconnect.properties file. afvcmp0.sql 1-AVLTAQ The aa_campaign_giving_by_id view returns incorrect data in certain fields. agamatg.fmb axkexmg.sql 1-7H13IO AGRGMMO amounts being incorrectly calculated. agapldg.fmb 1-5DHP7A Need a warning message when the pledge date falls outside the campaign start/end dates on AFACAMP. agkgrpt.p_proce ss_gift_data 1-4D2BLA Error "ORA-00942: table or view does not exist" when trying to run agkgrpt.p_process. AGPMATC CMS-DFCT84987 If MINIMUM, MAXIMUM, and ANN_EMP are left-justified within their 10-char fields on the HEP data file that is processed by AGPMATC, then the.lis and.lis4 reports show blanks for these fields. If these fields are right-justified, then the AGPMATC reports display the data correctly. agptlmk.pc 1-5ISWLM Banner 8 AGPTLMK errors for non-pledge phonathon results. June 2011 Banner Advancement 8.4.1 25 Problem Resolutions

Object Name Defect Number Summary agptlmk.pc 1-EMZJ6W AGPTLMK - only imports the first record on the file - no more. AMACONT 1-KZC7UD Ask Amount gets cleared when the Proposal is changed. amaprop.fmb amainfo.fmb 1-3H01JV ASK Amount fields on some forms only allow up to an 8 figure amount. AOAMTCH LN70-0197-432 Error message at first record displays in the first window of form every time you enter. aoaorgn.fmb 1-43U52E AOAORGN Cannot rollback or exit without saving. aoaorgn.fmb 1-45AQAH The Address From and To dates should never be accessible on Secondary Contacts tab of AOAORGN. AOVCOMP CMS-DFCT85969 Defect correction 14131 is causing the view AOVCOMP to displaying both active and inactive addresses. APACONS 1-3GWM4J Form should allow removal of SPS Xref code without having to alter Status field. apadclb.fmb 1-3O76HV *ERROR* Gift society name cannot be changed. "*ERROR* Gift society name cannot be changed." appcupd.pc 1-50C34Y APPCUPD may not process the last field on records in a delimited file. apvcni0.sql 1-E64TSJ aa_constituent_identification view is still pulling preferred phone number that has been inactivated. asasign.fmb 1-5GU14E Contact assign date is not updated when assignments are done via ASASIGN. ASEASON 1-DEIB6C ASEASON script may be incorrectly updating seasonal addresses 26 Banner Advancement 8.4.1 June 2011 Problem Resolutions

Object Name Defect Number Summary Current Moves 1-LA3K9N Cannot make changes via INB to any contact report that was entered via Banner SS Moves Management. Upgrade invalid object - AA_RELATIONS HIP view 1-67IE72 APVCHLD has typo. June 2011 Banner Advancement 8.4.1 27 Problem Resolutions

4 Country View Road Malvern, Pennsylvania 19355 United States of America www.sungardhe.com