TIBCO Business Studio™

- Community Edition
Release Notes
Software Release 3.5.3
April 2012
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 Enterprise Message Service, TIBCO ActiveMatrix and TIBCO Silver are
either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or 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.
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 © 2005-2012 TIBCO Software Inc. ALL RIGHTS RESERVED.
TIBCO Software Inc. Confidential Information
 | iii

Contents

Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Changes of Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Deprecated Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Migration and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
TIBCO Business Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

TIBCO Business Studio Community Edition Release Notes

iv Contents
|

TIBCO Business Studio Community Edition Release Notes

 |1

Release Notes

This is a service release to fix certain issues. See Closed Issues on page 9 for more
information.
Check the TIBCO Product Support web site 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.

Restrictions
The Community Edition of TIBCO Business Studio does not offer/support the
following:
• Import of a WSDL from a TIBCO BusinessWorks live link.
• TIBCO Business Studio Forms, with which you can design, view, and test the
forms you need to collect user input in a business process from within TIBCO
Business Studio.
• TIBCO Business Studio Asset Central, which allows you to create a
Subversion server for source control.
• Deployment to either TIBCO iProcess Engine® or TIBCO ActiveMatrix® BPM.
Contact TIBCO on http://www.tibco.com/company/contactus.jsp for
information on deployment licensing.
These features are documented in the online help and user guides, but are only
available with the commercial editions of TIBCO Business Studio.

Topics

• New Features, page 3

• Changes of Functionality, page 6
• Deprecated Features, page 7
• Migration and Compatibility, page 8

TIBCO Business Studio Community Edition Release Notes

2 Release Notes
|

• Closed Issues, page 9

• Known Issues, page 11

TIBCO Business Studio Community Edition Release Notes

 New Features 3
|

New Features

This section lists new features in TIBCO Business Studio.

Release 3.5.3
No new features in this release.

Release 3.5.2
No new features in this release.

Release 3.5.1
No new features in this release.

Release 3.5.0

General
• Dynamic sub-processes are supported (as in TIBCO iProcess Engine) using a
sub-process identifier of a scalar or array. You can perform an array to
non-array mapping.
• You can add additional instances to a multi-instance loop task whilst that task
is in progress.
• To improve performance, and avoid transformation on project clean, a
preference page is now available for WSDL to Business Object Model, and
Business Object Model to XSD transformation.
• You can compare the local Process Package you are working on with another
version to identify any changes you have made since the last time you saved
that Process Package or any changes made by another user in the Subversion
copy since you last checked it out. You can also compare the local Process
Package you are working on with the local history maintained by Eclipse.
• You can create your own email template which can contain
organization-specific information, with your own logos and corporate style. It
will be used in the email sent to the user after deployment when you have
pushed an email task to the Workspace.
• You can catch email errors by using a Catch Error Event attached to an email
service task.

TIBCO Business Studio Community Edition Release Notes

4 Release Notes
|

• You can now generate a DAA from the command line using an Ant task. See
the TIBCO Business Studio BPM Implementation Guide for more information.

Studio for Analysts

• Studio for Analysts is a new option which you can choose to install. It is
started from its own icon and provides a cut-down version of TIBCO Business
Studio useful for business analysts or for high level modeling, giving the user
access to all the project artifacts in a single file. Controls are in a familiar
ribbon format.
• To enable the Business Analyst to access all the artifacts of a BPM project from
a single location, Studio for Analysts saves the project as a Modelled
Application Archive (MAA) file. For Studio for Designers, MAA files can now
be imported, and projects can be exported to MAA files.

Web Services
See the TIBCO Business Studio BPM Implementation Guide for more information.
• You can now generate a concrete WSDL in TIBCO Business Studio from a Web
Service task.
• WSDLs which have top level elements can be converted to Business Object
Models. WSDLs having Document Literal as the binding style are supported.
• Additional xsd constructs are supported. See the TIBCO Business Studio
Business Object Modeler Guide for more information.
• You can define a common context root that will be used as a prefix to the URI
generated for any system participant that identifies a web service endpoint.

Deployment
• The DAA Deployment Wizard allows you to configure the application
properties and wirings in your application from TIBCO Business Studio.
• User Application Upgrade is supported through the Deployment Wizard in
TIBCO Business Studio. When redeploying applications, you can choose the
behavior of the application upgrade by checking or unchecking the Upgrade
Existing Application checkbox.
• A process that calls a service on a virtualization binding can now be wired and
deployed directly from TIBCO Business Studio. You do not have to create a
Distributed Application Archive (DAA), then use the Administrator interface
in the BPM runtime to perform the wiring and deploy the application.

TIBCO Business Studio Community Edition Release Notes

 New Features 5
|

Presentation Channels
• New channel types are now available for Openspace Mobile and Workspace
Google Web Toolkit.

TIBCO Business Studio Community Edition Release Notes

6 Release Notes
|

Changes of Functionality

This section lists changes in functionality in TIBCO Business Studio.

Release 3.5.3
No changes of functionality in this release.

Release 3.5.2
• Event Handlers are supported in both Pageflow processes and Business
Services. You can use an event handler to input data to the process multiple
times while it is in progress, regardless of whether the flow from any previous
occurrence is still in progress.
• Dynamic sub-processes are now supported for pageflow processes (they were
previously only supported for business processes).
• You can export the Work Data Model for a given project (an artifact containing
XML data definitions that a custom client application may need to enable it to
handle XML data generated from user activities defined in the project
processes for work items, pageflow pages or business service pages).
• Both a Sub-Process and Parallel loop prevent return data mapping into a
Business Object Instance (BOM Class). The output data can only be mapped
into an Array data field.

Release 3.5.0
• The channel types enabled by default are now Workspace Email, Workspace
Google Web Toolkit and Openspace Google Web Toolkit. See the TIBCO
Business Studio BPM Implementation Guide.
• The Shared Resource section on the Properties page for a System Participant
has moved from the Advanced tab to the General tab.

TIBCO Business Studio Community Edition Release Notes

 Deprecated Features 7
|

Deprecated Features

TIBCO Business Studio

• Persistent BOMs are no longer supported.

TIBCO Business Studio Community Edition Release Notes

8 Release Notes
|

Migration and Compatibility

TIBCO Business Studio

Projects are automatically migrated when you use the Import > Existing Studio
Projects into Workspace option.
You can migrate projects created in a previous version of the product with a single
action: right-click > Quickfix. See the TIBCO Business Studio Process Modeling
Guide for more information.

TIBCO Business Studio Community Edition Release Notes

 Closed Issues 9
|

Closed Issues

TIBCO Business Studio

This section lists issues that were closed for TIBCO Business Studio in this release.

Key Summary
XPD-2850 TIBCO Business Studio allows the import of an invalid complex restriction
WSDL and fails much later on DAA generation.

XPD-2659 Failure during import of WSDLs with merging namespaces.

XPD-2532 After starting Correlation projects, a simple request-reply Process As A Service

does not work.

XPD-2530 A merge of the BOM is not supported when importing a WSDL as a BOM.

XPD-2506 When using the Service Import Wizard, XML schemas that are never utilized
can sometimes be omitted from the import process.

XPD-2503 If a project containing a business object model (BOM) is referenced indirectly

from another project (Project1 references Project2 which references the BOM
project), and an external reference field in the indirect project (Project1)
references a class in the BOM, the script descriptor file is not generated.

XPD-2493 An incorrect validation error displays in the script editor when using a BOM
primitive type top-level element as a Text type.

XPD-2481 The BRM component in a user application should depend upon the Directory
Engine component using a range rather than a version, to enable application
upgrade.

XPD-2473 BPM user applications should use "Transacted One Way" policy rather than the
"At Least Once" policy.

XPD-2465 If one Business Object Model (BOM) depends on another, it should express the
dependency using a range in which the minimum and maximum values are
the same and they both are inclusive.

XPD-2454 A user-defined Business Object Model (BOM) generated an invalid schema

when a Class had both a generalization and an association.

TIBCO Business Studio Community Edition Release Notes

10 Release Notes
|

Key Summary
XPD-2441 Disable WSDL generation for a process interface. Adding a process interface to
an xpdl file can create a user application upgrade problem for a TIBCO
Business Studio project which is already deployed and running on the TIBCO
ActiveMatrix BPM server.
Note: If there is an application already deployed and running with process
interface(s), then to avoid any WSDL changes due to XPD-2441 which can lead
to a user application upgrade problem, user(s) can switch on WSDL generation
for a process interface by adding an extended attribute on the XPDL package
level called 'EnableWsdlGenForProcInterface' with its value set to true.

XPD-2434 A mapping error is seen when a Decimal Fixed Point value is mapped to a
value of the same type, and no error is seen when it is mapped to Decimal
Floating Point value.

TIBCO Business Studio Community Edition Release Notes

 Known Issues 11
|

Known Issues

TIBCO Business Studio

The table in this section lists issues related to TIBCO Business Studio in this
release.

Key Summary/Workaround
XPD-3121 Summary: For projects imported from "Studio for Analysts" into "Studio for
Designers", the destination (that is, BPM) specific validators and other features
are not applicable. For example, you will not get the JavaScript option on
sequence flows.
Workaround:
1. After import, open project properties and set the applicable destination (for
example, BPM) on the 'Lifecycle' page.
2. Right-click on the project > Refactor > Project Lifecycle.

XPD-3109 Summary: Renaming a BOM package does not get picked up when there is an
external reference and hence DAA generation of the project that refers it fails.
Dependent XSDs are not being regenerated in this case.
Workaround: In the Preferences option switch on Business Object Modeler >
Business Object Model Generator > Re-generate XSD on Project Clean and
then invoke a clean build on the Workspace. When the problem is fixed the
option can be switch back off.

XPD-3098 Summary: If a Designer project is open in the same workspace in which you
are creating a new parameter, the parameter name is erased and replaced by
the default repeatedly.
Workaround: Close the Designer project.

XPD-3096 Summary: For the Business Analyst persona, a persistent BOM entity ID fails
to change to a BOM attribute when its type is changed to a BOM type.
Workaround: Delete and re-create the entity, rather than change the type.

TIBCO Business Studio Community Edition Release Notes

12 Release Notes
|

Key Summary/Workaround
XPD-3095 Summary: TIBCO Business Studio documentation and license folders are
missing from STUDIO_HOME after successful installation of the Business
Analyst persona.
Workaround: Install and use the documentation from Solutions Designer or
use the on-line documentation.

XPD-3093 Summary: Command line DAA generation fails with 'ERROR: Problems with
artifacts preparation' when BOMs are used to generate WSDLs.
Workaround: Generate the DAA from the TIBCO Business Studio GUI.

XPD-3082 Summary: XSD-to-BOM-to-WSDL conversion can lose elements containing a

top-level simple type. This may happen when using the BOM to WSDL
transformation wizard option where there are one or more substitution groups
pointing to an element in the original XSD.
Workaround: Refactor the XSD to not include one or more substitution groups
pointing to an element.

XPD-3077 Summary: Build automatically is switched off after exporting process package
documentation from the command line, causing the validation framework to
not work.
Workaround: Switch the 'Build automatically' flag ON after restarting TIBCO
Business Studio.

XPD-3076 Summary: A Quick-fix is not available to set grammar = XPATH when

invoking an external service.
Workaround: Manually set the grammar to XPath when required.

XPD-3061 An Enumeration extending another Enumeration is treated as a restriction.

For example, if you have Enumeration "Shape" (RED,BLUE) extending
Enumeration "Color" (RED,BLUE, SILVER,GREEN), then this Shape is treated
as a restriction in BDS rather than an extension. Therefore, when at runtime
you pass a value "SILVER" for the Shape enumeration it fails.
Workaround: None. Despite the runtime failure, this is the correct behavior.

XPD-3060 Summary: Using "Import Existing Projects into Workspace" for BPM projects
may cause a null pointer exception.
Workaround: TIBCO recommends using "Import Existing Studio Projects into
Workspace".

TIBCO Business Studio Community Edition Release Notes

 Known Issues 13
|

Key Summary/Workaround
XPD-3055 Summary: Script validations are missing for script mappings used for the catch
error event, so errors go undetected and fail at runtime.
Workaround: None. Be aware that incomplete scripts are not validated.

XPD-3038 Summary: When trying to set the organizational entity Push Destinations
following the steps in the documentation, you do not see the Channel Type
Workspace Email with the push channel Id EmailGIPush_DefaultChannel
being populated in the dropdown list and the OK button does not become
active. Therefore you cannot create the push destination as documented.
Workaround:
1. Select Window > Preferences > Presentation Channels.
2. Click the edit button and tick the Workspace Email presentation channel
and add it to your Default Channel.
3. Click Finish.
4. Redeploy the process.

XPD-3035 Summary: When a process has one start message event and one message
receive task, there is incorrect generation of the web service provider
participant. This happens when it is a user provided WSDL.
Workaround: Manually select the same participant in both cases.

XPD-3027 Summary: Forms features are not installed when the Analyst Persona is chosen
during installation.
Workaround: Please select the Solution Designer Persona during installation if
you want to use forms.

XPD-3009 Summary: If an embedded subprocess could theoretically start from multiple

places (that is, does not contain start events) then the process may stall on
execution.
Workaround: Ensure that start events are used to remove ambiguity.

XPD-3004 Summary: TIBCO Business Studio creates SOAP/JMS participants with a

default value for the INBOUND destination.
Workaround: Leaving the default destination as it is causes no issues, but you
could also clear the default and progress.

TIBCO Business Studio Community Edition Release Notes

14 Release Notes
|

Key Summary/Workaround
XPD-2991 Summary: TIBCO Business Studio allows the import of an invalid WSDL with
multiple xsd:any types inside a complex type and fails on DAA generation.
Workaround: Ensure that the WSDL is valid before importing or copying it
into TIBCO Business Studio.

XPD-2989 Summary: If a user defined WSDL is deleted and then re-imported, the .js
folders needed for BPM generation may not be created. This will result in DAA
generation failure.
Workaround: Clean the project explictly, then all the .js folders are created and
the DAA can be generated successfully.

XPD-2930 Summary: When TIBCO ActiveMatrix BPM WSDL documents are copied to
the service descriptors folder with all associated XSDs, they do not generate all
the BOMs and hence cause broken reference errors.
Workaround: If this occurs, then use the service import wizard in preference to
directly copying the WSDLs into the service descriptors folder.

XPD-2929 Summary: If a DAA export is attempted when the project contains a process
package that does not contain any processes, then the export fails.
Workaround: Ensure that process packages within the project contains at least
one process definition.

XPD-2976 Summary: If you attempt to select a pageflow from a separate project from a
user task, it is not shown in the list. It is however possible to select a remote
pageflow from a re-usable sub-process task.
Workaround: Manually add a project reference.

XPD-2966 Summary: There is a validation error "BDS: The internal value of literal must
match the name". The quick fix does not get rid of the error unless the BOM is
saved.
Workaround: Save the BOM.

XPD-2958 Summary: The use of adhoc loops on embedded sub procedures is not
supported.
Workaround: None.

TIBCO Business Studio Community Edition Release Notes

 Known Issues 15
|

Key Summary/Workaround
XPD-2955 Summary: If a form references another form or BOM and the referenced form
or BOM is renamed without cascading the rename to the referencing form
(using Preview > and deselecting 'Update forms references to renamed
element') then the referencing form is not revalidated and does not acquire the
expected 'unresolved reference' marker(s).
Workaround: Clean and rebuild the project. This will create the expected
'unresolved reference' marker(s).

XPD-2954 Summary: Very infrequently, when re-opening a closed project, TIBCO

Business Studio hangs and must be forcibly terminated.
Workaround: None.

XPD-2916 Summary: There is an incorrect Warning marker for an rpc/literal SOAP

operation with a multipart request message. The warning marker says 'You
cannot generate a WSDL file for the Document style SOAP operation with the
message 'OperationRequest' because it has multiple parts' even if it is
'rpc/literal'.
The error related to the Warning should be an Error problem marker since this
usage is not supported.
Workaround: None.

XPD-2903 Summary: Sometimes when you click on File > Switch Workspace >
submenus are displayed, but then you cannot select anything since no focus is
available on submenus.
Workaround: Click back on File > Switch Workspace > Submenus and then
focus is available and you can select the intended option.

XPD-2893 Summary: After adding a new class to the BOM it is intermittently not possible
to access its attributes in the script task using the content assist.
Workaround: Complete the script without using content assist.

XPD-2869 Summary: For System participants used for the web service call, the
Governance App. name disappears from user interface intermittently.
Workaround: This is an intermittent problem. Repeat the action and the
Goveranance App. name should be available.

TIBCO Business Studio Community Edition Release Notes

16 Release Notes
|

Key Summary/Workaround
XPD-2761 Summary: Projects imported using "Import Existing Studio Projects into
Workspace" will now be automatically migrated to the latest version of TIBCO
Business Studio. If import is performed from the filesytem (not as a zip) and
"Copy projects into workspace" is not selected, the original project will be
migrated and will not work with the previous version any more.
Workaround: Back up your projects before import to a new version of TIBCO
Business Studio or always check "Copy projects into workspace" to avoid
migration of the original projects.

XPD-2704 Summary: The TIBCO Business Studio Forms User Guide currently refers to the
Welcome page and directs the user to the Samples page accessed from there.
The Samples are no longer available from the Welcome page.
Workaround: To find Forms samples, access the samples here:
http://developer.tibco.com/business_studio/samples.jsp

XPD-2596 Summary: Some WSDL issues may be reported during DAA build export
when performed from the command line interface.
Workaround: Fix WSDL issues and re-export the DAA from the command line
interface.

XPD-2546 Summary: If periods exist in an XML schema namespace then the namespace
string must be unique up to the final period. This is because the final string
segment directly following the period is ignored in some BPM processing
contexts. For example:
"http://www.tibco.com/schemas/Schemas/Schema.xsd"
"http://www.tibco.com/schemas/Schemas/Schema.xsd2"

do not resolve to unique namepaces.

If this situation is encountered then a validation error will be displayed and the
WSDL/XSD will not be imported.
Workaround: The namespaces must be edited to make them unique. For
example:
"http://www.tibco.com/schemas/Schemas/Schema.xsd"
"http://www.tibco.com/schemas/Schemas/Schema2.xsd2"

XPD-2479 Summary: During import of a database table the Eclipse DTP framework
cannot always resolve the column type of the original data. When the import
process recognizes an unresolved type, an attribute of type Text is always
created as default and a warning is not currently generated.
Workaround: None.

TIBCO Business Studio Community Edition Release Notes

 Known Issues 17
|

Key Summary/Workaround
XPD-2431 Summary: Working copy dependencies may not be synchronized after project
migration resulting in some forms not being able to resolve the location of
BOM files containing referenced data types. This results in a validation error
and Null Pointer Exception during project build.
Workaround: None.

XPD-2429 Summary: When using TIBCO Business Studio on Linux 32/64 bit, making
any changes in the Process Editor and saving any changes causes "Concurrent
Modification Exception".
This is caused by a known issue in the Eclipse Platform
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=245596).
Workaround: None - this issue does not cause any known adverse effects,
other than adding errors to the error log.

XPD-2307 Summary: At times the TIBCO Business Studio workspace can get locked
during building of the workspace. There is an issue with JDT's Java Model
Manager which ends up in a deadlock when setting a class path during the
build. See the Eclipse bug report for more details:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=249930
Workaround: Restart TIBCO Business Studio.

TIBCO Business Studio Community Edition Release Notes

18 Release Notes
|

Key Summary/Workaround
XPD-2010 Summary: Once you have deployed a user application to the BPM runtime, the
application can only be subsequently upgraded if its service interface (defined
by the WSDLs used to expose its services) has not changed. Making any of the
following changes will result in changes to the generated WSDL, meaning that
the application cannot be upgraded:
• Changing the number, name, or type of parameters assigned to a task or
event used to expose a web service operation.
• Changing a business object model used by a parameter assigned to such a
task or event.
• Adding, removing, or changing the name of a task or event that can be used
to expose a web service operation.
• Changing the name of the process. (This will also apply to a process that
uses an imported WSDL to expose a web service operation.)
• Changing the Binding Style/Use of the generated WSDL within the details
of the endpoint system participant associated with message API activity.
Workaround: If you have changed any of the above points, then changing the
name of the endpoint system participant associated with message API activity
is a workaround which will allow application upgrade to work.

XPD-1980 Summary: When database errors occur it is not possible to set an external
reference Organization Model to a participant as project import breaks the
reference.
Workaround: Re-start TIBCO Business Studio.

XPD-1947 Summary: If a special folder is deleted manually then it may not be possible to
generate a DAA from the project.
Workaround: Re-create the special folder manually.

TIBCO Business Studio Community Edition Release Notes

 Known Issues 19
|

Key Summary/Workaround
XPD-1852 Summary: There is a problem in Windows with extension association, that if a
studio-doc.exe or StudioForAnalyst.exe file is assigned to an .maa file
extension, that exact .exe file will remain the default .exe file. If you use the
Open with... option, and choose a different .exe from a different
location/installation, the very first one assigned is the one used. This could
cause problems if multiple versions of TIBCO Business Studio are installed.
Workaround: Manually change the path to the studio-doc.exe or
StudioForAnalyst.exe file in the registry by changing the properties:
For StudioForAnalyst.exe:
Computer\HKEY_CLASSES_ROOT\Business Object
Model\shell\open\command

For studio-doc.exe:
Computer\HKEY_CLASSES_ROOT\Applications\studio-doc.exe\shell\ope
n\command

Also, change the default value to the correct studio-doc.exe or

StudioForAnalyst.exe file location.
This problem does not affect the shortcut provided by TIBCO Business Studio
to open Studio For Analysts, it is just found when using the Open with...
option in the context menu of a .maa file.

XPD-1834 Summary: WSDL operation response object might not be converted into
equivalent BOM class during WSDL to BOM transformation. The generated
class might not have all the properties it is expected to have.
Workaround: None.

XPD-1829 Summary: User Application upgrade does not work when the WSDL
definition for a process acting as service provider is changed (for example, by
adding a process formal parameter).
Workaround:
1. Undeploy the old application and redeploy the new version of the
application.
2. If the process acting as service provider does not have any in flow message
API activities, then before redeploying, change the system participant
name and attempt a User Application upgrade.

TIBCO Business Studio Community Edition Release Notes

20 Release Notes
|

Key Summary/Workaround
XPD-1582 Summary: Studio for Analysts fails to launch when TIBCO Business Studio -
BPM Edition is installed on TIBCO ActiveMatrix.
Workaround: Do not install Studio for Analysts along with TIBCO Business
Studio - BPM Edition when installing it in TIBCO ActiveMatrix.

XPD-1549 Summary: On some installations, clicking on some controls in a property sheet

cause an SWT error dialog to appear.
Workaround:
1. If, when clicking on a control in a property sheet, an SWT error message is
displayed (for example Unhandled event loop exception
org.eclipse.swt.SWTERROR) then:
a. Click OK to this dialog.
b. If another Internal-Error dialog is displayed (An SWT error has
occurred. You are recommended to exit the workbench...) asking
whether to exit the workbench, click No.
2. Reselect the process background, and then the object you had originally
selected.
a. Next time you wish to use the control in the property sheet that caused
the problem, pre-activate the Properties view by clicking on the
Properties view tab-header first.
b. You should now be able to use the property sheet controls as normal.

XPD-994 Summary: When you use a new workspace, the banner in the Properties view
does not display a label and decoration. This is due to an Eclipse bug that was
fixed in Eclipse version 3.5 and later. See the Eclipse web site for a detailed
description.
Workaround: None

XPD-707 Summary: Cannot import into TIBCO Business Studio WSDLs with more than
one binding per service.
Workaround: Avoid having more than one binding for any given published
service.

TIBCO Business Studio Community Edition Release Notes

 Known Issues 21
|

Key Summary/Workaround
XPD-589 Summary: Eclipse 3.4.2 is not compatible with Xulrunner 1.9 as reported by
https://bugs.eclipse.org/bugs/show_bug.cgi?id=262929. Xulrunner is
typically installed as part of the Firefox browser and v1.9 is used by Firefox
v3.5 and above. The compatible versions of Xulrunner are shown here:
http://www.eclipse.org/swt/faq.php#browserlinux.
Workaround: Workaround 1: The preferred workaround is to obtain a
compatible version of xulrunner. You can configure TIBCO Business Studio to
use it by adding this to the end of the TIBCOBusinessStudio.ini file:
-Dorg.eclipse.swt.browser.XULRunnerPath=path_to_xulrunner_1_8

Workaround 2: If you are not able to use workaround 1, you can also create a
shell script to start TIBCO Business Studio that will first set GRE_HOME to a
non existent path (e.g. /dev/nul) and then start TIBCO Business Studio. This
will use a more basic browser than Firefox and will result in degraded behavior
wherever the browser control is used including in welcome pages, help content
and TIBCO Forms preview. If this is not successful, use workaround 3.
Workaround 3: Delete xulrunner. This will mean you cannot use Firefox and
will result in degraded behavior wherever the browser control is used
including in welcome pages, help content and TIBCO Forms preview.

XPD-475 Summary: The Business Object Modeler does not allow you to enter default
values as very large numbers or in scientific notation for Fixed Length
(BigInteger) and Fixed Point (BigDecimal) types. For example, the maximum
value you can enter at design-time for a default value on a 32 bit Signed Integer
is 2147483647. If you enter 2147483648 or greater then the designer reverts to
the last stored default value.
Workaround: None.

XPD-92 Summary: Organization model queries are executed against the highest major
version only.
Workaround: None.

XPD-1 Summary: When there are multiple overview URLs present, which is allowed
based on the uddi v3 schema, some of them may not be WSDL-type URLs.
Workaround: Only a URL using the "wsdlInterface" value is a WSDL URL that
can be imported. If a urlType is text, TIBCO Business Studio should not try to
import WSDL documentation from such a URL.

TIBCO Business Studio Community Edition Release Notes

22 Release Notes
|

Key Summary/Workaround
WRM-2991 Summary: In TIBCO Business Studio, when you try to export a project that
uses business data to a DAA:
• the export fails, even though the projects have no error markers, and
• on the Problems tab, "Package name does not exist in the plugin" errors are
shown against a resource MANIFEST.MF in one or more of the associated
.BDS projects.
Workaround: To resolve this problem:
1. Manually clean the project. (Use Project > Clean.)
2. Export the project to a DAA again.

WRM-2787 Summary: In TIBCO Business Studio, the following error is displayed when a
WSDL is imported:
WSDL 1.1 : BDS cannot process this WSDL as it has problems:
XML Schema contains an unsupported Complex Type restriction
of another Complex Type.

The error occurs because the base version of the Eclipse Modeling Framework
(on which the BDS Plug-ins are based) does not support:
• multiple xsd:any elements nested within the same complex object. (This
can be the case if there are nested sequences.)
• the extension of an object with an xsd:any defined where there is also an
xsd:any in the complex object that extends it.
Workaround: Do not use these constructs in a schema that is to be imported
into TIBCO Business Studio.

WRM-2311 Summary: In TIBCO Business Studio, you cannot assign Text to Signed
Integer on a mapper screen. (This should be allowed but with a warning.)
Workaround: Perform the mapping using a script. The script should use:
Number(textField)

to convert the text value to a numeric value suitable for mapping to a signed
integer.

SDS-4993 Summary: You cannot choose a shared resource instance when deploying from
TIBCO Business Studio with a Web Component node running on a second
host.
Workaround: Manually type in the name of the shared resource instance you
want to use.

TIBCO Business Studio Community Edition Release Notes

 Known Issues 23
|

Key Summary/Workaround
SDS-4982 Summary: Multiple shared resource instances will appear in the late binding
screen when TIBCO Business Studio is connected to a BPM runtime configured
in a HA/FT environment.
Workaround: Enter the value you require in the combo box for selecting the
resource instance. (You can look for the resource instance name in the Admin
Explorer view and type in that value.)

INST-383 Summary: If you choose to install Asset Central then the configuration dialog
for Asset Central does not come up during installation.
Workaround: To configure Asset Central, go to
$STUDIO_HOME/studio/3.5/assetcentral and run configure.bat

TIBCO Business Studio Community Edition Release Notes

24 Release Notes
|

TIBCO Business Studio Community Edition Release Notes