Jackson Community College

Change Request............: 37654.52

Summary...................: March 2008 Envision Bundle

Criticality...............: Release

Status....................: Complete

Date Completed............: 3/26/2008

Impact....................: Medium

Priority..................: B

Project...................:

Main Release ID...........:

Application...............: UT

Module Name...............: UT

Mnemonic..................:

Problem/Issue.............:

Clients reported a number of issues with the software.  See the Description section for more information about the issues resolved with this software update.

Resolution................:

This software update resolves a number of issues in Envision Runtime (UT) and Envision Tool Kit (TOOL) for Release 18.

See the Description section for more information about the issues resolved with this software update.

Client Impact.............:

CLIENT IMPACT

Datatel software is now easier to use.

See AnswerNet Support Solution Page 6294 for details on running the new WEEKLY.UDT.INDEX.ANALYSIS (WUIA) utility for analyzing UniData index files.

IMPLEMENTATION INSTRUCTIONS

Not Applicable.

TECHNICAL IMPLEMENTATION

Not Applicable.

NEW FORMS

Not Applicable.

CUSTOM IMPACT

Not Applicable.

SOFTWARE PARTNER

Not Applicable.

Description...............:

03/26/2008 - The following software update has been released and is available to Clients:

*******************************

SU37654.52-485*06

******************************* 

This update resolves the following issues:

14852.37

Issue:  Clients wanted a utility to analyze UniData indexing files.

Resolution:  Similar to WEEKLY.UDT.FILE.ANALYSIS (WUFA), a new utility has been created called WEEKLY.UDT.INDEX.ANALYSIS (WUIA).

37335.37

Issue:  WEEKLY.UDT.FILE.ANALYSIS (WUFA) could throw an unexpected error of "In INSTALL_PROGS/_WEEKLY.UDT.FILE.ANALYSIS at line 1428 Cannot find S.EXECUTE)" when run in an LPR.

Resolution:  WEEKLY.UDT.FILE.ANALYSIS (WUFA) no longer causes an unexpected error when run in an LPR.

26702.26

Issue:  The Workflow Def Move Utility (WFMV) process did not create MOVEINFO records.  This issue forced clients to manually create saved lists of all components for a given workflow by using the Savedlist Creation (SLCR) form to move a workflow from one environment to another.

Resolution:  The Workflow Def Move Utility (WFMV) form has been changed to create MOVEINFO records.

107.2766

Issue:  appl.PPROCESS 'login.BATCH' records, for batches run outside of a procedure, were allowed to grow without restriction.

Resolution:  Batch processes executed outside of Envision have been modified to update run information in a unique appl.PPROCESS record keyed by BATCH_<login>_<time>_<date> instead of constantly using and appending to a record keyed by <login>.BATCH.

15454.85

Issue:  A runtime message of "Unable to read HALF from unopened file .PRCS.CTL" was being logged to the UNOPENED.FILE.READ.ERRORS record in _HOLD_ when an appl.JUMPSTART routine was being invoked from the LOGIN paragraph.

Resolution:  Envision Runtime has been modified to no longer log an entry in UNOPENED.FILE.READ.ERRORS when an appl.JUMPSTART routine has been invoked from the LOGIN paragraph.

29381.63

Issue:  An unnecessary error message of "Can't process logical view in MMF for <logical file name>" was being displayed in a SQL Server or Oracle environment when updating a logical view file.

Resolution:  The Envision Tool Kit has been modified to longer issue the unnecessary warning message "Can't process logical view in MMF for "<logical file name>" when maintaining a logical view on the Define File Specifications (FS) or Default Release Behavior (DFRB) forms.

37601.75

Issue:  The S_SQL_RESET routine was referencing an incorrect insert, causing the initialization of some Envision parameters to be skipped.

Resolution:  Envision Runtime has been modified to use the correct insert when initializing ENVISION.PARAMETERS.

24289.74

Issue:  A "Dictionary access unsupported for DICT <file>" message was being incorrectly displayed when modifying an association on the Define Sub File (DSF) form in a SQL Server or Oracle environment.

Resolution:  The Envision Tool Kit has been modified to no longer issue the unnecessary "Dictionary access unsupported..." warning message when maintaining an association on the Define Sub File (DSF) form.

38080.19

Issue:  The process handler would fail to identify running jobs for HP environments.

Resolution:  A post-install subroutine is included in this software update to correct a potentially incorrect Datatel-delivered operating system command for HP environments.

6003.82

Issue:  Some application processes would display record lock messages on reports, instead of on the forms where the locks occur.

Resolution:  Locked record messages now correctly appear on Colleague forms and not on reports.

14999.04

Issue:  The Additional Selection Criteria form was not displayed when users saved their entries on the Process Status File Purge (PSFP) form.

Resolution:  When the Additional Selection Criteria field is set to "Yes" on the Process Status File Purge (PSFP) form, Envision opens the Additional Selection Criteria form when the user saves from the PSFP form.

37733.11

Issue:  RFSPECS and appl.VOC records were not being created for file suite instance files.  This was resolved in change request 33201.07 for new file suite instances, but the missing RFSPECS and appl.VOC records for older instances needed to be created.

Resolution:  A post-install subroutine is included in this software update to create all missing RFSPECS and appl.VOC records for file suite instance files.

Change Request............: 37690.56

Summary...................: Enhancements to FATR reporting

Criticality...............: Release

Status....................: Complete

Date Completed............: 3/26/2008

Impact....................: High

Priority..................: C

Project...................:

Main Release ID...........:

Application...............: ARCR

Module Name...............: AR

Mnemonic..................:

Problem/Issue.............:

When clients ran the Batch FA Transmittal Register (FATR) process with the Print All Students flag set to "No," the resulting report displayed students with reallocations netting to zero, in addition to students with a net increase or decrease in their Financial Aid amount.

Some clients have asked for a way to print only those students with a net increase or decrease to the amount of a Financial Aid award.

Resolution................:

The Batch FA Transmittal Register (FATR) process was modified such that the Print All Students field was renamed to Print Options, which now provides three options.  Option 'A' will print all evaluated awards, even if there was no activity for the award.  Option 'R' will print awards that were either Reallocated (payments were adjusted among invoices but no change in the net amount of aid) or Transmitted (net increase or decrease in aid amount.)  Option 'T' will print only Transmitted awards.

Client Impact.............:

Clients now have better control over the contents of the Batch FA Transmittal Register (FATR) report.

Description...............:

03/26/2008 - The following software update has been released and is available to clients:

******************************

SU37690.56-1805*03

******************************

When the Batch FA Transmittal Register (FATR) process is run, it evaluates all specified students to determine whether the students' Financial Aid should change.  The evaluation can have three outcomes.  Either there are no changes to a student's Financial Aid; Financial Aid can be reallocated among a student's invoices with no change in the net amount of a Financial Aid award; or Financial Aid can be (re)allocated with an increase or decrease in the amount of a Financial Aid award.  Further, the FATR process will report these results based on the entry in the 'Print All Students' field.

If the Print All Students flag was set to "Yes", then all evaluated students were printed.

If the Print All Students flag was set to "No", then evaluated students with reallocations netting to zero were printed, in addition to students with a net increase or decrease in their Financial Aid amount.

Some clients have asked for a way to print only those students with a net increase or decrease to the amount of a Financial Aid award.

Change Request............: 31163.33

Summary...................: Release 18 Colleague Student Improvements

Criticality...............: Release

Status....................: Complete

Date Completed............: 3/27/2008

Impact....................:

Priority..................: A

Project...................:

Main Release ID...........:

Application...............: ST

Module Name...............:

Mnemonic..................:

Problem/Issue.............:

Numerous issues appeared on Release 18 that provided difficulties for clients.  See the Description section for more information about the issues resolved with this software update.

Resolution................:

This software update resolves a variety of issues that clients were experiencing.  Corrections were made in numerous modules including Academic Credentials, Telephone Registration, and Student Educational Planning.  A complete list of issues is in the Description section of this document.

Client Impact.............:

Colleague Student is easier to use.

IMPLEMENTATION INSTRUCTIONS

Not applicable

TECHNICAL IMPLEMENTATION

Not applicable

NEW FORMS

Not applicable

CUSTOM IMPACT

Not applicable

SOFTWARE PARTNER

EPOS, for Integrated Voice Response (TREG) issues

Description...............:

3/27/2008 - The following software update was released to clients:

***************************

SU31163.33-1805*11

***************************

This software update resolves several issues in Colleague Student, as listed below:

INTEGRATED VOICE RESPONSE (TREG)

8298.04 When students asked to listen to their grades on TREG, they did not hear their GPA or academic standing if they had more than one course in a term.  The process TREG.HOST has been corrected so students will hear their GPA or academic standing.

35327.15 If a caller to TREG failed an eligibility rule during login, this error was not reported and the call was allowed to continue. In some cases the caller could successfully register for classes. In addition, these registrations would be saved even if the caller chose to cancel the changes, with TREG reporting that their changes were canceled. The registrations would also be saved if the caller hung up and the hang-up action was set to cancel. In other cases callers would receive errors while trying to register for classes. TREG has been modified so that an eligibility rule will be reported to the caller, and the call will be terminated.

36138.67 Users were receiving one or more errors while regenerating TREG.HOST.  The process was corrected so that the errors will no longer occur.

20961.26 When TREG logged into Colleague, warning messages were appearing in the background.  These warnings have been resolved and will no longer occur.

37179.15 When the initial receipt of a Step command from EPOS was logged in the TREG.TRANSACTIONS log, it contained the Step Number and Student ID of the previous command from EPOS, or was blank if there wasn't a previous command.  Now the TREG.TRANSACTIONS record contains the Step Number and Student ID of the Step command being logged.  This will help with the selection of TREG.TRANSACTION records during debugging.

37270.67 TREG was not recognizing that a student's record was locked during login to TREG, allowing the call to proceed. The call should have been terminated. Further problems would be encountered during the call due to the record locks. TREG has been corrected so that locked records are correctly detected during login.

WEBADVISOR REGISTRATION

37275.04 Users received an error when they attempted to use the link between Register and Drop Sections and Manage My Waitlist.  The link has been fixed and users can now go directly from Register and Drop Sections to Manage My Waitlist.

ACADEMIC CREDENTIALS

23628.15 When a user tried to access a record on the Student Academic Credits (STAC) form while the record was already accessed by another user, the second user got a message similar to the following:

PERSON_ST - 0000970 locked by user 6533

The second user was given only the option to retry and not to cancel.

The process ACS027 has been modified so now the second user will be able to retry or cancel.

STUDENT EDUCATIONAL PLANNING

26075.44 and 36392.59  When creating a new Student Ed Plan, the SEP.PLAN.STUDIES list is not being stored in the correct sort order.  This makes longer term use of Student Ed Plans difficult for Advisors, where new Courses may be approved, planned, and actual terms changed, and the resulting lists of Courses are no longer grouped together in a usable form.  The code for S.CREATE.STU.ED.PLAN and S.UPDATE.STU.ED.PLAN were revised to both use the same ordering logic and order the items in Term and Course Name order.

CURRICULUM MANAGEMENT

30827.41 If there were one thousand or more sections for a single course, and a new section was added to the course on the Sections (SECT) form, it would take several minutes to save the information on the SECT form.  The code was changed so that the SECT form now saves quickly in this scenario.

ELECTRONIC FILE TRANSFER (ELF)

31550.89 The Electronic Appl Interface (EAPP) process was not checking for duplicates and was producing error messages such as: "Pre-Commit: SSN Number assigned to 1126255 Jennifer L. Monser." The AMF076 process has been regenerated to correct those problems.

ACTIVE ADMISSIONS

35179.63 There was no online help for the Other Import Errors field on the Resolve AC-ADM Import Errors (ACIE) form (accessed from the My To Do List [MTDL] form when worklist item exists). The field help for Other Import Errors was added to the form.

35175.22 The online help for the ActiveAdm Import Parameters (AAIP) form was missing an entry for the Prospect Application Status field.  The field help has been added to the AAIP form.

DEGREE AUDIT

184.834 Clients were confused by the way prerequisites worked when a code of "In Progress" was used on the Registration Controls (RGCT) form.  In order to clarify the meaning of prerequisite status, the description of the codes in the DA.EVAL.STATUSES validation code has been changed to include the word "requirement" (for example, Requirement Pending, Requirement Complete, etc.).  Additionally Datatel recommends that you do not use "Requirement In Progress" on the Registration Controls (RGCT) form because the option is confusing - it is meant to allow registration even though the entire prerequisite is not yet complete.  Please refer to Support Solution number 750 for further explanation.

NATIONAL DEGREE VERIFICATION SERVICE (NDVS)

12644.52 No information was provided about how to utilize the functionality provided by the NDVS Deg/CCD Student Export (NDVS) process to flag student's data for protection under the Family Education Rights and Privacy Act (FERPA).  The field help for the Directory Codes field has been updated to include a note about how to automatically flag a student's record for FERPA protection, and if a student has requested FERPA protection, it must be specified in the Directory Codes field.  The Using Academic Records and Getting Started with Colleague Core manuals were also updated.

GENERAL ISSUES

32214.26 In R18 the BIOGRAPHICS.HEADER record was always defaulting to the record in the CORE.PARMS file, no matter which application you started in.  For example, if you accessed a form in HR that has its own BIOGRAPHICS.HEADER record (in the HR.PARMS file), it would display information as defined in the CORE.PARMS file.  The CORE.STARTUP subroutine has been changed to resolve this issue.

22851.59 The subroutine S.CALC.ADMISSIONS.GPA was specified as an IS type subroutine, but it uses the Rules processor, which is not supported in IS subroutines. Therefore errors would occur when generating it. The S.CALC.ADMISSIONS.GPA subroutine has been changed to an S type subroutine.

The subroutine S.CALC.ACAD.GPA was specified as an IS type subroutine, but it uses the Rules processor which is not supported in IS subroutines. Therefore errors would occur when generating it. The S.CALC. ACAD.GPA subroutine has been changed to an S type subroutine.

The code for STA.CURRENT.STANDING converted from the R17 computed column language to the R18 computed column language had an error dealing with multivalued and single-valued data. The R18 code for this computed column has been corrected. 

2047.44, 28974.52, and  33941.56 If a client used a database keyword when performing a LookUp on a Colleague form, such as "FOR" in UniData or "12AB" in SQL Server, the LookUp would fail. The LookUp processor has been modified so that it works with these keywords, but each form that contains the LookUp must be regenerated in order to take advantage of the modification.

Three LookUps in particular were identified as having this problem - Room LookUps against Buildings that are named with a keyword, Grade LookUps against Grading Schemes named with a keyword, and ELF transaction LookUps against an ELF batch named with a keyword.

Forms that contain Grade LookUps, Room LookUps, and ELF transaction LookUps (with the exception of the Target Results/Dupl Res [TGTR] form, which will be released at a later date) were regenerated to take advantage of the LookUp processor improvements.

Change Request............: 36345.89

Summary...................: UT/TOOL Spring 2008 Bundle

Criticality...............: Release

Status....................: Complete

Date Completed............: 3/26/2008

Impact....................: Low

Priority..................: C

Project...................:

Main Release ID...........:

Application...............: UT

Module Name...............: UT

Mnemonic..................:

Problem/Issue.............:

Clients reported a number of issues with the software.  See the Description section for more information about the issues resolved with this software update.

Resolution................:

This software update resolves a number of issues in Envision Runtime (UT) and Envision Tool Kit (TOOL) for Release 18.

See the Description section for more information about the issues resolved with this software update.

Client Impact.............:

Datatel Colleague software is easier to use.

IMPLEMENTATION INSTRUCTIONS

Not applicable.

TECHNICAL IMPLEMENTATION

Not applicable.

NEW FORMS

SCAN.DATA.RESULTS conversion (SDCV)

      Use this process to convert records from SCAN.DATA.RESULTS into

      CDSU.FILES and CDSU.RESULTS records. The Colleague Data Scanner Util

      (CDSU) and the Colleague Data Scanner Report (CDSR) processes allow you

      to store data and report from data scanner results. File-level

      information is stored in the CDSU.FILES file, and record-level

      information is stored in the CDSU.RESULTS file. The SDCV process

      converts data using a non-overwriting approach. The process creates

      records in the CDSU.FILES and CDSU.RESULTS files only if there is no existing

      data for the record that is being converted.

CUSTOM IMPACT

Not applicable.

SOFTWARE PARTNER

Not applicable.

Description...............:

03/26/08 - The following software update has been released and is available to Clients:

******************************

SU36345.89-485*08

******************************

This software update delivers Envision Runtime (UT) and Envision Tool Kit (TOOL) modifications made for the Spring 2008 bundle.  

------------------------------------------------------

The bundle makes the following changes not associated to an AnswerNet change request:

- GEN version number changed to 4.8.5  (visible on the header block of the GEN form).

------------------------------------------------------

The bundle addresses the following AnswerNet change requests:

36150.89 (Missing online help for inquiry fields on Resource Database forms ) Several forms used for maintaining and defining the Resource Database had online help missing for inquiry fields.  This help is now provided.

3203.85 (too many variables or no more entries in MI-table errors) If a program processed a large list of records at process level zero, then the MIO read cache would not get cleared for the entire duration of the program.  It was then possible for UniData to experience errors such as "too may variables" or "no more entries in MI-table."  MIO has been changed to no longer cache record reads at process level zero.

13792.78 (TOOL: S.OPEN.SEQ not returning errors; how to determine if file not present) S.OPEN.SEQ was not returning errors when trying to open a non-existent file. S.OPEN.SEQ has been changed to return an error if a non-existent file is opened for read-only access; otherwise, if trying to open a non-existent file for write or append, the subroutine still does not return an error. This software update is also delivering new UT versions of S.OPEN.SEQ, S.CLOSE.SEQ, S.READ.SEQ, S.WRITE.SEQ, and S.WRITE.EOF. A future COLL18 software update will eventually make the CORE versions of these routines obsolete.

17134.74 (ENV: too many levels of Uni/basic CALL 1024 using record level security) When record security was defined on a file that requires reading records from the file being secured, it was possible for the record security evaluation routine to be caught in an infinite (self-referencing) loop. Record security has now been changed so that data reads taking place within a record security evaluation routine no longer have record security applied.

37272.07 (Release UT insert I_INPUT.SEC.PRCS.CTL.LOOKUP) The UT insert record I_INPUT.SEC.PRCS.CTL.LOOKUP is now being released.

24335.85 (INTL shows incorrect date format when values are NULL) The International Parameters (INTL) form has been modified to provide default values if no values exist, and the fields have been made required in order for dates to be viewed correctly on Colleague forms.

36355.33 (R18 UT.SOURCE code for UTCTLS [PCSI] approved for release) The source code for the PRCS.CTL Security Inquiry (PCSI) form is now being released.

17488.63 (Cancelling out of SMD does NOT cancel changes made on SMD3) Any changes made while detailing from the Menu Definition (SMD) form, and then canceling from the SMD form will no longer be saved.

15166.19 (Fields on PCSI are not large enough ) The PRCS.CTL Security Inquiry (PCSI) form has been modified to allow users to view the full name of associated security classes.

36089.59 (Starting savedlist name with a number on SLCR results in error) A correct error message will be displayed on the Savedlist Creation (SLCR) form when a user enters a saved list name that is not valid.

21782.48 (SLCR Savedlist Creation name won't allow a length > 20) A correct error message will be displayed on the Savedlist Creation (SLCR) form when a user enters a saved list name longer than 20 characters.

24348.22 (UT: Error when using HOLD PRIVATE functionality in SQL/ORACLE) In SQL Server and Oracle, the inclusion of the HOLD output device and PRIVATE security designation in the Peripheral Options Defaults form no longer causes a data truncation error.

36204.15 (DCC allows user to enter incorrect auto x-ref specs) The Define Computed Column (DCC) form now ensures that a reference file key is specified if a reference file name is defined.

36205.74 (DEL allows user to enter incorrect auto x-ref specs) The Database Element Linkages (DEL) form now ensures that a reference file key is specified if a reference file name is defined.

36169.81 (Release remaining Envision 4.8 updates that are on ENV_RELEASE_955)

- The Convert to Multi-Addr Worklist (WFCA) form has been modified to be tied to the "WF" module. 

- The Colleague Data Scanner Util (CDSU) and the Colleague Data Scanner Report (CDSR) processes have been updated to match the functionality provided in R17. 

- The new Scan Data Results Conversion (SDCV) utility has been released to convert to the new file structure (to R18) of the data scanner utility.

30177.85 (Envision Painter> Misplaced SEHH Code when fields are added/deleted) The Envision painter has been updated to retain hyperlink code attached to the appropriate fields when additional fields are added or deleted from a form.

12896.63 (Login ID with underscore in it can cause problems in procedures.) The Envision Tool Kit uses a user's login ID to store jobs run by that user with a key format of <mnemonic>_<login ID>_<time>.  The Tool Kit has been changed to ignore any underscores in a login ID to prevent problematic additional delimiters in the key.

14762.22 (SELECT on SEC.AVAIL.STATUS returns incorrect results with Database Indexing) Processes that used UniData's active list #0 in conjunction with calling S_MIO_INDEX_INFO or S.GET.INDEX will now work correctly.

23360.41 (S_MIO_INDEX_INFO needs better performance) Some processes that access file indexes by calling either S_MIO_INDEX_INFO or S.GET.INDEX now run faster.

28393.48 (Cannot use Savedlist #2 when using Database Indexing) Processes that use UniData's active list #2 in conjunction with calling S_MIO_INDEX_INFO or S.GET.INDEX now function correctly.

36281.33 (S_MIO_INDEX_INFO fails to properly match keys in multi-key request) Processes that call S_MIO_INDEX_INFO or S.GET.INDEX to retrieve lists of keys that include numeric keys where not all the numeric keys are of the same length now retrieve the correct list of keys.

1096.67 (Wrong CDD element assigned to key by GEN_BATCH) A batch process in which the first demanded element is not a key will now be generated correctly.

4251.07 (Generator produces GOSUB to nonexistent SET.REC.MOD routine) Batch processes that reference a secondary pointer in a FOR_ statement that does not use either the SECONDARY or INTO keywords, will now be generated without error.

28983.81 (Compile error from code generated when selectively deleting Q-pointer) Batch processes that reference a secondary pointer in a FOR_ statement that does not use either the SECONDARY or INTO keywords, will now be generated without error.

12581.25 (error with EBSL FOR_THE...EXISTING construct) Keywords "NEW" and "EXISTING" used with the "FOR_" statement, now work as documented.

13211.33 (Multi-part key reads fail when any part of the key is null.) Reading from a file with a multipart key will now work correctly as long as at least one of the parts is not null.

13840.74 (GEN uses VLs for key to primary file) Forms that contain a regular (non-phantom) field defined as a pointer back to the form's primary file no longer produce an error during generation.

15630.41 (GEN error when use FOR_EACH ASSOCIATED with ptr with relation file assoc'd) Batch processes with multipart keys will no longer generate code containing literal value marks.

22.274 (ETK: Multi-part IDs created incorrectly in EBSL and Screens) Statements of the form  "KEY.<file> = V.<keyfield1>xV.<keyfield2>", where "x" is a literal value mark, are no longer produced by the batch processor

22.119 (BPO: BED: Value Marks generated when using 2-part keys) Forms that contain a regular (non-phantom) field defined as a pointer back to the form's primary file no longer produce an error during generation when the primary file has a multipart key.

5014.52 (Batch Generator relies on sequence of demanded fields) Batch processes no longer require a file's key field to precede all of the file's data fields in the process' demanded fields list on BED.

36034.59 (GEN infinite loop in some batch prcses with "MATCH..." keyword) Code generated for an EBSL statement of the form "FOR_EACH ASSOCIATED <element> MATCHING LAST" no longer results in a possible infinite loop at runtime.

36142.78 (Batch GEN error expanding multi-argument ERROR_IF statement) Code generated for an ERROR_IF statement with multiple arguments is now correct.

36658.85 (Improve debugging functionality within the UI batch and form generators)

The UI batch and form generators now have better diagnostic features.

37304.59 (Form generators should use  STANDARD system "original data" variables) For developer convenience, the UI form generator now generates assignment statements to copy data into "orig" variables.

29771.96 (SET_SECURITY sometimes changes the last field on the screen) The SET_SECURITY statement no longer incorrectly modifies security of a form's last field.

20723.22 (SET_SECURITY macro generates wrong code) Extra code is no longer generated for the SET_SECURITY statement.

20559.59 (SET_SECURITY causing problems when set from a window field) Specifying the SET_SECURITY statement from within a window no longer causes window data to be corrupted.

37066.52 (Syntax issues with SET_SECURITY statement) SET_SECURITY syntax errors are now detected and reported when the form is generated.

33412.44 (Tab characters in hook code causes GEN errors) Tab characters in hook code no longer cause GEN errors.

20759.26 (GEN should handle single-valued use of "A" type field more gracefully) The generator now issues a warning message when it encounters a form on which a multivalued field has been painted but not included as a window member.

28983.81 (Compile error from code generated when selectively deleting Q-pointer) The generator now correctly compiles the code which selectively deletes a Q-pointer. 

33412.44 (Tab characters in hook code causes GEN errors) The generator now handles tab characters correctly.

36345.89 (CDD statement in output hook ignored ) The generator now uses the CDD statement in the output hook code correctly

36658.85 (Add GRAS diagnostics to UI batch and form generators) The GRAS diagnostics are now availalble to the UI batch and form generators.

Change Request............: 30570.52

Summary...................: Release 18 CF Update for AP and AR voucher maintenance

Criticality...............: Release

Status....................: Complete

Date Completed............: 3/28/2008

Impact....................:

Priority..................: A

Project...................:

Main Release ID...........:

Application...............: CF

Module Name...............:

Mnemonic..................:  

Problem/Issue.............:

Clients reported a number of issues with Colleague Finance. See the Description section for an overview of the activities resolved with this release.

Resolution................:

This software update resolves a number of issues with Colleague Finance.  See the Description section for an overview of the activities resolved with this release.

Client Impact.............:

Colleague Finance is now more accurate and easier to use, in the following ways:

- The institution can choose whether to void related vouchers or not. Credit card refunds will now use the cash account from the originating cash receipts.

- Blanket Purchase Orders now encumber and unencumber the correct amount.

- Vouchers that originated from a purchase order, and vouchers that originated from a BPO that previously caused posting errors, are now posted correctly.

- Rebate taxes are now correctly calculated and posted to the general ledger and the subsidiary ledgers.

- Manual journal entries will no longer skip sequential number IDs.

- The GL number descriptions that are displayed in the GL account number resolution and in the funds availability window will now be displayed correctly.

IMPLEMENTATION INSTRUCTIONS:

Not applicable.

TECHNICAL IMPLEMENTATION:

Not applicable.

NEW FORMS:

Not Applicable

CUSTOM IMPACT:

Not applicable.

SOFTWARE PARTNER:

Not applicable.

Description...............:

03/28/08 - The following software update has been released and is available to Clients:

**************************

SU30570.52-1805*06

**************************

This software update resolves the AnswerNet change requests described below.

13395.25

VRAV:  Voiding Related Vouchers

When using the AR Refunds/Advances Void (VRAV) process to void an AR voucher, the system would automatically void all of the vouchers related to that specific voucher. 

The VRAV process has been changed so that it no longer automatically voids related vouchers.  A new Void Rel Vous field has been added to the VRAV form to allow the users to choose whether they want to void related "Outstanding" or "Not Approved" vouchers.

23178.15

BPO unencumbers tax amounts when APDE's Distribute Tax Expense flag = 'No'

When the Distribute Tax Expense field was set to "No" on the AP Parameters Definition (APDE) form, a voucher with a blanket purchase order was incorrectly unencumbering the full cost of the purchased item and the taxes, less tax rebate amount.  Only the amount that was expensed on the BPO GL account number should have been unencumbered. 

Now, when taxes are not distributed and a voucher with taxes is associated with a blanket purchase order, only the voucher expense amounts will relieve encumbrances from the BPO. Tax amounts on the voucher do not relieve encumbrances from the BPO.

27589.81

R18:  Credit Card Refunds Paid for Wrong GL Account

When refunding a credit card payment, the cash GL account that is supposed to be used is the cash account that was used on the original cash receipt.

The program that determines what GL account to use when processing a credit card refund has been modified to use the cash account that was used on the cash receipt.

28806.26

VOUM:  Added line items are not posting GST rebate to the General Ledger

Clients found that when editing an outstanding voucher on the Voucher Maintenance (VOUM) form to include a new line item with GST tax amounts, GST tax percentage on the new line item was calculated correctly.  However, the rebate amount to the GST Rebate Account was not posted correctly, and caused a discrepancy between the Accounts Payable subsidiary ledger and the General Ledger.

The rebate tax amounts are now accurately reflected in the general ledger.

29201.37

Changing outstanding voucher with rebate/refund taxes creates bad postings

If a voucher was changed to delete one of the GL numbers from the line item and add a second line item using the same GL number and amount that was deleted from the first line item, then the posting records that were created from this change had incorrect amounts for the rebate tax amount.  The entire rebate/refund amount that was on the original line item was reversed. Only the amount that was moved to the second line item should have been reversed.

This issue has been corrected, and changes to outstanding vouchers are now accurately reflected in the general ledger.

29764.96

VOUM:  doesn't create reversing PJ transaction for a Purchase Order.

When a voucher associated with a Purchase Order was changed after it was made outstanding, a reversing PJ transaction was not created. This issue occurred when all items for the PO were accepted and a voucher was created, and then the user went back to the Voucher Maintenance (VOUM) form and removed unneeded items or deleted/adjusted the tax amount.   Posting was not created for the PJ transaction. 

Changes to outstanding vouchers are now accurately reflected in the general ledger.

30678.63

GLJM:  Numbers skipped on journal entries

Creating journal entries on the General Journal Manual Entry (GLJM) form could result in skipped journal entry numbers.  The form used a process to get the next journal entry key that did not guarantee the use of the next sequential number.  However, it did guarantee that the number was unique.  This issue was fixed previously on the Journal Entry (GLJE) form.

The GLJM form now uses a process that guarantees that the next available sequential number will be used.

32675.33

GLND: After loading SU29416.22, GL.ACCTS descriptions missing

An enhancement was delivered on the 2007 CF Summer Bundle (29416.22) to allow for the specification of what descriptions would be displayed in the GL account resolution when performing a LookUp for a GL account number. This was done by changing the LookUp to use the GL module description from the Descriptions Display (GLND) form. Unfortunately, if the GL module for GL account description was not defined on the GLND form, the LookUp would display nothing for the description.

The LookUp has been changed to display the default GL account description (which is the descriptions of the last two major components that are defined on the Account Structure Maintenance [GLAS] form), when the GL module description is not defined on the GLND form.

32728.75

GL.ACCTS component descriptions no longer include delimiter

An enhancement was delivered on the 2007 CF Summer Bundle (29416.22) to allow for the specification of what descriptions would display in the GL account resolution when performing a LookUp for a GL account number. This enhancement removed the colon (:) separator between the GL component descriptions that were being shown in the GL account resolution.

The GL account LookUp has been changed to include a colon as a separator between the GL component descriptions that are shown in the GL account resolution.

33154.96

VOUM/REQM/POEM/BPOM: GL# description missing on funds avail window

The 2007 CF Summer Bundle (29416.22) delivered a correction for funds availability for poolee accounts (28468.44  - RQIM/POIM: Available funds incorrect for poolee amounts). After this correction was released, the GL number description was no longer displayed in the funds availability window, which is displayed in the procurement document maintenance forms.

The process that calculates the information displayed in the funds availability window has been updated to correctly display the GL account description.

Change Request............: 36465.26

Summary...................: Colleague Advancement Planned Gift Conversion Update

Criticality...............: Release

Status....................: Complete

Date Completed............: 3/28/2008

Impact....................: High

Priority..................: A

Project...................:

Main Release ID...........:

Application...............: CA

Module Name...............: B2A

Mnemonic..................:

Problem/Issue.............:

Benefactor clients converting into Colleague Advancement needed the ability to convert their planned gifts so that donor giving histories are complete and so that fundraisers can track planned gifts that have yet to be satisfied.

Resolution................:

The Planned Gift conversion program enables clients to convert their Planned Gifts into Colleague Advancement, including planned giving information recorded in Benefactor's Planned Gift (PG) module and planned gifts recorded as pledges.  This software update delivers the necessary files and validation code tables necessary for the conversion program to run properly.

Technical:

Eight new validation code translation tables have been added.  These can be maintained on the Scan Benefactor Codes (ACP1) and the Benefactor Code Translation (ACP2) forms.

--BENCA.BEQUEST.TYPES

--BENCA.BENEFICIARY.TYPES

--BENCA.LEAD.SOURCES

--BENCA.LIFE.INCOME.TYPES

--BENCA.PG.PAY.FREQUENCIES

--BENCA.PLANNED.GIFT.STATUS

--BENCA.PROFESSIONAL.ROLES

--BENCA.TRUST.TYPES

--BENCA.VEHICLE.TYPES

The BENCA.DEGREE.DIVISIONS translation table has been updated to reflect that the Colleague equivalent is the OTHER.DIVISIONS file.

The B2A.PLANNED.GIFT ELF Specifications and Conversion programs have been delivered.  This allows the user to run the planned gift conversion found as step P7 of the conversion manager.  The validation step for P7 populates the INTER.PLANNED.GIFT file.  The update step for P7 populates the following Advancement files:

--CA.PAYMENT

--CONTRIBUTION

--CONTRIB.DONOR

--CONTRIB.DONOR.DESIG

--IN.KIND.CONTRIB

--INSURANCE.CONTRIB

--PLANNED.GIFT

--PLANNED.GIFT.BENFCY

--PLANNED.GIFT.REP

--SECURITIES.CONTRIB

--TANGIBLE.CONTRIB

The newly delivered Convert Actualized Gifts (ACU6) process takes the BENCA.AG file created during the planned gift preprocessor and converts the gift type contributions from a type of GF to AG, associating them to the appropriate planned gift. It also takes the pledge type contributions and converts their pledge payments from a type of PP to AG, associating them to the planned gift, and voids the pledge.   For full details, see the Converting from Benefactor to Advancement documentation.

Client Impact.............:

CLIENT IMPACT

Upon implementing this software update, you will be able convert Planned Gift data into Colleague Advancement.

IMPLEMENTATION INSTRUCTIONS

Not applicable.

TECHNICAL IMPLEMENTATION

Not applicable.

NEW FORMS

Convert Actualized Gifts (ACU6)

CUSTOM IMPACT

Not applicable.

SOFTWARE PARTNER

Not applicable.

Description...............:

UPDATE 3/28/08

****************************************

SU36465.26-1805*13 is available

****************************************

This software update delivers the Planned Gift Conversion programs and associated ELF processes for Colleague Advancement.

Change Request............: 36517.15

Summary...................: Column definitions for AR.INVOICES and AR.INVOICE.ITEMS

Criticality...............: Release

Status....................: Complete

Date Completed............: 3/28/2008

Impact....................:

Priority..................: B

Project...................:

Main Release ID...........:

Application...............: ARCR

Module Name...............: AR

Mnemonic..................:

Problem/Issue.............:

Some clients have reported performance issues when computing the net invoice amount for large numbers of invoices. 

Additionally, some clients have requested better access to the GL distribution of charges incurred by student course sections.

Resolution................:

This release adds four columns to the AR.INVOICES file to address to improve performance when computing net invoice amounts, and one new column to the AR.INVOICE.ITEMS file to make it easier to select how student course section charges are distributed among GL accounts.  The columns created in this release lay the ground work for the resolution to be delivered in subsequent release packages.

See the Description section for more information about the AnswerNet change requests resolved with this software update.

Client Impact.............:

Your database is prepared for additional software updates that will improve performance when computing net invoice amounts and to make it easier to select how student course section charges are distributed among GL accounts.

IMPLEMENTATION INSTRUCTIONS

Not Applicable

TECHNICAL IMPLEMENTATION

Not Applicable

NEW FORMS

Not Applicable

CUSTOM IMPACT

Not Applicable

SOFTWARE PARTNER

Not Applicable

Description...............:

3/28/08

This update must be loaded with updates 36531.04 and 36532.33.

The following software update has been released and are available to Clients:

xxxxxxxxxxxxxxxxxxxxxxx

SU36517.15-180510R

xxxxxxxxxxxxxxxxxxxxxxxx

Some clients have reported slow performance when computing the invoice amount for multiple invoices.  This release defines four new columns in the AR.INVOICES file. These new columns will be utilized in a subsequent release to improve performance.  The columns will contain the aggregate values of all the invoice's items for charges, credits, tax charges, and tax credits.  The new columns are:

INV.CHARGE.AMT

INV.CREDIT.AMT

INV.TAX.CHG.AMT

INV.TAX.CR.AMT

Further, some clients have asked for improved access to the way in which student course section charges are distributed among GL accounts.  This release defines a new column in the AR.INVOICE.ITEMS file that will be utilized in a subsequent release to better provide this information.  The new column contains the pointer to the STUDENT.COURSE.SECTIONS record that has incurred the charge.  The new column is:

INVI.STUDENT.COURSE.SEC

Change Request............: 36531.04

Summary...................: Modifications to maintain invoice aggregate amounts

Criticality...............: Release

Status....................: Complete

Date Completed............: 3/28/2008

Impact....................: High

Priority..................: B

Project...................:

Main Release ID...........:

Application...............: ARCR

Module Name...............: AR

Mnemonic..................:

Pre Install Instructions..:

The post-install utility provided with this update computes aggregate values for all invoices in the AR.INVOICES table.  Depending upon the number of invoices being processed, the post-install process may be lengthy.  The utility produces periodic status messages containing the number of invoices that have been updated and an Estimated Time to Completion (ETC).  These messages are written to the COMO file in addition to being written to the screen.  Datatel recommends that the UI Console window be opened prior to installing this update to facilitate monitoring the progress of the post-install utility.

Problem/Issue.............:

Some clients have reported performance issues when computing the net invoice amount for large numbers of invoices.

Resolution................:

This release addresses performance issues by dynamically maintaining aggregate values for an invoice's charges, credits, tax charges, and tax credits.  The aggregated values are stored in the following fields:

INV.CHARGE.AMT

INV.CREDIT.AMT

INV.TAX.CHG.AMT

INV.TAX.CR.AMT

Aggregate values will initially be populated by a post-install utility.  The procedures delivered on this release have been modified to dynamically maintain the aggregate amounts.

Client Impact.............:

Performance is improved when computing the net invoice amount for large numbers of invoices.

The fields aggregating the charges, credits, tax charges, and tax credits for an invoice will be available to clients for use in reporting, processing, and rules.

IMPLEMENTATION INSTRUCTIONS

Not Applicable

TECHNICAL IMPLEMENTATION

Not Applicable

NEW FORMS

Not Applicable

CUSTOM IMPACT

If you have modified any of the following processes, you will need to either implement the changes delivered with this software update into your customized software, or re-implement your customization to the software after loading this update:

FLNKB012

S.CREATE.AR.INVOICE

S.CREATE.PERSON.SPON.INVOICES

S.FLNK.UPDT.INVI.TAXES

S.REVERSE.INVOICE.POST

MCRG

AJIN

SOFTWARE PARTNER

Not Applicable

Description...............:

3/28/08

This update must be loaded with updates 36517.15 and 36532.33.

The following software update has been released and are available to Clients:

xxxxxxxxxxxxxxxxxxxxxxx

SU36531.04-180508R

xxxxxxxxxxxxxxxxxxxxxxxx

Some clients have reported performance issues when computing the net invoice amount for large numbers of invoices.  This release resolves those issues by dynamically maintaining aggregate values for an invoice's charges, credits, tax charges, and tax credits.  The aggregated values are stored in the following fields respectively:

INV.CHARGE.AMT

INV.CREDIT.AMT

INV.TAX.CHG.AMT

INV.TAX.CR.AMT

Aggregate values will initially be populated by a post-install utility.  The procedures delivered on this release have been modified to dynamically maintain the aggregate amounts.

Change Request............: 36532.33

Summary...................: Invoice amount performance enhancements

Criticality...............: Release

Status....................: Complete

Date Completed............: 3/28/2008

Impact....................: High

Priority..................: B

Project...................:

Main Release ID...........:

Application...............: ARCR

Module Name...............: AR

Mnemonic..................:

Problem/Issue.............:

Some clients have reported slow performance when computing the invoice amount for large numbers of invoices.

Resolution................:

The procedures delivered on this release have been enhanced to make use of the aggregate invoice amounts in the AR.INVOICES file.  Use of these aggregate values removes the necessity of summing the charges, credits, and taxes of an invoice's items.

Client Impact.............:

Clients will experience an increase in performance when retrieving the aggregate charges, credits, taxes, or net amount for an invoice.  Also, clients will see improved performance when accessing the computed columns INV.AMT, ARA.BALANCE, and STU.AR.BALANCE.

IMPLEMENTATION INSTRUCTIONS

Not Applicable

TECHNICAL IMPLEMENTATION

Not Applicable

NEW FORMS

Not Applicable

CUSTOM IMPACT

If you have modified any of the following processes, you will need to either implement the changes delivered with this software update into your customized software, or re-implement your customization to the software after loading this update:

S.CALC.INVOICE.AMT

S.GET.AR.ACCT.BALANCE

SOFTWARE PARTNER

Not Applicable

Description...............:

3/28/08

This update must be loaded with 36517.15 and 36531.04

The following software updates have been released and are available to Clients:

xxxxxxxxxxxxxxxxxxxxxxxx

SU36532.33-180504R

xxxxxxxxxxxxxxxxxxxxxxxx

Some clients have reported slow performance when computing the invoice amount for large numbers of invoices.  The existing procedures delivered on this release have been enhanced to make use of new aggregate invoice amount fields in the AR.INVOICES file.  Use of these aggregate values removes the necessity of summing the charges, credits, and taxes of an invoice's items each time these values are needed.

Change Request............: 36812.37

Summary...................: HR 2008 Bundle 1 Software Update

Criticality...............: Release

Status....................: Complete

Date Completed............: 3/28/2008

Impact....................: High

Priority..................: B

Project...................:

Main Release ID...........:

Application...............: HR

Module Name...............:

Mnemonic..................:

Problem/Issue.............:

Clients reported a number of issues with Colleague HR.  See the Description section for a list of issues resolved in this update.

Resolution................:

The Withholding Cycles per Year field has been added to the Accounting Information (BACT) form for benefits/deductions.  If you have entered a code in the Payroll Period Code field already on this form, then in the new field you can enter the actual number of pay cycles in which to deduct the benefit/deduction during the calendar year. The number of withholding pay cycles entered in this field overrides the person's primary position pay class when Colleague calculates the pay period amount of the benefit/deduction. This means you no longer have to inflate the annual cost to correctly calculate the pay period cost. The following processes also use the Withholding Cycles per Year to calculate the person's benefit/deduction pay period amounts:

-     Benefit Template Enroll (TEMP)

-     Benefit/Deduction Cost Update (BDCU)

-     Batch Enroll Benefit/Deduction (BEBD)

-     Batch Replace Benefit/Deduction (BRBD)

-     Life Insurance Premium Update (LIPU)

-     Benefit/Deduction Information (BENR) displays Withholding Cycles per Year.

The following forms no longer corrupt the year start date fields that are displayed as MM/DD:

- Leave Plan Definition (LEAD) 

- Benefit/Deduction Definition (BEND)

- Pay Class Definition (PCLS)

- Version Raise Rules (VRRR

The Leave Carryover Computation (LCOV) process now selects all the leave plans that match the date entered on the form. The process no longer updates leave records when run in Test Mode. The process can now be generated in the Tool Kit.

The Review Batch Wage Changes (RVWC) process now correctly updates the new wage records for the employees.

The process HRB034 has been corrected and it now generates properly.

The CSEN process now calculates the correct expiration date for months with less than 31 days and the process generates properly.

The Payroll Summary Register-Post process no longer creates duplicate AR postings.

Client Impact.............:

CLIENT IMPACT

Colleague HR is now easier to use.

IMPLEMENTATION INSTRUCTIONS

Not Applicable.

TECHNICAL IMPLEMENTATION

This software update will automatically run a post-install subroutine to correct any corrupt year start dates in the following files:

BENDED

- BD.PLAN.YR.START.DATE

LEAVPLAN

- LPN.YR.START.DATE

PAYCLASS

- PCLS.BGT.WAGE.START

- PCLS.BGT.WAGE.END

- PCLS.BGT.BEN.START

- PCLS.BGT.BEN.END

PBPOSPAY

- PBPPAY.BGT.WAGE.ST.DATE

- PBPPAY.BGT.WAGE.END.DATE

- PBPPAY.BGT.BEN.ST.DATE

- PBPPAY.BGT.BEN.END.DATE

SWVER

- SWV.RAISE.DATE

NEW FORMS

Not Applicable.

CUSTOM IMPACT

Not Applicable.

SOFTWARE PARTNER

Not Applicable.

Description...............:

03/28/08  -  The following software update has been released and is available to Clients:

*********************************

SU36812.37-1805*07

*********************************

This software update resolves the following issues:

39.779 - Ben/ded calc with 24 payments when pay cycle is 26 pay periods.

Clients have 26 pay dates per year, but some benefit/deductions are taken only 24 pay dates per year. To correctly calculate the pay-period amount, clients must inflate the annual amount.

15390.85 - The Leave Carryover Computation (LCOV) process was not selecting and displaying all the leave plans for the plan year start date entered on the form. The leave plans not selected were not being updated. The problem was caused when the user carriage-returned through the plan year start date on the Leave Plan Definition (LEAD) form, which corrupted the plan year start date. This problem also occurred on the Benefit/Deduction Definition (BEND) form, the Pay Class Definition (PCLS) form, and the Version Raise Rules (VRRR) form.

24166.41 - The LCOV process updated records when run in Test Mode.

36871.04 - The LCOV process did not generate in the Tool Kit. It was stalling when it reached HR.INSERTS HRB034 line FOR_EACH SECONDARY PERLVACC.ID.

28472.41 - When the Review Batch Wage Change (RVWC) process in R18 was run, the system produced an erroneous error message, such as "Not Processed: Yearly work time must be filled in." As a result, employees' wages were not updated.

5192.48 and 37491.85 - The Calculate Seniority (CSEN) process received an expression stack overflow error and terminated the process. The process was also calculating a corrupt expiration date. This could happen in months with fewer than 31 days.

Change Request............: 36957.37

Summary...................: FA Computed Column Updates

Criticality...............: Release

Status....................: Complete

Date Completed............: 3/28/2008

Impact....................: Medium

Priority..................: A

Project...................:

Main Release ID...........:

Application...............: FA

Module Name...............: FA

Mnemonic..................:

Problem/Issue.............:

T.SQL.SCRIPTS records must be updated to process the 2008/2009 financial aid year. Related computed columns and IS-type subroutines that reference file suite files required modification to take advantage of the new computed column functionality.

Resolution................:

T.SQL.SCRIPTS records with year-specific processing may now process the 2008 financial aid year.

Client Impact.............:

Datatel-delivered Financial Aid T.SQL.SCRIPTS records will continue to function for 2008/2009.

CUSTOM IMPACT

The following subroutines have been modified to require an additional argument; any custom code using these subroutines must also be changed:

- S.FA.STUDENT.OPE.ID

- S.FA.GE