TIBCO BusinessEvents Process Orchestration Release Notes€¦ · TIBCO BusinessEvents Process...

Two-Second Adv

TIBCO BusinessEvents®

Process Orchestration

Release NotesSoftware Release 5.3.0May 2016

antage®

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, TIBCO ActiveMatrix BusinessWorks, TIBCO Administrator, TIBCO ActiveSpaces, TIBCO BusinessEvents, TIBCO Designer, TIBCO Enterprise Administrator, TIBCO Enterprise Message Service, TIBCO Hawk, TIBCO Runtime Agent, TIBCO Rendezvous, are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform Enterprise Edition (J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle Corporation 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 © 2004-2016 TIBCO Software Inc. ALL RIGHTS RESERVED.

TIBCO Software Inc. Confidential Information

| iii

Contents

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

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

Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixHow to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixHow to Access TIBCO Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixHow to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

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

New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 1.2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 1.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 1.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 1.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 1.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 1.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Release 1.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Release 1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Release 5.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Release 1.2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Release 1.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Release 1.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Release 1.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Release 1.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Release 1.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Release 1.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Release 1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Deprecated and Removed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Deprecated Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Removed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Migration and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Release 5.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Release 1.2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Release 1.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Release 1.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Release 1.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

TIBCO BusinessEvents Process Orchestration Release Notes

iv | Contents

Release 1.1.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Release 1.1.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Release 1.0.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Release 1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15


| v

Preface

TIBCO BusinessEvents® Process Orchestration software is an add-on to TIBCO BusinessEvents. It provides CEP functionality within the context of a BPM process, enabling you to segregate different CEP rule sets within the flow of a BPM process.

Topics

• Typographical Conventions, page vi

• Connecting with TIBCO Resources, page ix


vi | Typographical Conventions

Typographical Conventions

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

Convention Use

ENV_NAME

TIBCO_HOME

BE_HOME

TIBCO products are installed into an installation environment. A product installed into an installation environment does not access components in other installation environments. Incompatible products and multiple instances of the same product must be installed into different installation environments.

An installation environment consists of the following properties:

• Name Identifies the installation environment. This name is referenced in documentation as ENV_NAME. On Microsoft Windows, the name is appended to the name of Windows services created by the installer and is a component of the path to the product shortcut in the Windows Start > All Programs menu.

• Path The folder into which the product is installed. This folder is referenced in documentation as TIBCO_HOME.

TIBCO BusinessEvents installs into a directory within a TIBCO_HOME. This directory is referenced in documentation as BE_HOME. The default value of BE_HOME depends on the operating system. For example on Windows systems, the default value is C:\tibco\be\5.3.

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]


Preface | vii

italic font Italic font is used in the following ways:

• To indicate a document title. For example: See TIBCO ActiveMatrixBusinessWorks 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.

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 param1 | param2 | param3


viii | Typographical Conventions

{ } 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}

Table 2 Syntax Typographical Conventions

Convention Use


Preface | ix

Connecting with TIBCO Resources

This section provides links to helpful 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 TIBCO DocumentationYou can access TIBCO documentation here:

http://docs.tibco.com

How to Contact TIBCO SupportFor comments or problems with this manual or the software it addresses, 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.tibcommunity.com

http://docs.tibco.com

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


x | Connecting with TIBCO Resources


| 1

Release Notes

Check the TIBCO Product Support web site at https://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

• Changes in Functionality, page 4

• Deprecated and Removed Features, page 8

• Migration and Compatibility, page 10

• Closed Issues, page 12

• Known Issues, page 15



2 | Release Notes

New Features

This section lists the features added since the last major (x.0.0) release of this product.

Release 5.3.0There are no new features in this release.



Release 1.2.0• Added the SharedAll persistence support to the TIBCO BusinessEvents

Process Orchestration.

• Added functionality to call and execute user defined Java Code as Java task and provide integrated development and debugging environment.


Release 1.1.1• A new catalog function is added to set the default exception handler function

URI for the given template.

void Process.Template.setExceptionHandler(Object template, String handlerFunctionURI)

The version number of the TIBCO BusinessEvents Process Orchestration add-on is adjusted to match TIBCO BusinessEvents and other add-ons.


New Features | 3

Release 1.1.0Support for looping functionality in process is now added.

Release 1.0.1Following features are introduced in this release:

• Support for secure HTTP (SSL) is added. See the "Configuring WebService Task For HTTPS-SSL" section in the TIBCO BusinessEvents Process Orchestration Developer’s Guide for details.

• Support for secure JMS (SSL) is added. See the "Configuring WebService Task For JMS-SSL" section in the TIBCO BusinessEvents Process Orchestration Developer’s Guide for details.

• For Business Rule and Inference tasks, double clicking the resource allows you to open the editor.

Release 1.0This is a new add-on product. See TIBCO BusinessEvents Process Orchestration Developer’s Guide for details.


4 | Release Notes

Changes in Functionality

This section lists changes in functionality since the last major (x.0.0) release of this product.

Release 5.3.0There are no changes in functionality in this release.



Release 1.2.0

Documentation

The documentation of TIBCO BusinessEvents Process Orchestration is no longer bundled with the installer. The documentation is available on https://docs.tibco.com.

To access the product documentation directly from the docsite, double-click the TIB_businessevents-process_1.2.0_docinfo.html file.

Release 1.1.2

Catalog Functions

• The Process.Activity.moveTo() function now also has an optional parameter timeOutInMillis, which identifies the timeout in milliseconds to get the job context lock.

The Process.Activity.moveTo() signature is now changed to:

int moveTo(Object job, String activityName, [int timeOutInMillis])


Changes in Functionality | 5

• The catalog function Process.Template.setExceptionHandler() for the BPMN process templates has been changed so that you can use the Process URIs or the Rulefunction URI.

The Process.Template.setExceptionHandler() signature is now changed to:

void setExceptionHandler(Object template,String processOrfunctionURI,<optional>boolean isAsynchronous)

Release 1.1.1• Behavior has changed for the following the catalog functions. If the projects

are already using these functions, then update the projects in BusinessEvents Studio.

— Process.Template.newJobContext() signature changed to String newJobContext(Object template, String extId)

— Process.Template.getTemplate() signature changed to Object getTemplate(String name, int revision)

— Process.Activity.moveTo() signature changed to int moveTo(Object job, String activityName)


Release 1.0.1The following are changes in functionality in this release.

Signature Changes for Fork and Join Rule Functions

Signatures have changed for the Fork and Join rule functions, manually update these functions within the projects containing parallel gateways.

Fork Function

Signatures

The new signature is defined as below:Object forkFn(Object jobContext,String seqFlowId)

This is called for every sequence flow originating from the fork.


6 | Release Notes

Parameters

See Fork Function Parameters on page 6.

Returns

A Object: New or original jobContext passed as the argument.

Join Function

Signatures

The new signature is defined as below:Object joinFn(Object seqFlowJobContextMap,String mergeKey)

Parameters

See Join Function Parameters on page 6.

Returns

A Object: The function can return a new jobContext or an incoming job context from seqFlowJobContextMap after a data merge is done.

Table 3 Fork Function Parameters

Parameter Type Description

jobContext Object The cloned job context containing the process variables from the parent job.

seqFlowId String The id of the sequence flow.

Table 4 Join Function Parameters

Parameter Type Description

seqFlowJobContextMap Object This is a map of sequence flow id's to the corresponding job context i.e Sequence Flow id(String) -> (Object: Process concept) Job Context , for all the sequence flows merging at this gateway.

merge key Object This is a String key derived from an expression which extracts the same key value from each merging job context process variables.


Changes in Functionality | 7

Release 1.0This is a new add-on product, so this section is not relevant in this release.


8 | Release Notes

Deprecated and Removed Features

This section describes the 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.

Deprecated Features

Release 5.3.0

No features are deprecated in this release.

Release 1.2.2


Release 1.2.1


Release 1.2.0


Release 1.1.2


Release 1.1.1


Release 1.1.0


Release 1.0.1



Deprecated and Removed Features | 9

Release 1.0

This is a new add-on product, so this section is not relevant in this release.

Removed Features

Release 5.3.0

No features are removed in this release.

Release 1.2.2


Release 1.2.1


Release 1.2.0


Release 1.1.2


Release 1.1.1


Release 1.1.0


Release 1.0.1


Release 1.0

This is a new add-on product, so this section is not relevant in this release.


10 | Release Notes

Migration and Compatibility

This section explains how to migrate from a previous release to this release.

Release 5.3.0See TIBCO BusinessEvents Release Notes for full details. No special action is required for this add-on.

Release 1.2.2See TIBCO BusinessEvents Release Notes for complete details. No special action is required for this add-on.







Migration and Compatibility | 11

Release 1.0.1• Signatures have changed for the Fork and Join rule functions, so any existing

projects using parallel gateways with these functions should be manually updated for the new signatures. See Signature Changes for Fork and Join Rule Functions, page 5 for details.

• Sometimes, the input mappers for activities in the project being migrated might show errors. These errors should be taken care automatically by using Project -> Clean menu option and rebuilding the ear files. Alternatively, you should open the Input Map and Output Map tabs for the activities with error markers and click on the Mapper Check and Repair option to fix them manually.

Release 1.0This is a new add-on product, so this section is not relevant in this release.


12 | Release Notes

Closed Issues

The table in this section lists issues that were closed in the named releases.

Closed in Release Key Summary

1.2.0 BE-20003 When multiple events were sent to the loop over receive tasks, the task was executed parallely by different threads instead of sequentially.

1.2.0 BE-20480 The meaning of "AssertEvent" is provided in chapter 4 - Process Execution : Checkpointing and Recovery of TIBCO BusinessEvents Process Orchestration Developer's guide.

1.2.0 BE-17791 Concepts created with Cache Only mode were not returned correctly when the persistence option was None.

1.2.0 BE-17753 The Process Orchestration mapper did not supported the use of option ’for each’ for non-array element types.

1.2.0 BE-17361 Process Message Start activity, upon receiving events with payload, threw the following exception: Error while generating output transformation code com.tibco.cep.mapper.codegen.UnsupportedXsltMappingException

1.2.0 BE-17135 In BPMN, use of rule-based timer event, which triggers process using time start, was not supported at run time.

1.2.0 BE-3220 BusinessEvents did not support the ability to model using Business Studio.

1.0.1 BE-17436 In Studio, the modified icons for tasks in the process graph were not available when custom palette was loaded.

1.0.1 BE-17404 An exception was thrown when generating code if the output mapping included array mappings.

1.0.1 BE-17398 A NullPointerException was thrown when executing a mapping for the referenced concept if a process variable was defined as a referenced concept.


Closed Issues | 13

1.0.1 BE-17373 For a Web Service task, changing the value of the JNDI Context Factory in a JMS WSDL caused an unhandled event loop exception to be thrown.

1.0.1 BE-17370 An error was thrown during startup if rule functions that return array types (int[], Concept[]. and so on) were used in the rule function tasks.

1.0.1 BE-17366 In Studio mapper, the value of a particular index in the array was null if the number of occurrences in WSDL file is unbounded (maxOccurs = unbounded).

1.0.1 BE-17355 Removing a virtual rule function from a business rule task did not remove the associated decision table.

1.0.1 BE-17354 A concept could incorrectly be contained in more than one process as a contained concept.

1.0.1 BE-17353 The process engine incorrectly waited for a response from a one-way web service request.

1.0.1 BE-17352 When a Fork or Join rule function was moved, the process properties were not updated with the new path.

1.0.1 BE-17350 Exclusive gateways did not handle null conditions for the test variable. If the test variable was empty or null, a NullPointerException was thrown at runtime and execution did not continue along the default path.

1.0.1 BE-17349 Using drag and drop to move processes from one folder to another within the same project caused a NullPointerException to be logged. This has been fixed to display a warning message instead.

1.0.1 BE-17347 In Studio Properties tab for Receive Message Task, the Key Expression field displayed the xPath expression instead of the key value.

1.0.1 BE-17344 A NullPointerException was thrown during shutdown if any failures had occurred.

1.0.1 BE-17343 When a rule function was used to return an Object into a script task, the output data mapper of the script task was rendered empty.

1.0.1 BE-17342 Using the ’$Job’ variable in the Input Mapper of the Call Activity resulted in a compilation error.



14 | Release Notes

1.0.1 BE-17315 Exclusive gateway did not provide the default transition setting for runtime.

1.0.1 BE-17296 When executing a Call Activity task with Parallel Gateway, occasionally the current task was null. This caused a NullPointerException to be thrown while logging at the DEBUG level.

1.0.1 BE-17288 An exception stating "Exclusive Gateway does not have a Default" was thrown when using an Exclusive Gateway with more than two outbound paths.

1.0.1 BE-17260 Studio Help was no longer available when a WSDL file was selected for a Web Service Task and was restored when the WSDL file was removed from the resource.

1.0.1 BE-17206 After associating a private process to the Call Activity Task in Studio, clicking the Resource hyperlink did not open the editor for the associated process. Also, when no process was assigned to the Call Activity Task, the new process creation editor did not open.

1.0.1 BE-17186 Upon starting a process, scorecards were not initialized and an exception was thrown.



Known Issues | 15

Known Issues

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

Key Summary/Workaround

BE-18543 Summary In TIBCO BusinessEvents Process Orchestration, if the project library dependency is not resolved, the WSDL cannot be opened as links.

Workaround Use local (that is, non-project library) processes.

BE-17936 Summary At runtime, processes containing the receive tasks throw null java.lang.NullPointerException when the persistence option was set as Shared Nothing within the cluster deployment descriptor.

Workaround None.

BE-17701 Summary The rich text editor is not supported on Mac OS. Hence it is not possible to export and view documentation for elements in a process flow, including transitions, from the Documentation tab on Mac OS.

Workaround None.

BE-17571 Summary The option ’Copy-contents of’ is not supported by the Process Orchestration mapper.

Workaround After you drag and drop a contained concept from the left to the right panel, select the second option "For each..." on the mapper wizard to copy the mappings.

BE-17229 Summary XPath 2.0 functions and operations are not supported in the TIBCO BusinessEvents Process Orchestration Mapper at runtime.

Workaround None.

BE-16793 Summary A Cluster can either have an Inference Agent or a process agent, but not both.

Workaround None.

BE-16336 Summary In TIBCO BusinessEvents Process Orchestration Studio, even after you change the custom palette to any other palette and load it, the newly created process does not display the color of the new palette.

Workaround Refresh the project.


16 | Release Notes


Date post:	24-Jun-2020
Category:	Documents
Upload:	others
View:	10 times
Download:	0 times

TIBCO BusinessEvents Process Orchestration Release Notes€¦ · TIBCO BusinessEvents Process...

Documents