TIBCO iProcess Workspace (Windows) Release Notes€¦ · (windows) release notes software release...

TIBCO iProcess® Workspace (Windows)

Release NotesSoftware Release 11.3.0October 2011

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc.TIBCO, The Power of Now, TIBCO ActiveMatrix BusinessWorks, TIBCO iProcess, TIBCO iProcess Suite and TIBCO Enterprise Message Service are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.EJB, Java EE, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.Copyright © 1999-2011 TIBCO Software Inc. ALL RIGHTS RESERVED.TIBCO Software Inc. Confidential Information

| iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiHow to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiHow to Access All TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiHow to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 11.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 11.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Release 11.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Release 11.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Release 11.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Release 11.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Earlier Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Deprecated Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Release 11.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Release 11.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Release 11.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Release 11.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Release 11.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Release 11.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Change History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Release 11.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Release 11.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Release 11.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Release 11.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Release 11.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Release 11.0.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Release 11.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Earlier Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Other Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

TIBCO iProcess Workspace (Windows) Release Notes

iv | Contents

Enabling or Disabling Prediction on a Procedure Only Affects Background Case Prediction . . . . . . . . . . . . 23Discrepancy in the Display of Large Decimal Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Product Re-branding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23


| v

Preface

TIBCO iProcess Workspace (Windows) allows you to define and manage iProcess procedures.

Topics

• Typographical Conventions, page vi

• Connecting with TIBCO Resources, page viii


vi | Typographical Conventions

Typographical Conventions

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

Convention Use

code font Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example:

Use MyCommand to start the foo process.

bold code

font Bold code font is used in the following ways:

• In procedures, to indicate what a user types. For example: Type admin.

• In large code samples, to indicate the parts of the sample that are of particular interest.

• In command syntax, to indicate the default parameter for a command. For example, if no parameter is specified, MyCommand is enabled: MyCommand [enable | disable]

italic font Italic font is used in the following ways:

• To indicate a document title. For example: See TIBCO ActiveMatrix BusinessWorks Concepts.

• To introduce new terms For example: A portal page may contain several portlets. Portlets are mini-applications that run in a portal.

• To indicate a variable in a command or code syntax that you must replace. For example: MyCommand PathName

Key combinations

Key name separated by a plus sign indicate keys pressed simultaneously. For example: Ctrl+C.

Key names separated by a comma and space indicate keys pressed one after the other. For example: Esc, Ctrl+Q.

The note icon indicates information that is of special interest or importance, for example, an additional action required only in certain circumstances.

The tip icon indicates an idea that could be useful, for example, a way to apply the information provided in the current section to achieve a specific result.


Preface | vii

The warning icon indicates the potential for a damaging situation, for example, data loss or corruption if certain steps are taken or not taken.

Table 1 General Typographical Conventions (Cont’d)

Convention Use

Table 2 Syntax Typographical Conventions

Convention Use

[ ] An optional item in a command or code syntax.

For example:

MyCommand [optional_parameter] required_parameter

| A logical OR that separates multiple items of which only one may be chosen.

For example, you can select only one of the following parameters:

MyCommand para1 | param2 | param3

{ } A logical group of items in a command. Other syntax notations may appear within each logical group.

For example, the following command requires two parameters, which can be either the pair param1 and param2, or the pair param3 and param4.

MyCommand {param1 param2} | {param3 param4}

In the next example, the command requires two parameters. The first parameter can be either param1 or param2 and the second can be either param3 or param4:

MyCommand {param1 | param2} {param3 | param4}

In the next example, the command can accept either two or three parameters. The first parameter must be param1. You can optionally include param2 as the second parameter. And the last parameter is either param3 or param4.

MyCommand param1 [param2] {param3 | param4}


viii | Connecting with TIBCO Resources

Connecting with TIBCO Resources

How to Join TIBCOmmunityTIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts, a place to share and access the collective experience of the TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety of resources. To register, go to http://www.tibcommunity.com.

How to Access All TIBCO DocumentationAfter you join TIBCOmmunity, you can access the documentation for all supported product versions here:

http://docs.tibco.com/TibcoDoc

How to Contact TIBCO SupportFor comments or problems with this manual or the software it addresses, please contact TIBCO Support as follows.

• For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site:

http://www.tibco.com/services/support

• If you already have a valid maintenance or support contract, visit this site:

https://support.tibco.com

Entry to this site requires a user name and password. If you do not have a user name, you can request one.


http://www.tibco.com/services/support

https://support.tibco.com

http://docs.tibco.com/TibcoDoc

http://www.tibcommunity.com

| 1

Release Notes

Check the TIBCO Product Support web site at http://support.tibco.com for product information that was not available at release time. Entry to this site requires a username and password. If you do not have a username, you can request one. You must have a valid maintenance or support contract to use this site.

Topics

• New Features, page 2

• Deprecated Features, page 6

• Compatibility, page 7

• Change History, page 8

• Restrictions, page 16

• Known Issues, page 20

• Other Information, page 23


http://support.tibco.com

2 | Release Notes

New Features

This section lists features added since the last major release of this product.

Release 11.3.0The following are new features in this release.

Disable the Browse Button in the iProcess Workspace (Windows) and iProcess Administrator Login Dialogs (IPWW-192)

The Browse button in the iProcess Workspace (Windows) and iProcess Administrator login dialogs can be disabled.

To disable the Browse button, complete the following steps:

1. Navigate to IPWWDIR, and double-click swpref.exe. The iProcess Preference Editor dialog is displayed.

2. Click the Advanced button, the Advanced Options dialog is displayed.

3. Check the Disable Browse Button checkbox, and click the OK button twice.

Uncheck the Disable Browse Button checkbox to enable the Browse button.

Select Which Work Item Is Highlighted After a Work Item Is Released (IPWW-178)

You can now configure which work item is highlighted after another work item is released. The work item above the released one is highlighted by default. You can select to highlight the work item below the released one.

To highlight the work item below the released one, complete the following steps:

1. Navigate to IPWWDIR, and double-click swpref.exe. The iProcess Preference Editor dialog is displayed.

2. Click the Advanced button, the Advanced Options dialog is displayed.

3. Check the Highlight Next Item After Release checkbox, and click the OK button twice.

Uncheck the Highlight Next Item After Release checkbox to restore the default setting.

Optionally Migrate Only Live Cases

You can choose to migrate only live cases from previous versions to a new version by using iProcess Workspace (Windows) in one of the following ways:


New Features | 3

• Via the main window

a. In the Procedure Manager, select the procedures you want to release.

b. Click the Release Procedure button. A dialog is displayed showing the procedures and versions that will be released and withdrawn if you continue, as shown in Figure 1.

Figure 1 Release Procedures Dialog via Main Window

c. Check the Migrate Cases To New Related Version(s) checkbox to enable the Only Migrate Live Cases radio button.

d. Click the Only Migrate Live Cases radio button to migrate only live cases.

• Via the Version Control window

a. In the Procedure Manager, select the procedures you want to release.

b. Click the Version Control button or double-click a single procedure in the Procedure Manager. The Version Control window is displayed.

c. Select the version you want to release, and click the Version Control button.

d. Fill in information in the displayed dialog, and click the OK button. A dialog is displayed, as shown in Figure 2.


4 | Release Notes

Figure 2 Release Procedures Dialog via Version Control Window

e. Click the Migrate Live Cases To New Procedure Definition Version radio button to migrate only live cases.

Release 11.1.3There are no new features in this release.


Release 11.1.1The following are new features in this release.

Additional Platform Support - Microsoft Windows

TIBCO iProcess Workspace (Windows) now supports Microsoft Windows 7 Professional.




New Features | 5

Earlier VersionsFor details of the new features implemented in earlier versions of the product, see the readme file and release notes for that particular product.


6 | Release Notes

Deprecated Features

This section describes deprecated features and lists equivalent features that accomplish the same result, if relevant. Any use of a deprecated feature should be discontinued as it may be removed in a future release. You should avoid becoming dependent on deprecated features and become familiar with the equivalent feature.

Release 11.3.0No features are deprecated in this release.







Compatibility | 7

Compatibility

In addition to other Version 11 TIBCO iProcess Suite™ components, the following TIBCO products have been successfully tested for compatibility with iProcess Workspace (Windows) Version 11.3.0.

If you have any queries regarding product compatibility with this version of iProcess Workspace (Windows), please contact TIBCO Support for further assistance.

Product Version(s)

TIBCO iProcess® Decisions Client Plug-in Version 10.3.0

TIBCO iProcess® Web Services Client Plug-in Version 10.6.1

TIBCO iProcess® Workspace Plug-ins Versions 11.2.0


8 | Release Notes

Change History

The following Modification Requests (MRs) have been implemented since the last major release of TIBCO iProcess Workspace (Windows).

Release 11.3.0

Defect # Description

IPWW-198

(Parent JIRA IPWW-196)

The send_keys() function did not work with Windows 7 with UAC enabled.

Corrected.

IPWW-192 Allows a user to disable the Browse button in the TIBCO iProcess Workspace (Windows) Login dialog and TIBCO iProcess Administrator Login dialog.

Implemented. See Disable the Browse Button in the iProcess Workspace (Windows) and iProcess Administrator Login Dialogs (IPWW-192) on page 2.

IPWW-189


Work queues did not refresh on one server in a node cluster architecture after upgrading the iProcess Engine, even though the Check For New Work Period field was set to a new value.

Corrected.

IPWW-188


Adding a sub-procedure call to a procedure definition using the drag-and-drop method in TIBCO iProcess Modeler caused TIBCO iProcess Workspace (Windows) to fail while in UTF-8 mode.

Corrected.

IPWW-187


Cases disappeared from Work Queue Manager after opening a case from a queue.

Corrected.

IPWW-186


Occasionally, after searching for and selecting a work item in a queue, the work item opened was not the one selected.

Corrected.

IPWW-185


TIBCO iProcess Workspace (Windows) failed when calling the winfind function.

Corrected.


Change History | 9

Release 11.1.3

IPWW-183


Under certain circumstances, the four WQ parameters shown in the TIBCO iProcess Workspace client (for example, WQ parameters1) disappeared.

Corrected.

IPWW-182


Multiple cases could not be forwarded simultaneously from one group queue to another.

Corrected.

IPWW-181


Performance was low when loading many users or groups into the user manager.

Corrected.

IPWW-179


When the total number of characters in the Supervisor field was greater than 24, supervisors could not be set to monitor users.

Corrected.

IPWW-178


Provide user an option to determine which work item is highlighted after release of a work item.

Implemented. See Select Which Work Item Is Highlighted After a Work Item Is Released (IPWW-178) on page 2.

IPWW-177


In the TIBCO iProcess Workspace (Windows) client, importing a procedure into TIBCO iProcess Engine failed if a procedure with the same name already existed there.

Corrected.


IPWW-180 The TIBCO iProcess Workspace (Windows) client crashed when dragging and dropping a sub-procedure into a procedure definition.

Corrected.

IPWW-176 In the TIBCO iProcess Workspace (Windows) client, importing a procedure into TIBCO iProcess Engine failed if a procedure with the same name already existed there.

Implemented.



10 | Release Notes

Release 11.1.2

IPWW-174 Performance was low when loading many users or groups into the user manager.

Corrected.


IPWW-169 Workspace windows crashed when calling the winfind function.

Corrected.

IPWW-170 Extra debug messages were added to further investigate why the refresh-function (updating) for the work queues did not work.

Implemented.

IPWW-171 After searching for and selecting a work item in a Queue, a different work item from the one selected might be opened.

Corrected.

IPWW-172 Cases disappeared from Work Queue Manager after opening a case from a queue.

Corrected.

MR 43606 When the total number of characters in the Supervisor field was greater than 24, supervisors could not be set to monitor users.

Corrected.

MR 43614 Multiple cases could not be forwarded simultaneously from one group queue to another.

Corrected.

MR 43618 In certain circumstances, the four WQ parameters shown in the TIBCO iProcess Workspace client (for example, WQ parameters1) disappeared.

Corrected.

MR 43527 The TIBCO iProcess Workspace client crashed.

Implemented the following actions:

- Added more information into the log.

- Changed the condition of freeing the memory of the script data.



Change History | 11

Release 11.1.1

MR 43412 After upgrading TIBCO iProcess Engine or TIBCO iProcess Workspace (Windows) from a lower version to version 11.1.1, an error occurred in TIBCO iProcess Engine script if there was no space between a keyword and parentheses in the script.

Corrected.


MR 43019 Arrival Time for all work items was displayed as "01/01/2000 00:00".

Corrected.

MR 42986 When defining a procedure with an EAI email step and the correct SMTP server information, if you repeatedly clicked the Test Connection button, sometimes TIBCO iProcess Workspace (Windows) crashed.

Corrected.

MR 42949 After exporting a procedure as an XPDL file, then importing the file into the TIBCO iProcess Workspace (Windows) again, the defined links in the specific situation were not correct.

Corrected.

MR 42819 The dot character (.) was not accepted in the server field when defining an EAIDB in the TIBCO Workspace.

Corrected.

MR 42659 The filter changed after the Case Data Queue Parameters (CDQP) was imported.

Corrected.

MR 42506 An error occurred in Microsoft IE 7.0 or 7.0+ when openning a procedure saved to HTML format, and then clicking the Printable View button.

Corrected.

MR 42174

(Parent MR 4628)

An error occurred if the parameter length of the Winrun command was greater than 127 characters.

Corrected.



12 | Release Notes

MR 42171

(Parent MR 41719)

If one CDQP definition had been imported and another one was imported afterwards, the selected CDQP fields displayed were not correct.

Corrected.

MR 41702

(Parent MR 39747)

When changing the order of the fields and columns displayed in the USER-Workqueue, the order in the GROUP-Workqueue was also changed, or vice versa.

Corrected

MR 41701

(Parent MR 41677)

After installing TIBCO iProcess Workspace (Windows) 11.1.0 , the iProcess Modeler .dlls would be called statically, no matter which type had been chosen.

Corrected.



Change History | 13

Release 11.1.0

Release 11.0.2

Release 11.0.0


MR_39675 Graphical Workflow definer (GWD) Object IDs can get very large when copying and pasting objects, causing GWD to be very slow to load procedure definitions.

Corrected.

MR 38669 (Parent MR 30847)

If an iProcess script contains a long expression which is split over multiple lines using the '\' character it cannot be correctly exported / imported as XPDL.

Corrected.

MR 39968 (Parent MR 38944)

Unable to change user passwords from iProcess Workspace (Windows).

Corrected.

MR 40255 (Parent MR 33317)

TIBCO iProcess Workspace (Windows) incorrectly deduces a user's access rights for a procedure.

Corrected.


No MR Internal build issues only.


MR 34049 The 'Del' key does not work in iProcess Workspace (Windows) procedure version list.

Corrected.

MR 33220 Remove the PTHREAD.DLL file from the server and client installation sets and make available from the download site. See TIBCO iProcess Engine Installation guide for more information.

Implemented.


14 | Release Notes

MR 33012 If a crash occurs while an Administrator user is logged into the iProcess Administrator, when the Administrator logs back in to the iProcess Administrator, a message is displayed asking the user if they want to override the lock. However, the lock is not overridden and no users can access the locked area.

Corrected.

MR 32962 (Parent MR 31870)

The localized Korean version of iProcess Workspace (Windows) shows question marks in the Save As dialog.

Corrected.

MR 32961 (Parent MR 32264)

When using the User Manager in the iProcess Administrator to export user, groups and roles, the iProcess Administrator crashes.

Corrected

MR 32954 (Parent MR 32421)

If a procedure:

— includes a sub-procedure call step that calls 3 sub-procedures,

— and two of the sub-procedures can be completed automatically

— and one of the sub-procedures contains a step that requires interaction with a user

then, when the automatic sub-procedures have completed, the iProcess Engine thinks the procedure has finished, even though the third sub-procedure (that requires interaction from a user) has not.

Corrected.

MR 32951 (Parent MR 30981)

iProcess Modeler exports that include a sub-process reference are not exporting the sub-process when saved as xpdl.

Corrected.

MR 32950 (Parent MR 32201)

Entering a very large number as an I/O parameter does not throw an error.

Corrected.

MR 31205 None of the system / user attribute fields are output by WRITEFIELDS when run from iProcess Workspace (Windows). All the field values are left blank.

Corrected.



Change History | 15

Earlier VersionsFor details of the MRs/CRs implemented in earlier versions of the product, please see the Readme and Release Notes for that particular product release.

MR 19941 If you are importing an xpdl procedure, a subprocedure callstep truncates the start step name if it is more than 7 characters long.

Corrected.



16 | Release Notes

Restrictions

The table in this section lists known restrictions in this release.

Defect # Summary/Workaround

MR 33660 Summary When you map a sub-process call using the "data field mapping" option, or when using the "I/O parameter" option, the mapping dialogue in the parent shows a drop-down list of fields you can map the Outputs into. This drop-down list includes SW_PARENTPROC, SW_PARENTCASE, SW_PARENTHOST - depending on the type of variable (numeric or text). These are critical fields and there is never any reason to modify these.

Workaround Do not attempt to map to these fields. To do so can cause your system to crash.

MR 30723 Summary When performing a workitem filter on CDQP data if there is an AND/OR condition in the statement then the data is not being returned correctly for time, numeric and date CDQPs. Text based CDQPs are working correctly but all others are returning 0 cases when the conditions are valid.

Workaround None.

MR 30217 Summary To load XPDL source into iProcess Workspace (Windows), the XPDL source must be copied into the directory where iProcess Workspace (Windows) is installed.

Workaround None.

MR 30194 Summary The on-line help describes the SW_ADDRESSEE and SW_STEPDESC2 system values as available for use in expressions in iProcess scripts. This is incorrect.

Workaround None.

CR 19964 Summary If you run Setup on a Japanese platform, you get an error if you select English or French (Standard) from the Choose Setup Language dialog. An Internal Dialog Box Error is displayed and Setup crashes.

Workaround You can only select Japanese from the Choose Setup Language dialog if you are installing iProcess Workspace (Windows) on a Japanese platform.


Restrictions | 17

CR 18848 Summary If you create a new iProcess group, run movesysinfo and then try to use the new group in an expression in the access control field of a procedure or library, an error message is generated saying that the syntax is not valid, but without further explanation. The new group is treated as invalid because group information is only cached when the iProcess Client starts up, and cannot be subsequently refreshed.

Workaround If you log out of the iProcess Client and log back in again, the new group will then be available.

CR 18614 Summary When you log in to the iProcess Client (Windows) test queues are not displayed in Work Queue Manager.

Workaround Select your personal work queue and press F5. The Rebuild List button appears. Click Rebuild List and the test queues are displayed.

Note: Although the effect of the problem is visible in Work Queue Manager, CR 18614 is actually an iProcess Engine problem.

CR 14041 Summary If you have an array field called TOWN and you define it as a CDQP in the CDQP Control File using the following command:

F+TOWN,20,Town/City

it causes incorrect data to be displayed in the Work Queue Manager. This is because the WIS process loads the data for CDQPs from the pack_data table by searching for fields called TOWN for each work item in the queue. If it finds a matching field name, it puts the value of the field into the CDQP value.

However, array fields can have multiple values for each field name. They are stored as, for example, TOWN[0], TOWN[1] in the pack_data table. When a work item is kept, the iProcess Workspace (Windows) goes through the form being kept and builds a list of field values that are CDQPs for the current queue and builds a buffer of these values so the WIS can update the CDQPs without going back to the database. However, the iProcess Workspace (Windows) incorrectly passes the WIS data for the currently displayed array field element (e.g. TOWN[0]) as a single instance field (e.g. TOWN="SWINDON"). This means that the previously blank CDQP now has a value. Each time the currently displayed element is changed and the form kept, the CDQP value changes to the value of the current element.

Workaround None.



18 | Release Notes

CR 12961 Summary The following iProcess Expressions are currently not available to the iProcess Script Server Plug-in. Therefore, even though you can successfully enter the expressions in your iProcess Script plug-in definition, they will not be processed by the iProcess Engine. All of the following expressions will return SW_NA (except GOTOSTEP, which has its own error code).

• ATTACHFILENAME

• CALL

• CASECLOSE, CASESTART, CUSTAUDIT

• DBWRITEFIELDS, DDEGETNAME, DDEGETTOPIC, DDEINITIATE, DDEPOKE, DDETERMALL, DDETERMINATE, DDEXECUTE

• FILEREQUEST, FORMCONTROL, FORMMAXIMIZE, FORMMINIMIZE, FORMMOVE, FORMRESTORE, FORMSIZE

• GETHANDLE, GOTOSTEP

• MARKFIELDCHANGED, MEMOFILE, MESSAGEBOX

• READFIELDS

• SCRIPT

• SENDKEYS, SERVEREXEC, SERVERRUN

• TRIGGEREVENT

• UNIXEXEC, UNIXRUN

• VLDFILE, VLDFILEX, VLDQUERY

• WINACTION, WINACTIVATE, WINCLOSE, WINEXIST, WINFIND, WINMAXIMIZE, WINMESSAGE, WINMINIMIZE, WINMOVE, WINRESTORE, WINRUN, WINSIZE, WRITEFIELDS

The following iProcess data fields are not available:

• SW_USER:attribute

• SW_GROUP:attribute

• SW_IP_work item priority fields

Workaround None



Restrictions | 19

CR 12163 Summary Attachments, automatic steps and open client steps are not supported on the TIBCO iProcess Engine. If you import a version 8 or version 9 procedure into the iProcess Modeler that contains any reference to attachments, automatic steps or open client steps, the iProcess Modeler indicates that the procedure is incomplete (until the unsupported items are removed from the procedure).

Workaround None.

CR 12037 Summary You should not use any special characters (!, £, &, *, ?, /, etc.) when naming new groups, roles, lists or tables using the TIBCO iProcess Administrator.

Workaround None.

CR 11525 Summary If you start a case containing an EIS step, then open the EIS step and click the Create Test File button, the following error is displayed:

"There are no cases of this procedure to create test data from. Save the procedure and run some cases"

Workaround None.

CR 11513 Summary If a procedure contains a step with an Addressee that is more than 245 characters long, the iProcess Modeler will crash when you try and save the step.

Workaround None.

CR 9868 Summary The Work Queue Sort Criteria dialog allows you to select more than 10 items when defining the order in which work items are displayed in the Work Queue Manager. However, only 10 items at a time can be displayed in the Work Queue Manager. This means that you should only select up to or including 10 items in the Work Queue Sort Criteria dialog at any one time.

Workaround None.



20 | Release Notes

Known Issues

The following table lists known issues in this release.

Summary

Summary Matching a single non-ASCII character in Work Queue Manager filter criteria

In Work Queue Manager, when you filter cases you can use a question mark character (?) in your filter criteria as a wildcard to match any one character at the position where the wildcard is included. However, if the iProcess Workspace (Windows) handles multi-byte character sets such as Chinese, Japanese and Korean, the single character wildcard (?) will not match any multi-byte character, because Work Queue Manager treats all the string as a byte stream.

When filtering cases, if you need to match a single non-ASCII character in your filter criteria you must do one of the following:

• specify the non-ASCII character explicitly, or

• use two single-character wildcards (??) for matching a 2 byte character, or

• use the asterisk (*) wildcard, which matches zero or more characters at the position where the wildcard is included.

Summary Entering headers without colons in the iProcess Email Client Plug-in

In the iProcess Email Client Plug-in, if you enter a message header in the Mail Message Definition tab without a final colon, it will not be treated as valid. The header text will appear in the message body, not the message header. You must ensure that you enter valid header values.

Summary Cut, copy and paste keyboard shortcuts do not work in private scripts

When you are editing a private script in the iProcess Modeler, the keyboard shortcuts to cut (CTRL-X), copy (CTRL-C) or paste (CTRL-V) do not work. If you want to use these functions, you must select the Cut, Copy and Paste options from the Edit menu instead.


Known Issues | 21

Summary Multiple iProcess Workspace (Windows) Plug-in installations can corrupt SW_CLIENTCLASSPATH

When installing iProcess Client plug-ins, the SW_CLIENTCLASSPATH environment variable can occasionally become corrupted. This can occur when multiple installations have taken place on the same machine (but possibly against multiple iProcess Modeler installations). Each installation of an iProcess Client plug-in adds information to the SW_CLIENTCLASSPATH variable and following multiple installations the Windows limit of 1024 characters for environment variables can be exceeded. This results in plug-ins failing to initialize and being inoperable when using the iProcess Modeler.

A further complication can occur in that on occasions when uninstalling an iProcess Client plug-in the entries added to the SW_CLIENTCLASSPATH environment variable are not removed.

As a workaround to the problem you can manually edit the SW_CLIENTCLASSPATH variable to include references to one instance only of each of the following:

• The log4j library

• The bootstrap library webservices_bootstrap_library.jar from the Web Services plug-in

• The bootstrap library product_bootstrap_library.jar from any one of the products listed below that is installed on your system, other than the Web Services plug-in

The following iProcess Client plug-ins are affected by this problem:

• TIBCO iProcess™ Java Client Plug-in

• TIBCO iProcess™ BusinessWorks Connector Client Plug-in

• TIBCO iProcess™ Decisions Client Plug-in

• TIBCO iProcess™ Conductor Orchestration Client Plug-in

• TIBCO iProcess™ Conductor Order Client Plug-in

• TIBCO iProcess™ Conductor XML Transform Client Plug-in

• TIBCO iProcess™ Web Services Client Plug-in

Summary


22 | Release Notes

Summary Format of Message Event Request (MER) messages is incorrect in Help

In the iProcess Modeler Help, the section "Examples of Configuring Activity Monitoring Information" states that you can specify "the name of the procedure you want to monitor or you may specify that you want to monitor all procedures", when generating a MER message.

This is incorrect. You cannot specify that you want to monitor all procedures in a single MER message. If you want to monitor all procedures you must specify each procedure in a separate MER message.

Summary


Other Information | 23

Other Information

Enabling or Disabling Prediction on a Procedure Only Affects Background Case Prediction

In the Procedure Manager, you can enable or disable the use of case prediction for a procedure (or sub-procedure). You do this by setting or clearing the Prediction flag on the Status tab of the Procedure Properties dialog.

However, you should note that doing this only affects the use of background case prediction. Background case prediction is performed by the case prediction server process (BGPREDICT) on the iProcess Engine. TIBCO iProcess™ Objects, TIBCO iProcess™ Server Objects or SAL applications can still perform live case prediction or case simulation on this procedure, whether or not the Prediction flag is set.

Discrepancy in the Display of Large Decimal Numbers A discrepancy can exist in the display of large decimal numbers as field data in the iProcess Workspace (Windows). This is because numeric field data is converted to floating point format and then back into decimal format. The error affects the least significant digit. For example, the number 444444444444444.44 could be displayed as 444,444,444,444,444.43.

Product Re-brandingFurther product re-branding was carried out in the 10.6.0 release, as follows:

• TIBCO Staffware Process Suite™ was renamed TIBCO iProcess Suite™

• TIBCO iProcess™ Client (Windows) was renamed TIBCO iProcess™ Workspace (Windows)

• TIBCO iProcess™ Client (Browser) was renamed TIBCO iProcess™ Workspace (Browser)

The term "Staffware" was replaced by "iProcess".

You may still see references to Staffware and to the old product names within the software and in some documentation.


24 | Release Notes


Date post:	26-Sep-2020
Category:	Documents
Upload:	others
View:	6 times
Download:	0 times

TIBCO iProcess Workspace (Windows) Release Notes€¦ · (windows) release notes software release...

Documents