Description:
Product Name    : TIBCO iProcess Engine (Oracle)
Release Version    : 10.5.0.10
Release Date    : March 2007

=============================================================
Note: This hotfix corrects the issues listed in the next section.

This release applies to a TIBCO iProcess Engine 10.5.0 running on
one of the following platforms:
- Sun SPARC; Solaris 8-10 with an Oracle 10g database
- IBM RS/6000; AIX 5L with an Oracle 10g database
- HP 9000; HP-UX 11-23 with an Oracle 9i database
- Intel Pentium x86; Red Hat Linux Enterprise AS (3.0) with an
   Oracle 10g database

=============================================================
Closed Issues in 10.5.0-HF10

Defect Id: CR 19812
  Use of IO parameter mappings of type "Expression" do not work in
  sub-procedures.

Closed Issues in 10.5.0-HF09

Defect Id: CR 19779
  Upgrade of the iProcess Engine reports an error if any part of the
  version number has a leading 0, for example, 10.0.0.09.

Defect Id: CR 19740
  The WQS does not pick up the WIS hostname after a crash or restart.

Defect Id: CR 19737
  iProcess Objects calls can fail when iProcess Objects is running on
  a slave node and round robin WIS allocation is NOT used.

Defect Id: CR 19703
  EAIMAIL is handling invalid email addresses incorrectly.

Defect Id: CR 19449
  An iProcess Objects Server can fail with a SUSPENDED error when
  keeping or releasing a step with a zero-byte memo field.
  
Defect Id: CR 19408
  Upgrading from a 10.5.0 version of iProcess Engine gives errors when
  upgrading process attributes.
  
Defect Id: CR 19340
  iProcess Engine processes can crash when a process attribute is
  deleted.

Defect Id: CR 19287
  The TIBCO iProcess Email Server Plug-in needs to support the RFC821
  Simple Mail Transfer Protocol.

Closed Issues in 10.5.0-HF08

Defect Id: CR 19705
  After doing a MOVESYSINFO you may not be able to access the queues.

Defect Id: CR 19647
  The TIBCO iProcess Objects Server process can crash if there is a
  problem connecting to the iProcess Engine database.

Defect Id: CR 19641
  The SWIP application cannot connect to the iProcess Engine.

Defect Id: CR 19606
  Long IAPJMS audit messages can be truncated prematurely and
  %USERNAME and %USERDESC are processed as %USER.

Defect Id: CR 19593
  If you install the iProcess Engine using an existing iProcess
  database, database errors occur.

Defect Id: CR 19563
  The processing of a case stops after a sub-procedure call if:
  - the sub-procedure call contains an output mapping script and
  - the sub-procedure does not contain any normal steps (for example,
    it only contains EAI steps or complex routers etc).
    
  This causes the main procedure to show as completed even though no
  steps after the sub-procedure call have been executed.

Defect Id: CR 19509
  Complex filtering does not work on CDQP fields. A simple filter, for
  example LAST="hello" works but a complex filter like LAST="hello" OR
  LAST="goodbye" does not.

Defect Id: CR 19489
  A case step can only be forwarded once.
        
Defect Id: CR 19463
  If the deadline for a deadline withdraw is changed (by dynamic
  deadlines) to a date in the past, the step is not withdrawn.

Defect Id: CR 19446
  If a client process is sending lots of requests to the WIS process
  on a single-CPU machine (for example, an iProcess Objects Server
  requesting full-item-details on each item in a queue), then the WIS
  process can start to respond slowly.

Defect Id: CR 19421
  The WIS process can crash if QueueDeltas are being used and X
  debugging is turned on.
  
Defect Id: CR 19401
  A problem in Oracle 10gR2 can cause the WORKER process to crash
  when publishing an event during startup or shutdown. (See Oracle
  fault <&ltBug:5658402>> OCIAQENQ LATE MUTEXING OF SVCCTX CAUSES
  OCI-21500 IN THREADED APP.)

Defect Id: CR 19397
  Changes to the lock status of work items are not counted as changes
  to queues for the purpose of monitoring changes in queues, so if a
  user just locks or keeps an item without making any other changes
  to a queue, then iProcess Objects or the SAL does not flag that any
  changes have been made to the queue, and even if the queue is
  refreshed, no changes are apparent.
    
  A new process attribute for WIS processes has been introduced:
  
  WIS_QCHANGE_EXTENDED_CHECK which can be set to 0 or 1 (defaults to 0
  if not present.)  
    
  This process attribute is not installed by the installer.
    
  If the above process attribute is set to 1 then it changes
  the behavior of the WIS as follows:
    
  On open, open first unlocked and keep of work items, the QPAR
  version number is updated (and the OREC version number
  is incremented) which allows the Queue Delta feature to
  detect those changes in the queue.

Defect Id: CR 19383
  If prediction hits the MAX_PREDICTION_LOOPS limit an error is
  returned and no future steps are returned.

Defect Id: CR 19372
  The BG process (swbgmbd) has a small memory leak every time a case
  is started.

Defect Id: CR 19365
  If an EAI step assigns an iProcess Table Keyfield (1st subfield),
  and the length of the last field being assigned is shorter than the
  data being assigned to the keyfield, then the keyfield value will
  be truncated to the length of the last field.
  
Defect Id: CR 19353
  The SHLIB_PATH environment variable contains multiple occurrences
  of the SWLIB_PATH environment variable after system startup.
  
Defect Id: CR 19278
  The watcher sentinel does not always stop on UNIX Oracle systems
  because the worker sentinel can exit while still leaving Oracle
  shadow processes running.

Defect Id: CR 19291
  Changes to the contents of a form are not visible after saving the
  procedure and re-opening the form.
  
Defect Id: CR 19192
  The "Sub-procedure step completed" audit entry is written before
  the "Sub-procedure case completed" entry.

Defect Id: CR 19188
  The entries in the port_range_active table are cleared when a
  slave server in a node cluster is restarted. This means the iProcess
  Clients can no longer see the work queues as they cannot connect to
  the iProcess Engine processes.

Defect Id: CR 19148
  When using the multiple firewall implementation introduced in
  v.10.5.0:
  - The swadm set_range command that puts a specified machine ID
    behind a firewall does not work.
  - If ports are in use that are within the defined range then the
    server processes do not skip over them as they should.

Defect Id: CR 19136
  After performing a ldapsync, if the server stops you can get a
  "PARTIAL RESULTS. Not all User entries returned from LDAP Servers"
  message.
  
Defect Id: CR 19075
  A case start started by a stored procedure can create a case
  started by "Undelivered work items".

Defect Id: CR 18982
  If an error occurs during an LDAP synchronization, all user and
  group information can be lost.

Defect Id: CR 18877
  iProcess Engine activity monitoring can cause the BG process to
  crash if long audit messages are generated.

Defect Id: CR 18313
  When performing an LDAP synchronization for a large number of groups
  with multi-user membership, the BG process can crash.

Defect Id: CR 17415
  If port ranging is enabled and some of the ports are already being
  used, a file handle leak occurs.
  
Defect Id: CR 16771
  A sub-procedure will not return to a parent procedure if:
    - the parent procedure that calls it is migrated to a new version and
    - the previous versions of the parent procedure are deleted.
    
Defect Id: CR 16287
  Page level locking is used on the staffo table which causes
  contention between WIS processes.
  
Defect Id: CR 13930
  If a command is issued in a SERVERRUN command and it fails, the
  TIBCO iProcess Client does not recognize this. This causes
  the iProcess Client to go into a loop until it times out. This
  problem is caused because the numeric value returned by the failed
  command matches the numeric value returned by a running process.
  
  Corrected. The SERVERRUN now returns a different numeric value.
  
=============================================================
Restrictions
  
  Defect ID: CR 19329
  Summary: The process attribute SWLIB_PATH was introduced in v.10.5.0
   to extend the SHLIB_PATH for use with IAPJMS. However, it is set by
   default against all processes, and this can create a conflict with
   the iProcess Java Plug-in.
  
  Workaround: Set SWLIB_PATH to the value 0 IAPJMS 0 rather than
   0 ALL 0. See the description of SWLIB_PATH in the iProcess Engine
   Administrator’s Guide for further details.
           
=============================================================

The TIBCO iProcess Engine (Oracle) HotFix 10 can be downloaded from our support-ftp.tibco.com. You will be able to download by clicking on the link below after you provide your TIBCO Support Web username and password in the url:

                     ftp://username:password@support-ftp.tibco.com

Directory path:
StaffwareProcessSuite/iProcess/engine/oracle/10.5.0/hotfix-10