TekAdmin V2.10.006
Copyright (c) 2000-2003.  Teknowledge Corporation.  All Rights Reserved.

1/13/2003


Overview
- Executive Administrator
  - Issue: Reports (Batch and Aggregated Accounts) were not picking up the 
      changes to the PROCESS_NAME field for TekCapture.  This field is now 
      filled in by TekCapture@IPAddress
    Resolution: Modify SQL statements from PROCESS_NAME='TekCapture' to be 
      PROCESS_NAME like 'TekCapture%'
  - Issue: Sub-reports wouldn't work for large numbers of records
    Resolution: Link back/next buttons to only get the amount of information
      specified by the UI.RecordsPerPage property on each page.
  - Issue: SQL Statement for Inactive wouldn't work with Oracle
    Resolution: Convert TABLE AS X to TABLE X in SQL statements


Requirements
- TekAdmin V2.1 Patch 005


Installation Instructions
- Log on to each of the TekAdmin Application Server(s).
- Solaris
  - Login as tekp (or your J2EE Application Server id)
  - Stop your J2EE Application Server
  - Note: The instructions below assume you installed TekAdmin in
    the root directory; if this is not the case, please replace that
    with the directory you installed TekAdmin.  Also, if you are
    using a different id/group, please replace those with yours.
  - uncompress -c TekAdmin_V2.10.006.tar.Z | (cd /; tar -xvf -)
  - chown -R tekp:tekp /TekAdmin/*
  - chmod -R 750 /TekAdmin/*
  - Note: If any JSP files are updated, they are purposely 
    extracted into the Tpx2.Patch006 directory to not overwrite 
    any changes you may have made.  You must copy them over to the 
    Tpx2 explicitly.
  - Start your J2EE Application Server
- Windows NT/2000
  - Stop your J2EE Application Server
  - Run TekAdmin_V2.10.006.exe and extract to c:\ (or wherever
    you have installed TekPortfolio)
  - Note: If any JSP files are updated, they are purposely 
    extracted into the Tpx2.Patch006 directory to not overwrite 
    any changes you may have made.  You must copy them over to the 
    Tpx2 explicitly.
  - Start your J2EE Application Server


Summary of Changes
- Note: The following are the specific files that have changed.  If you have
  made any custom modifications to these files, you will need to reapply
  those changes to these new versions; or else these versions will overwrite
  your custom modifications.
*****************  TP_UI_EX_ReportsBatch.java  *****************
Issue: Reports were not picking up the changes to the PROCESS_NAME
field for TekCapture.  This field is now filled in by TekCapture@IPAddress
Resolution: Modify SQL statements from PROCESS_NAME='TekCapture' to be
PROCESS_NAME like 'TekCapture%'
*****************  TP_UI_EX_ReportsAggAct.java  *****************
Issue: Reports were not picking up the changes to the PROCESS_NAME
field for TekCapture.  This field is now filled in by TekCapture@IPAddress
Resolution: Modify SQL statements from PROCESS_NAME='TekCapture' to be
PROCESS_NAME like 'TekCapture%'
*****************  TekAdmin_EX_BillingSingle_en.jsp  *****************
Issue: Crashed if values in Partner were null
Resolution: If Parnter values are null, use 0
*****************  TP_UI_EX_ReportsUser.java  *****************
Issue: Sub-reports of User Summary wouldn't work for large numbers
of records
Resolution: Link back/next buttons to only get the amount of information
specified by the UI.RecordsPerPage property on each page.

Issue: SQL Statement for Inactive wouldn't work with Oracle
Resolution: Convert TABLE AS X to TABLE X in SQL statements
*****************  TekAdmin_EX_UserSummary_en.jsp  *****************
Issue: Sub-reports wouldn't work for large numbers of records
Resolution: Link back/next buttons to only get the amount of information
specified by the UI.RecordsPerPage property on each page.
*****************  TekAdmin_EX_UserSummaryDetail_en.jsp  *****************
Issue: Sub-reports wouldn't work for large numbers of records
Resolution: Link back/next buttons to only get the amount of information
specified by the UI.RecordsPerPage property on each page.