===============================================================================
Product Name   : TIBCO iProcess(R) Engine (SQL Server)
Release Version: 11.9.0_HF-002
Release Date   : January 2023

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

 This is a full distribution set.

 For detailed installation instructions, see TIBCO iProcess Engine
 Installation guide.

===============================================================================
Affected Files for 11.9.0_HF-002 (This Release)

 This is a full distribution set.

===============================================================================
Closed Issue in 11.9.0_HF-002 (This Release)

IPE-6011
The SPO/WQS process crashes intermittently on updating keys and in the event
of concurrent log-in sessions.

===============================================================================
Closed Issues in 11.9.0_HF-001

IPE-5954 (Parent Id: IPE-5891)
The WQS process crashes in the event of concurrent log-in sessions.

IPE-5942
When iProcess Engine is upgraded from 11.7.0 to 11.9.0, on opening the EAIDB
step in an existing procedure, the Database name is incorrectly fetched as
Server name.

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

Defining the Database Stored Procedure to call a ‘Process Step’ or a
‘Withdraw Step’ can be categorized with respect to populating the Stored
Procedure drop-down as follows:

1. With Server and/or Database name in input:

   The Stored Procedure drop-down populates the list of stored procedures
   fetched from the given details and in the following format.

   <SCHEMA>.<StoredProcedure> – all procedures from the given database and
   that are accessible to the foreground user are displayed
   (with schema name).

   The behavior is same for the new EAIDB step or an Edit step.

2. Without Server and Database name in input:

   The Stored Procedure drop-down for new step populates the list of stored
   procedures fetched from the iProcess Engine’s database and in the following
   formatted lists.

   a) <SCHEMA>.<StoredProcedure> – stored procedures from the non-default
   schema of the foreground user (all other schemas from the iProcess Engine
   database, other than your default schema) are displayed with the schema
   name.

   b) <StoredProcedure> – stored procedures from the default schema of the
   foreground user are displayed without schema name. There is a process
   attribute to suppress this behavior. For example, in the event when you
   want to view the procedures from default schema along with schema name.

   The 'DEF_SCHEMA_PROCS_FORMAT' process attribute controls the display format
   of the stored procedures from default schema. This attribute has no effect
   on the stored procedures 'point a' display.
 
   The role or behavior of process attribute value is described as follows:

   1 - displays the stored procedures from default schema in the
   <StoredProcedure> format

   2 - displays the stored procedures from default schema in the
   <SCHEMA>.<StoredProcedure> format

   0 or not set – behaves the same as 1

   Note: This is applicable only to 'point b'.
 
   Edit has a different behavior occasionally as the Stored Procedure drop-down
   can be populated from two paths:

   a. When the dialog is loaded after clicking the new step:

   The drop-down list format matches with the already configured procedure
   name to retain the designed format and respect your original intention.

   The 'DEF_SCHEMA_PROCS_FORMAT' process attribute has no effect on the step
   initial load.

   b. When ‘Refresh’ is clicked:

   The drop-down list format matches with the already configured procedure
   name. You have an option to override this behavior by setting the
   'DEF_SCHEMA_PROCS_FORMAT' process attribute.  
 
   The role or behavior of process attribute value is described as follows:

   1 - displays the stored procedures from default schema in the
   <StoredProcedure> format

   2 - displays the stored procedures from default schema in the
   <SCHEMA>.<StoredProcedure> format

   0 or not set – displays the stored procedures in the format of the already
   configured procedure name.

   Note:
   
   a) Overriding the behavior might result in procedure name mismatch error
   that was configured earlier, and is expected if you intend to modify the
   procedure name or the associated parameters.
   
   b) To view optional parameters in store procedure EAIDB step correctly,
   you must provide the 'View Definition' permissions to the stored
   procedure. This is applicable only if you connect to an external database
   or server.
 
From the 11.9.0 version, '@' is removed from the parameter name. For all the
previous versions, steps are auto-migrated for display and a permanent change
is applied on the step's first edit.