===============================================================================
Product Name   : TIBCO iProcess(R) Workspace (Windows)
Release Version: 11.9.0_HF‐006
Release Date   : April 2024    

===============================================================================
Installation

 1. Shut down TIBCO iProcess Workspace (Windows).

 2. Back up the following existing files from the TIBCO iProcess
    Workspace (Windows) installation directory
    (For example, C:\TibcoiProcessWorkspace) to a safe location
    that must be outside of the installation directory.
    
      - eai_plugins\EAIDB\eaidb.eag
        - eai_plugins\EAIDB\eaidb_gwdrc.dll

 3. Copy the new files into the appropriate directory
    (For example, C:\TibcoiProcessWorkspace) overwriting the existing files,
    leaving the permissions and ownership as they are.

 4. Restart TIBCO iProcess Workspace (Windows).

Note: For debugging purposes, copy the debug version of the files and
pdb files from the debug folder of the hotfix to the install location
of TIBCO iProcess Workspace (Windows).
 
===============================================================================
Affected Files for 11.9.0_HF‐006 (This Release)
 - eaidb.eag
 - eaidb_gwdrc.dll

==============================================================================
Closed Issue in 11.9.0_HF‐006 (This Release)

IPWW-937
EAIDB Ora - Procedure Lookup failed error.

==============================================================================
Additional Information

This fix effectively operates with TIBCO iProcess(R) Engine (Oracle) 11.9.0.6
and subsequent versions.

When configuring EAIDB step for a local database server, either leave the
Server field empty or set it to the local Database Name (v$database value of
iProcess Engine DB, not TNS identifier nor Oracle SID). For a remote database,
use the remote DBLink name (configured on the iProcess Engine DB).

With this fix, there is a provision to list procedures from multiple schemas,
but the Database field can only take a single schema. Do not enter
comma-separated value as it leads to a run-time failure), and the extended
list of schemas can be configured using the EAIDB_PROCS_SCHEMAS process
attribute described below.

The Stored Procedure drop-down for EAIDB step is displayed with the list of
Stored Procedures fetched from iProcess Engine schemas (SWUSER, SWPRO) and
list of schemas configured in EAIDB_PROCS_SCHEMAS process attribute. The
stored procedure names are displayed in the following formats:

- <PackageName>.<StoredProcedure>: stored procedures from all packages.
   The stored procedure name is prefixed with packagename when
   displayed in the drop-down.
   The DEF_SCHEMA_PROCS_FORMAT process attribute has no effect
   on this display.
-  <StoredProcedure>: all stored procedures from given schemas. The
   procedure name does not display the owner name in the drop-down
   unless the behavior is modified by the DEF_SCHEMA_PROCS_FORMAT
   process attribute.
    
Two new process attributes are introduced with this fix. They are
applicable to the design-time EAIDB step:

- DEF_SCHEMA_PROCS_FORMAT: To control the display format of the stored
  procedure names. Valid values are 0, 1 and 2.
- EAIDB_PROCS_SCHEMAS: To add additional schema names for procedure lookup.
  Valid format: <schema>[,<schema>][,<schema@dblink>]...

Defining the Database Stored Procedure to call a ‘Process Step’ or a
‘Withdraw Step’ can be categorized into:

1. New Step:

   The DEF_SCHEMA_PROCS_FORMAT process attribute can override the  
   behavior of Procedure drop-down as follows:    

   1 - displays the stored procedures in <StoredProcedure> format
   2 - displays the stored procedures in <Owner>.<StoredProcedure> format
   0 or not set – behaves the same as 1

2. Edit Step:

   The Edit Step has a different behavior depending on the action, the
   drop-down can be populated from two paths:

   a. When the dialog is loaded after clicking on ‘Edit’ step.
      The drop-down list format matches the already configured
      Procedure Name. This is mainly to retain the designed format and
      respect the original intention of the user.
      
      Process Attribute 'DEF_SCHEMA_PROCS_FORMAT' has no effect on step
      initial load.

   b. When ‘Refresh’ is clicked.
      The drop-down list format matches the already configured
      Procedure Name. Here, user has an option to override this behavior
      by setting process attribute 'DEF_SCHEMA_PROCS_FORMAT'.  

The DEF_SCHEMA_PROCS_FORMAT process attribute can override the
behavior of the Stored Procedure drop-down as follows:
1 - displays the stored procedures in <StoredProcedure> format
2 - displays the stored procedures in <Owner>.<StoredProcedure> format
0 or not set – displays the stored procs in the format of the
               already configured Procedure Name.

NOTE: The DEF_SCHEMA_PROCS_FORMAT process attribute gives the
flexibility of overriding the default format of the Procedure Name
drop-down, which is needed for backward compatibility with existing
iProcess Procedures. However, we recommend that you use it
cautiously. Otherwise, it could lead to design-time and/or
run-time failures.