Tib Bs Modeler User

TIBCO Business Studio™
Modeling
User’s Guide
Software Release 2.1
September 2007
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 TIBCO BUSINESS STUDIO INSTALLATION GUIDE) 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.
TIB, TIBCO, TIBCO Software, TIBCO Adapter, Predictive Business, Information Bus, The Power of Now, TIBCO
iProcess, and TIBCO Business Studio are either registered trademarks or trademarks of TIBCO Software Inc. in
the United States and/or other countries.
EJB, Java EE, J2EE, JMS 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. PLEASE SEE THE README.TXT 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-2007 TIBCO Software Inc. ALL RIGHTS RESERVED.
TIBCO Software Inc. Confidential Information
Contents iii
|
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
TIBCO Business Studio Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Other TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Third-Party Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
How to Contact TIBCO Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Chapter 1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Who Should Use TIBCO Business Studio? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Modeling Approach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Define the "As is" Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Define the "To be" Process (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Hand Over for Implementation (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
About Projects, Packages and Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Asset Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Getting Help in TIBCO Business Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Using the Sample Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Creating a Project, Package and Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Working with Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Adding Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Connecting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Selecting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Tutorial 1: Creating a Simple Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Tutorial 2: Extending a Simple Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Tutorial 3: Refactoring Activities into a Sub-Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Tutorial 4: Working with Process Fragments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Tutorial 5: Exporting to the TIBCO iProcess Modeler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Deploying a Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Chapter 2 Concepts and Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Artifacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Data Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Text Annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
TIBCO Business Studio - Modeling User’s Guide

iv Contents
|
Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Connecting Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Associations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Message Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Sequence Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Flow Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Process Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Process Fragments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Project Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Assets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Special Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Standards Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Business Process Modeling Notation (BPMN). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
XML Process Definition Language (XPDL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Swimlanes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Lanes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Chapter 3 Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Migrating Processes Created in Previous Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Migrating from Version 1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Migrating from Version 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Creating a Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Copying a Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Creating a Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Deleting a Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Creating Data Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Creating Participants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Associating Participants with Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Deleting Data Fields, Parameters, Participants, and Type Declarations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Creating Extended Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Configuring Timer Event Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Working With Special Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Enabling and Disabling Special Folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Contents v
|
Workflow Patterns in Business Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Forking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Combining Sequence Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Decisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Reusing Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Independent Sub-Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Embedded Sub-Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Refactoring Sub-Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Using Process Fragments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
How Projects, Packages and Processes Support Reuse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Using Throw and Catch Error Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Importing a TIBCO iProcess Modeler Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Source Controlling Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Using Subversion with TIBCO Business Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Creating a Project from an Existing Project in Source Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Browsing SVN Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Deleting Projects from SVN Repositories with Asset Central . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Emailing Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Integrating with the TIBCO iProcess Suite. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Integrating with Aris Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Creating Custom Symbols in Aris (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Using Custom Symbols in TIBCO Business Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Exporting from Aris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Importing Aris into TIBCO Business Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Creating Process Package Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Viewing Process Package Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Setting the Validation Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Chapter 4 Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
The TIBCO Business Studio Modeling Perspective. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Project Explorer View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Problems View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Outline View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Diagram Fragments View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Properties View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Cheat Sheets View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Process Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Process Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
General Rules for Export to the TIBCO iProcess Modeler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Correcting Validation Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

vi Contents
|
Object Mappings - TIBCO iProcess Modeler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Object Mappings - Aris Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Chapter 5 Tips and Tricks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Process Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Problems View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

| vii
Preface
This guide is intended for business analysts and focusses on using the modeling
capabilities of TIBCO Business Studio. No previous software experience is
necessary, but a familiarity with Business Process Modeling Notation (BPMN) is
useful (see http://www.bpmn.org).
Topics
• Related Documentation, page viii

• Typographical Conventions, page ix
• How to Contact TIBCO Support, page x

viii Preface
|
Related Documentation
This section lists documentation resources you may find useful.
TIBCO Business Studio Documentation

The TIBCO Business Studio documentation set consists of user’s guides for its
main features such as modeling and simulation. This documentation has the
following main sections:
• Getting Started takes you through the basics of TIBCO Business Studio,
including several tutorials.
• Concepts and Definitions explores the concepts and terminology related to
TIBCO Business Studio.
• Tasks describes common tasks that you perform using TIBCO Business Studio.
• Reference provides detail about the major components of TIBCO Business
Studio such as the properties sheets and user interface (UI).
The following documentation is also provided:
• TIBCO Business Studio Installation Guide: Read this manual for instructions on
site preparation and installation.
• TIBCO Business Studio Release Notes: Read the release notes for a list of new
and changed features. This document also contains lists of known issues and
closed issues for this release.
Other TIBCO Product Documentation

You may find it useful to read the documentation for the TIBCO iProcess Suite™,
which may be used or integrated with TIBCO Business Studio. Information about
this set of products can be found in the TIBCO iProcess Suite: Documentation
Library.
Third-Party Documentation
The Eclipse help also contains useful information on the Workbench and the
Eclipse user interface.

Typographical Conventions ix
|
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 TIBCO foo process.
bold code Bold code font is used in the following ways:

font
• In procedures, to indicate what a user types. For example: Type the username
admin.
• In large code samples, to indicate the parts of the sample that are of
particular interest.
• In command syntax, to indicate the default value.
italic font Italic font is used in the following ways:

• To indicate a document title. For example: See TIBCO BusinessWorks Concepts
for more details.
• 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 Key name separated by a plus sign indicate keys pressed simultaneously. For
combinations example: Ctrl+C.
Key names separated by a comma and space indicate keys pressed one after the
other. For example: Esc, Ctrl+Q.

x Preface
|
How to Contact TIBCO Support
If you have purchased another TIBCO product that includes support for TIBCO
Business Studio and have 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:
http://support.tibco.com
Entry to this site requires a username and password. If you do not have a
username, you can request one.
The community edition of TIBCO Business Studio is unsupported. For self-service
support, education, and access to the TIBCO Developer Network, visit
http://www.tibco.com/devnet/index.html.

|1
Chapter 1 Getting Started
If you are new to using this product, there are several resources available to you
from the Welcome page that is displayed when you first start TIBCO Business
Studio. The Welcome page is also available from the Help menu. These resources
include:
• A cheat sheet that guides you through the process of creating a Project and
Package.
• Tutorials in the help that explain creating a Process in detail. These tutorials
will help you become familiar with the Process Editor.
• Sample Processes (including solutions to the Tutorials) that you can install
into your workspace.
Topics
• Who Should Use TIBCO Business Studio?, page 2

• Modeling Approach, page 3
• Getting Help in TIBCO Business Studio, page 6
• Using the Sample Processes, page 7
• Creating a Project, Package and Process, page 8
• Working with Processes, page 10
• Tutorial 1: Creating a Simple Process, page 12
• Tutorial 2: Extending a Simple Process, page 16
• Tutorial 3: Refactoring Activities into a Sub-Process, page 23
• Tutorial 4: Working with Process Fragments, page 27
• Tutorial 5: Exporting to the TIBCO iProcess Modeler, page 30
• Deploying a Process, page 33

2
| Chapter 1 Getting Started
Who Should Use TIBCO Business Studio?
TIBCO Business Studio is for business analysts and those responsible for the
implementation of business processes. The following diagram shows how TIBCO
Business Studio is intended to be used:
Referring to the previous diagram, if you are using native service calls (database
or email) or general service calls (such as web services), you can augment the
process with execution details in TIBCO Business Studio and deploy it directly to
the TIBCO iProcess Engine. However, if you need to make other types of service
calls (for example, EAI Java), you must augment and implement the Process using
another product such as TIBCO iProcess Modeler.

Modeling Approach 3
|
Modeling Approach
Modeling a Process can be achieved in several different ways, however the

following general approach reflects best practices:
Define the "As is" Process

1. Interview business end users about their current practices.
2. Capture the process flow (either on paper first or directly in modeling tool).
3. Capture the process relevant data (either on paper first or directly in modeling
tool).
4. Attach the process-relevant data at key points (for example, at decision points
or certain activities).
5. Simulate and analyze to ensure that the "As is" process is an accurate
representation of the current process.
Define the "To be" Process (Optional)

This is an iterative exercise in which you:
1. Propose optimizations (process changes and new automation of existing
processes).
2. Simulate to validate changes or to quantify estimated savings.
Hand Over for Implementation (Optional)

If the Process is to be executed in a BPM environment, you should:
1. Set the appropriate Destination Environment.
2. Check the Problems view for any warnings or errors in the Process.
3. Hand the Process off to the corporate developer for implementation. The
corporate developer will underpin the Process with the necessary details
(such as calls to web services and so on) that will enable the Process to execute
in the specified Destination Environment.

4
About Projects, Packages and Processes
In TIBCO Business Studio there is a hierarchy consisting of Project, Package and

Process:
You must create a Project to use TIBCO Business Studio. TIBCO Business Studio
supports the full project life cycle, bringing together all artifacts in a single place.
The Project is the container for these artifacts. As such, Projects help to facilitate
sharing and organization of resources. For example, team members may have
different responsibilities but need to use the same resources that are made
available through the TIBCO Business Studio Project.
Each Project has a corresponding directory in the file system (specified when you
create the Project).
A Package is a mandatory container for Processes and their infrastructure
(Participants and Data Fields). For example, in the insurance environment,
separate packages could contain the Processes used by the Claims Department,
the Policy Origination/Maintenance Team and the IT Department. Processes can
be shared between Packages so libraries of process components can be created
and reused. For more information on reuse, see Reusing Processes on page 94.
A Process models actual and future business processes in your organization. The
Process Editor provides tools on a Palette that use Business Process Modeling
Notation (BPMN) features. By creating your business process this way, you can
fully prepare it for implementation by a specialist in your organization.

About Projects, Packages and Processes 5
|
Some objects such as Business Assets can be shared at the Project Level. Others
such as Data Fields and Participants can be created at either the Package level
(where they can be shared amongst Processes in that Package), or at the
individual Process level (where they can only be used by that Process).
Asset Types
Besides Business Assets, there are other types of Assets that you can include in
your Project. When you create the Project, you can decide which types of Assets to
include and also designate a Special Folder for each Asset type. For example, this
project has been created with the default folders for Packages and Concept
Models:

6
Getting Help in TIBCO Business Studio
TIBCO Business Studio uses online help and cheat sheets:

• The main help for TIBCO Business Studio is displayed by selecting Help >
Help Contents. The help and associated tutorials can also be accessed from
the Welcome page that is displayed when you first start TIBCO Business
Studio.
• Cheat sheets can be displayed by selecting Help > Cheat Sheets. They can
also be accessed from the Welcome page that is displayed when you first start
TIBCO Business Studio.

Using the Sample Processes 7
|
Using the Sample Processes
TIBCO Business Studio provides sample Processes that you can install from the
Welcome page. To install TIBCO Business Studio sample Processes, do the
following:
1. If you are starting TIBCO Business Studio for the first time, the Welcome
screen is displayed; otherwise click Help > Welcome.
2. Click the Samples button.
This displays a page that lists samples available for various products.
3. The TIBCO BPM samples are grouped together.
4. To install a set of sample Processes (for example the Process Modeling Tutorial
Solutions), click the link and in the resulting dialog, click Finish.
The XPDL Packages that contain the sample Processes are installed into your
workspace. You can modify these as necessary. If you want to revert to the
original copy of a sample Package, simply reinstall it from the Welcome page
and overwrite the current copy.

8
Creating a Project, Package and Process
To create a new TIBCO Business Studio Project, Package and Process, do the
following:
This section describes how to create a Project and at the same time create a
Package and Process using a template. You can however perform each operation
separately (see Creating a Package on page 72 and Creating a Process on page 75).
1. Select File > New > Project.

2. Expand Business Process Management, select Analysis Project and click
Next.
3. Enter the Project Name.
4. Either accept the default location for the Project (your workspace) or de-select
Use default location checkbox and click Browse to select a different location.
5. Click Next.
6. The Asset Type Selection dialog displays the types of Assets that you can
include in your Project. For example, for a BPM/SOA Developer Project, you
can include Business Processes, Concept Models, and so on. Select the types of
Assets you want to include in your Project and click Next. Later in the wizard
you will be able to specify the special folders for these Assets.
7. The default Packages Folder is called Process Packages; either accept the
default or rename the Packages Folder.
8. Optional - To apply a template, click the button next to the Apply
Template field.
Select one of the following templates:
— An empty package - Selecting this option creates a Packages folder with no
Processes.
— A package with an empty process - Selecting this option creates a Packages
folder and an empty Process (with no Activities, Events, etc.).
— A package with a simple process - Selecting this option creates a Package
and a Process with a Start Event, an Activity and an End Event.

Creating a Project, Package and Process 9
|
9. If you applied a template and want to accept the default properties of the
Package and Process, click Finish. Otherwise, click Next, modify the
following as needed, then click Finish to exit the template wizard:
— File Name - filename of the XPDL file where the Project, Package and
Process are stored.
— Name - Name of the Package. Defaults to the same name as the filename of
the package and is used for purposes such as simulation reports
— Author - username of the user who created the Package.
— Created - displays the date/time that the Package was created.
— Description - text description of the package.
— Documentation Location - URL or filename of any supporting
documentation.
— Status - project life cycle status for informational purposes. How or
whether you use life cycle statuses is up to you, but they are typically used
as follows:
UNDER_REVISION - for packages in development
UNDER_TEST - for packages in User Acceptance Testing (UAT)
RELEASED - for packages in production
— Business Version - version information about the Package.
The version you specify in this field is unrelated to any source control
system and Business Versions are entirely user-defined.
— Process Name - If necessary, change the name of the Process.

Click Finish.
10. For each Asset Type you selected to include in your Project, you can select a
special folder to hold that Asset Type. For example, if you selected the
Concept Model Asset Type, a dialog is displayed to allow you to change the
folder that will be used for Concept Models. To accept the default Special
Folder names, click Finish or to review each folder name, click Next and then
click Finish when you are done.
The newly-created Project is displayed in both the Project Explorer and the
Navigator views, along with any Packages and Processes that you elected to
create.
Previously the Project Explorer offered contextual view and Navigator offered a
file-based view, now these are both integrated into the Project Explorer (see
Project Explorer View on page 129).

10
Working with Processes
This section describes some common tasks and shortcuts to help you use the
Process Editor to create Processes. For additional information, see Process Editor
Tips and Tricks.
Adding Objects
Add an object (for example, a Task) by doing the following:
1. Click the appropriate tool in the Palette. If an object has more than one type
(for example, Service Task, User Task, and so on), each type has a tool on the
Palette. For example:
In this example, the different types of Tasks will be hidden when you click a
different tool on the Palette (for example, the Gateway tool). If you want the
available tasks to remain open, you can pin them open by clicking the Pin
Open button ( ).
If you want to add more than one object of the same type, hold down the Ctrl
key.
2. Position the pointer on the Process at the place where you want to place the
object. The pointer changes shape:
3. Click on the Process. The object is added.

Working with Processes 11
|
Connecting Objects
To connect two objects with Sequence Flow, do the following:
1. Click the Sequence Flow tool.
2. Position the pointer over the object that will be the source of the Sequence
Flow. The pointer changes shape:
3. Draw the Sequence Flow using one of the following methods:
While drawing the Sequence Flow, you can add bendpoints by right-clicking
or pressing the spacebar.
— Click the source object, then position the pointer over the target of the
Sequence Flow. If you are satisfied with the shape of the flow, click the
Target.
— Click the source object, holding down the mouse button, drag the pointer
to the target object and release the mouse button.
Selecting Objects
Select objects using one of the following methods:
• Use the Select tool on the palette. Hold down the Ctrl to add single objects to
the selection or Shift keys to select a range of objects.
• Using the Marquee tool. This allows you to drag a rectangle around all the
objects that you want to select.

12
Tutorial 1: Creating a Simple Process
To get started working with the Process Editor, use this tutorial to create a simple
Process that represents part of the hiring process within a company. In this
tutorial, we will do the following:
• Create the Project, Package and Process
• Customize the Lane
• Add Some Objects to Your Process
• Add Flow to the Process
• Add a Gateway
Task A Create the Project, Package and Process

1. Make the Project Explorer active by selecting Window > Show View > Project
Explorer.
2. If you have not already done so, create a Project and Package.
3. Select the Package you created, right-click and select New Process.
4. Click Next to accept the current Package and Process.
5. Enter Hiring for the Name and click Finish.
6. Double-click the title bar:
The Process Editor expands to fill the window. You can double-click the title
bar at any point to restore it to its original size (for example, if you need to see
other windows).
Task B Customize the Lane

1. Rename the lane by double-clicking Lane and entering the text HR
Department.

Tutorial 1: Creating a Simple Process 13
|
2. Make the Lane larger:

a. Click the Lane.
b. Position the mouse pointer over the bottom edge. The pointer changes
shape .
c. Drag the lower edge of the Lane to make it larger.
Task C Add Some Objects to Your Process

1. If the Palette is not visible, expand it by clicking the Show Palette button to
the right of the window:
2. On the Palette, click Start Event.

3. Press F1. This displays context help on Process Editor (if the Process Editor is
maximized, double-click the title bar to see the help). You can get context help
on specific tools in the palette by selecting them.
4. Position the mouse pointer over the white area of the Lane and click.
The Start Event (indicated by a circle) is added to your Process.
5. Double-click the Start Event and enter the text Start.
6. On the Palette, click Task.
7. Position the mouse pointer over the white area of the Lane (following the Start
Event) and click.
The Activity is added to the Process.
8. Double-click the newly-added Activity and enter the text Receive
Application.

14
9. Add another Activity in the same manner, naming it Review Application.

Your Process should now look like this:
Task D Add Flow to the Process

The Process now consists of three disconnected objects. Now we will add
Sequence Flow to the Process.
1. On the Palette, click the Sequence Flow tool.
2. Click the Start Event (this marks the beginning of the Flow).
3. Click the Receive Application Activity (this marks the target of the Flow).
The Process should look like this:
4. Another way to add Sequence Flow is by dragging: click the Receive

Application Activity, click the Sequence Flow tool and holding down the
mouse button, drag the pointer to the Review Application Activity and
release the mouse button.
• If you have several Sequence Flows to add, hold the Ctrl key down while
adding them to avoid having to re-select the Sequence Flow tool.
• For easier alignment of objects in the Process Editor, you can select either or
both of the following options:
— Diagram > Grid - This allows you to align objects to a grid.
— Diagram > Alignment Guides - As you move objects in a Process Editor, a
blue line appears when the center of two objects coincides.
Task E Add a Gateway

1. Click the Gateway tool and add a Gateway after the Review Application
step.
2. Double-click the Gateway and name it Accept?.

Tutorial 1: Creating a Simple Process 15
|
3. Add Flow that connects the Review Application Activity and the Gateway.
The Process should look like this:
4. From the Gateway, add Regret Letter and Interview. Add Sequence Flow to
connect these to the Gateway:
5. Double-click the title bar to see the Project Explorer. Note that at this point you
have not saved the Process. This is indicated in the Project Explorer by an
asterisk (*) next to the Package that contains the Process. For example:
6. Right-click the Package, select Save and note that the asterisk disappears.
Summary
This tutorial explored using some of the Palette tools to create a simple (although
incomplete) Process. Continue with Tutorial 2: Extending a Simple Process on
page 16.

16
Tutorial 2: Extending a Simple Process
In the previous tutorial we created a simple Process that represented the

beginning of a hiring process. In this tutorial, we will add to this Process,
exploring some of the advanced features of the Process Editor, including:
• Add a Timer Intermediate Event
• Add Text Annotations and Associations
• Configure Service and User Activities
• Add an Exclusive Gateway
• Add an Activity Loop
• Add Conditional Flows
These features are part of the complete set of Business Process Modeling Notation
(BPMN).
Task A Add a Timer Intermediate Event

1. Open the Hiring Process that you created in Tutorial 1: Creating a Simple
Process.
2. Add a new Activity Remind Interviewer below the Review Application
Activity:

Tutorial 2: Extending a Simple Process 17
|
3. Select the Timer Intermediate Event tool from the Palette:
4. Place the Timer Intermediate Event on the boundary of the Review

Application Activity. It should look like this:
5. Connect the Remind Interviewer Activity to the Timer Intermediate event as

follows:
This means that this Sequence Flow is followed based on a time-based

expression supplied when the Process is implemented. In this case, if a
specific time limit is exceeded, the interviewer is sent a reminder to review the
application.
Task B Add Text Annotations and Associations

To explain or document your Process, you can add text annotations and associate
them with an object as described in this section.

18
1. Click the Text Annotation tool and add the following next to the Remind
Interviewer Activity. You can enter the text in the Properties view:
2. You can associate this annotation with the Remind Interviewer by selecting
the Association tool, then clicking the annotation and then the Remind
interviewer Activity:
3. Add annotations to the Sequence Flow coming out of the Accept? Gateway to
indicate the Yes and No paths:
Task C Configure Service and User Activities

Some activities can be performed automatically (for example, an automated email
reminder) and others must be performed by a user (such as conducting an
interview). In TIBCO Business Studio, automatic activities are called "service
activities" and manual activities are called "user activities."
1. Right-click the Remind Interviewer Activity that you created and select Show
Properties View.
2. The properties of the Activity are displayed, including the Activity Type,
which is Task by default.
3. Because the sending of the reminder email is a Task that could be automated,
select Service Task.

|
4. The Remind Interviewer Activity changes appearance to indicate that it

represents a Service Task:
5. Repeat this for the Interview Activity, but make it a User Task.
Note that you can also create a User Task by right-clicking the Activity and
selecting Activity Type > User Task.
Task D Add an Exclusive Gateway

At the end of the interview, a decision is made as to whether to hire the candidate.
However, in this case it is not a simple yes-no decision. We will construct a
Gateway to represent the exclusive choice of three options.
1. Add a Gateway to represent the conclusion of the interview. Give it the name
Hire? and position it to the right of the Interview Activity.
2. Add a flow from the Interview Activity to the newly-added Gateway.
3. Add two new Activities and flows that connect them to the Gateway as
follows:

20
4. Add a Sequence Flow from the Gateway back to the Regret Letter Activity.
This indicates that the result of the Interview is one of the three results that
flow from the Hire? Gateway.
Task E Add an Activity Loop

Some Activities may need to be repeated. For such Activities you can use a loop.
In our example, the Remind Interviewer Activity may need to be repeated.
An Activity Loop is an annotation that indicates a repeated Activity in the

Modeling environment only. At runtime, this behavior might be achieved
differently depending on destination environment.
1. Right-click the Remind Interviewer Activity and select Show Properties

View.
2. The properties of the Activity are displayed, including the Activity Markers.
3. Select Standard Loop.
4. The Activity changes to show that it contains a loop:
Task F Add Conditional Flows

In our example, we don’t want to endlessly keep looking for candidates. If we
identify a likely candidate, we need to begin the hiring process again.

|
Similarly if we create a shortlist, we may decide to make an offer to one of the

short-listed candidates.
1. Add a Sequence Flow that connects the Shortlist but keep looking Activity
back to the Receive Application Activity. You may need to reposition the flow
to make the process diagram legible.
2. Right-click the Sequence Flow that you created and select Show Properties
View.
3. The properties of the Sequence Flow are displayed, including the Type of
Sequence Flow.
4. Select Conditional (this can be completed by the Implementer. A diamond is
added to the source of the Sequence Flow to indicate that it is conditional:
5. In the Properties view, in the Name field of the Sequence Flow, enter a
description of the condition. This is to help the Implementer with the technical
implementation of the condition.
6. Add an End Event to the right of the Offer Activity, label it and connect it
with a Sequence Flow.
7. Add a Default Sequence Flow from the Shortlist but keep looking Activity to
the End Event.
8. Save the Process.

22
The process diagram that you created should look similar to this:
Summary
In this tutorial we explored some of the advanced features of the Process Editor,
including features that form the complete set of BPMN. Although this is a
reasonable approximation of the hiring process, it could be extended further. For
example after making an offer there could be another process that starts. Also the
interview Activity could be broken down into further steps that could be
represented as a Sub-Process.

Tutorial 3: Refactoring Activities into a Sub-Process 23
|
Tutorial 3: Refactoring Activities into a Sub-Process
This tutorial shows how to create a Sub-Process from several objects in the
Process. In the Hiring Process, it is possible that the Receive Application, Review
Application and Remind Interviewer Activities are related. For example, they
could be the responsibility of the same department. If that were the case, we could
move these Activities into a Sub-Process as follows:
1. Select the three Activities that will be refactored into the Embedded
Sub-Process:
2. Right-click and select Refactor > Move into New Embedded Sub-Process.

24
3. The following warning dialog is displayed:
This warning is generated because before refactoring, the Sequence Flow

proceeds from the Review Application Activity to Gateway without
necessarily waiting for the Remind Interviewer Activity to complete.
However, after refactoring, the End event that will be inserted effectively
synchronizes the two Activities meaning that flow will not proceed until both
Activities have finished. A similar situation exists for the multiple flows going
into the Receive Application Activity.
Select the check box to confirm this change to the Process and click Next.

Tutorial 3: Refactoring Activities into a Sub-Process 25
|
4. The following dialog is displayed:
Complete the dialog as follows:

— Enter Process Application as the name for the Embedded Sub-Process that
you want to create.
The Insert end event in new sub-process check box is selected and greyed out
in this case because in the preceding step you elected to joining the multiple
exit path to the selection. Therefore the End event is mandatory.
5. Click Finish. The Activities that you selected are placed within a new
Embedded Sub-Process called Process Application:

26
Summary
In this tutorial we refactored some Activities into a Sub-Process. Because we were
changing the Process slightly by doing this, there was a warning message to allow
us to confirm the change.

Tutorial 4: Working with Process Fragments 27
|
Tutorial 4: Working with Process Fragments
The Diagram Fragments view allows you to reuse parts of your Process by
allowing you to drag a group of objects to the Fragment Explorer and save them.
You can then use the "fragment" that you saved to construct another Process.
TIBCO Business Studio also provides some predefined BPMN process fragments
that you can drag and drop onto your Processes.
This tutorial shows how to use predefined Process Fragments and how to create
your own Process Fragments.
Suppose that the Process Application Embedded Sub-Process of the Hiring
Process is one that you are likely to reuse in other Processes. You can capture the
useful part of the Process as follows:
1. Make sure that the Diagram Fragments view is visible. If it is not, select
Window > Show View > Diagram Fragments.
2. In the Diagram Fragments view, there is a treeview that looks similar to the
Project Explorer. This is the Fragment Explorer.
3. Create a new Category by either right-clicking a folder in the Fragment
Explorer and selecting New > New Fragment Category or by clicking the
Create Custom Fragment Category button ( ).
4. Click in the name field of the newly added Category and name it My Hiring
Fragments.
5. Open the Hiring Process in the Process Editor and select the Process
Application Embedded Sub-Process.
6. Press Crtl and drag the selection into the Diagram Fragments view.
You can also use the Copy and Paste menu options either by right-clicking or by
selecting from the Edit menu.

28
7. The Fragment that you created is stored in that Category with the name New
Fragment. Click on the name, and rename it Process Application.
8. Create a new Process and Name it Hiring 2.

9. Drag the Process Application fragment from the Fragment Explorer to the
new Process. You can see that in this way, the Process Application fragment
can be reused in new Processes.
In the Fragment Explorer, clicking the Category that you created displays
graphical previews of the Fragments in that Category.
To use one of the predefined fragments in your Process, do the following:

1. Open the Hiring 2 Process.
3. Expand BPMN Process Fragment folder. This contains Categories of BPMN
Process Fragments.
4. Expand the Basic Fragments Category.

Tutorial 4: Working with Process Fragments 29
|
5. Select the Task Sequence Fragment. This consists of two Tasks connected by
Sequence Flow:
6. Drag the Task Sequence Fragment onto the Hiring 2 Process and place it after
the Embedded Sub-Process.
You can see that the two Tasks have been added to the Process. You can then
continue to add other Fragments or to add other objects manually.
Summary
In this tutorial, we created a Process Fragment from an existing Embedded
Sub-Process and then used that Fragment in a new Process. We also added a
predefined Fragment to the new Process.

30
Tutorial 5: Exporting to the TIBCO iProcess Modeler
This tutorial shows how to take the Process defined in the previous tutorial and
export it to the TIBCO iProcess Modeler.
In the previous tutorials, we created a Process that approximated a hiring process
in an organization. Because we did not specify a destination environment when
we created the Process, only basic BPMN validation was performed when we
saved it. If we want to deploy this Process to the TIBCO iProcess Modeler, we
need do the following:
• Set the Destination Environment and Correct Validation Errors
• Export the Process from TIBCO Business Studio
• Import the Process into the TIBCO iProcess Modeler
Task A Set the Destination Environment and Correct Validation Errors

1. Go to the Properties View for the Hiring Process (from Tutorial 2 solution) and
click the Destinations tab.
2. Select the iProcess Modeler as the Destination Environment. The Hiring
Process is validated for potential import into the TIBCO iProcess Modeler.
Note that a red "x" appears in the Project Explorer. This is because the Process
cannot be imported into the TIBCO iProcess Modeler in its current state.
3. Several errors are reported in the Problems View.
4. From the Problems view, correct the errors and warnings as follows:
— Several errors are generated because the Process cannot have Default or
Conditional Sequence Flows on Activities (they must flow from a
Gateway). Insert an XOR Gateway after the Shortlist but keep looking
Activity and connect the Conditional and Default Sequence Flows to the
Gateway. This is in accordance with BPMN best practices for making
explicit use of Gateways in this situation.
— Several warnings are generated because the Activities must be either User,
Service or Sub-Processes. Right-click each error and select Quick Fix to
change each of these Activities.
— The embedded Sub-Process in the Process cannot be exported to the
iProcess Modeler. To correct this, recreate the original Process (before the
embedded Sub-Process was created). You can do this by copying the
Activities out of the embedded Sub-Process and into the main Process.
When you have done this, delete the embedded Sub-Process.

Tutorial 5: Exporting to the TIBCO iProcess Modeler 31
|
5. Save the Package and check the Problems view to ensure that all the
validation errors have been corrected.
Task B Export the Process from TIBCO Business Studio

Export the Process and its containing Package as follows:
1. Select the Package that contains the Hiring Process.
2. Select File > Export. The Export dialog is displayed.
3. Select TIBCO iProcess Modeler XPDL and click Finish.
4. The exported Process appears in the Project Explorer under Exports >
iProcess Modeler XPDL and in the file system in your workspace in the
\projectname\Exports\iProcess Modeler XPDL directory.
Task C Import the Process into the TIBCO iProcess Modeler

Import your TIBCO Business Studio Process as you would any other Process (see
the TIBCO iProcess Modeler Procedure Management Guide for more information).
See Object Mappings - TIBCO iProcess Modeler on page 145 for information
about how TIBCO Business Studio objects are mapped into TIBCO iProcess
objects.
Open the Process in the TIBCO iProcess Modeler and complete its detailed
implementation. Then execute and test the Process.
1. Start the TIBCO iProcess Client.
2. In the Procedure Manager, select the Library into which you want to import
the Process.
3. Select Procedure Management > Load From and browse for the XPDL file of
the Package that contains the Hiring Process. Click OK.
4. Information about the Package and Procedures is displayed. Click Load.

32
5. Depending on whether you did all of the tutorials, one version of the
imported Procedure looks similar to this:

Deploying a Process 33
|
Deploying a Process
Deployment is part of the software development cycle (design, deploy, execute).

After preparing the software some transformation, packaging, physical delivery,
configuration and initialization takes place. All of these, some of which may be
optional, are aspects of deployment.
For more information about deployment, see the TIBCO Business Studio Process
Developer’s Guide.

34

| 35
Chapter 2 Concepts and Definitions
This section of the help defines concepts and terminology related to TIBCO
Business Studio.
Topics
• Artifacts, page 36
• Connecting Objects, page 39
• Flow Objects, page 42
• Process Components, page 54
• Process Fragments, page 55
• Project Objects, page 56
• Special Folders, page 63
• Standards Support, page 64
• Swimlanes, page 65

36
| Chapter 2 Concepts and Definitions
Artifacts
Artifacts are used to add more information about a Process. Artifacts include Data
Objects, Text Annotations and Groups, all of which do not affect the Sequence or
Message Flow of the Process.
Data Objects
A Data Object is used for informational purposes to show how a document or
other data relates to the Process. It may be associated with a Sequence Flow or
Message Flow, but like other Artifacts it does not affect either flow.
Data Objects are usually associated with Flow Objects with an Association:
The Data Object in the preceding example should not be confused with the actual
Message being sent between the two Pools.

Artifacts 37
|
A Data Object can also be associated with a Sequence Flow or other Flow Object:
Data Objects are not preserved during export to the TIBCO iProcess Modeler.
Text Annotations
Text Annotations serve to explain or clarify the Process. They can be connected to
Flow Objects (for example, Tasks) using an Association:
Unlike any text that you enter on the Description tab in the Properties view for an
object, Text Annotations are displayed directly on the Process.

38
Groups
Groups are used to indicate a relationship between elements of a Process by
enclosing them in a dashed line. A Group can span Lanes and Pools. For example:
Lane 1
Lane 2
Groups are not preserved upon export because they have no meaning in the
runtime environment.

Connecting Objects 39
|
Connecting Objects
You can create a relationship between Flow Objects or between Flow Objects and
other information using the following Connecting Objects such as:
• Associations
• Message Flows
• Sequence Flows
Associations
An Association is a connection from a Data Object or Text Annotation to a Flow
Object (for example, an Activity) used to make a Process more readable:
Associations are not preserved during export to the TIBCO iProcess Modeler.
Message Flows
A Message Flow indicates the flow of messages between objects in separate Pools
or between Pools. For example:

40
This Process shows a Mortgage Approval Process where the Customer Details are
sent to the Credit Agency for approval using a message. In this case the Pool and
Lane that represent the Credit Agency Process are closed because we either do not
care about or are not familiar with their internal Processes.
Sequence Flows
Sequence Flows indicate the order in which Activities will be performed. You can
set up Sequence Flows between Flow Objects. When you create a Sequence Flow,
you can highlight it, right-click and select one of the following types of Sequence
Flow:
• - Shows the default flow from a Gateway or Activity.
• - Shows a flow that is only followed if the associated

condition is met.
• - Indicates a flow that does not have a condition

associated with it (the default).

Connecting Objects 41
|
Example
In this example, an enquiry is responded to either by email (the default), or

depending on a condition, by fax.

42
Flow Objects
Flow Objects are the main category of BPMN objects used to define the business
process. They include:
• Activities
• Events
• Gateways
Example
The following process contains several Flow Objects - a Start Event, a Gateway,
two Activities and an End Event:
Activities
An Activity represents work that a company or organization performs using
business processes. An Activity can be atomic (it is not broken down into a finer
level of detail) or non-atomic. Atomic Activities are represented in the Process
Editor by Tasks. For more information, see http://www.bpmn.org.
When creating the TIBCO Business Studio Process, each time a different person,
group, role, or system does something, an Activity is added to the Process.
Activities may be triggered by events such as the receipt of an email, phone call or
workflow item, and may involve making a judgement on the presented facts and
performing an action (such as entering data to a computer system, phoning
someone in the same or different organization, and so on).

Flow Objects 43
|
Tasks
A Task in a process diagram represents an atomic Activity (one that cannot be
further broken down). A Task of an unspecified type looks like this in the Process
Editor:
If the Activities can be broken down into finer steps, they should be represented
as Sub-Processes. The Activity Type is set in the Properties view. Activity Markers
are also set in the Properties view and are indicated by symbols within the Task.
User Tasks
User Tasks are those that require human interaction with a software application.
For example:
Manual Tasks
Manual Tasks are those that are completed by a person without using software.
For example:
Service Tasks
Service Tasks can ideally complete without human interaction (for example, an
automatic email notification or a web service). For example:

44
Script Tasks
Script Tasks contain a set of instructions written in a scripting language (usually
added to the step by the corporate developer) that will be executed in the runtime
environment when the Process is deployed and executed. For example:
Send Tasks
Send Tasks are used to send messages to a system or person outside of the
Process (often using a web service):
Receive Tasks
Receive Tasks are used to wait for a message from a system or person outside of
the Process (often using a web service). This type of task can be used to start a
Process as long as it has no incoming Sequence Flow and there are no Start Events
in the Process:
Reference Tasks
Reference Tasks refer to another Task and prevent you from having to duplicate
the same Task several times in a Process.

Flow Objects 45
|
Sub-Processes
Some Activities can contain further steps, or Sub-Processes.
There are two types of Sub-Process that are described in this section, Embedded
and Independent. For more information about how Processes can be reused, see
Reusing Processes on page 94.
A Sub-Process that is Embedded can be re-factored into an Independent

Sub-Process and vice versa. For more information see Refactoring Sub-Processes
on page 97.
Embedded
An Embedded Sub-Process looks similar to the following:
An Embedded Sub-Process has the following characteristics:

• It is fully contained within the parent Process, and is executed within the
parent Process.
• Activities within the Embedded Sub-Process have access to the same Data
Fields and Parameters as the parent Process and Package.
• No data mapping is required.
• It cannot contain Lanes and Pools.
Embedded Sub-Processes cannot be exported to the iProcess Modeler or deployed

to the iProcess Engine.

46
Independent
Activities that contain an Independent Sub-Process look like this in a Process
Editor:

Flow Objects 47
|
Click the plus sign (+) in the Activity to view the Sub-Process.
An Activity of this type defines a call-out to another Process:
• The called Process exists as a separate Process from the parent Process, and
because of this it can be started from other Processes.
• The called Process does not have access to Data Fields and Parameters of the
calling Process and Package. For this reason, data mapping must be
performed to and from the called Process.
Transactions
A Sub-Process (either Embedded or Independent) can be specified as a
Transaction using the Is a transaction check box. This means that the behavior of
the Sub-Process is governed by a transaction protocol. This is indicated by a
double-line around the Activity:
Typical outcomes of a Transaction Sub-Process that you should cater for are
Success and Cancel. For more information, refer to the BPMN specification.
Activity Markers
Activity Markers indicate parts of the BPMN complete set that you can select on
the Properties of the Activity. The currently selected Activity Marker is indicated
by the following symbols on the Activity:
• Multiple Instance Loop - Indicates a Task or Sub-Process that is replicated
a fixed number of times. This reflects the programming construct for each.
• Standard Loop - Indicates a Task or Sub-Process that may have more than
one instance, depending on the conditions of the Loop. When the condition is
placed before the Activity, the Loop is in effect a While loop; after the Activity
it functions like an Until loop.
• Ad-hoc - Indicates an Embedded Sub-Process marker that contains

Activities that have no pre-defined sequence. This also means that the number
of times the Activities are repeated is completely determined by the
performers of the activities and cannot be defined beforehand.

48
Events
An Event in a process is something that happens, for example the start of the
Process. There are three main types of Event: Start, Intermediate and End.
Start Events
Start events can be used to indicate the start of a Process (they are optional).
Different types of Start events can control how a Process is started (or triggered):
• Untriggered ( ) - there is no specific trigger to start the Process.
• Message ( ) - the Process is started upon receipt of a message. This can be

implemented using a web
service:
The configuration of the web service is done in the same manner as adding a
service call to a Process. You must first import a WSDL file, and then select the
desired operation. For more information see TIBCO Business Studio Process
• Timer ( ) - the Process is started at a specific date/time or at a regular

interval (time
cycle):

Flow Objects 49
|
• Rule ( ) - the Process is started by a Rule:
• Link ( ) - the start of an Embedded Sub-Process is linked from (and

triggered by) the completion of an End event in another Embedded
Sub-Process within the same parent Process.
• Multiple ( ) - there can be several possible triggers for the start of the
Process, which are specified in the Properties view of the Start event.
Intermediate Events
Intermediate events can be placed after Start events and before End events to
indicate messages, exceptions, compensation, and so on. Most types of
Intermediate events can also be placed on the border of an Activity. You can use
the following types of Intermediate events:
BPMN imposes some restrictions on the placement of Intermediate events. For

example:
• Intermediate events of type None and Link cannot be placed on the boundary
of a Task.
• Intermediate events of type Cancel and Multiple cannot be placed in
Sequence Flow.
TIBCO Business Studio allows you to place any type of Intermediate event on the
boundary of a Task or in Sequence Flow; however any invalid constructions are
reported in the Problems view.
• Untriggered ( ) - indicates an unspecified change in the Process.
• Message ( ) - the Event is triggered upon receipt of a message. This can be

implemented using a web service. The configuration of the web service is
done in the same manner as adding a service call to a Process. You must first
import a WSDL file, and then select the desired operation. For more
information see TIBCO Business Studio Process Developer’s Guide.

50
• Timer ( ) - the Event is triggered at a specific date/time or at a regular

interval (time cycle). When placed on the boundary of a Task, a Timer Event
defines deadline for iProcess step. In the Properties view for the Event, there
are two options you can select (Withdraw Task on Timeout and Continue
Task on Timeout). These are equivalent to the iProcess Withdraw flag.
• Rule ( ) - the Event is triggered based on the evaluation of a Rule.
• Link ( ) - indicates a connection from one or more Link Intermediate

Events to another Link Intermediate event in the same parent Process. This
can be thought of as a "go to" or "off page connector" that you can use to break
up a Process for better legibility.
You can also connect a Link End event in an Embedded Sub-Process to a Link
Intermediate event in another Embedded Sub-Process.
• Multiple ( ) - there can be several possible triggers for the Event, which are
specified in the Properties view for the Event.
• Error ( ) - This is used for error handling:
— If located in Sequence Flow of the Process, this event throws an error.

— If located on the boundary of an activity, this event either catches the
specified errors, or catches any error if no specific error is specified.
• Compensation ( ) - indicates that compensation is necessary:
— If located in Sequence Flow of the Process, this event calls for

compensation.
— If attached to the boundary of an activity, this event reacts to a named
compensation call.
• Cancel ( ) - This type of Intermediate Event is used on the boundary of a

Transaction Sub-Process. It is triggered if a Cancel End Event is reached
within the Transaction Sub-Process or if a Transaction Protocol “Cancel”
message is received while the Transaction is being performed.
End Events
An End event indicates when the Process has completed. They are optional,
however if a Process contains a Start event, it must contain an End event. End
events have different types that indicate different results upon completion of the
Process:

Flow Objects 51
|
• No Result ( ) - there is no specific end result to the Process.
• Message ( ) - indicates that a message is sent at the end of the Process.
• Link ( ) - indicates that the end of an Embedded Sub-Process is linked to

the Link Start event or a Link Intermediate event of another Embedded
Sub-Process.
• Multiple ( ) - indicates that there is more than one result that will occur
when the Process ends. You can specify the desired results on the Properties
view for the End event.
• Error ( ) - indicates that the specified error is generated at the conclusion

of the Process.
• Compensation ( ) - indicates that a compensation is necessary. For more

information, see the BPMN specification at http://www.bpmn.org.
• Cancel ( ) - used within a Transaction Sub-Process to trigger a Cancel

Intermediate event attached to the Sub-Process boundary.
• Terminate ( ) - ends all Activities in the Process immediately without

Compensation or Events.
Gateways
Gateways are a control mechanism for the Sequence Flow in the process. They are
represented by a diamond:
Although the Gateway resembles a decision box in a flow chart, Gateways are
used for branching, merging, forking and joining as well as for conditional
decisions (see Workflow Patterns in Business Processes on page 87).
As shown on the Properties view of a Gateway, these are the different types of
Gateway that you can create:

52
Exclusive (XOR)
In an Exclusive Gateway, there are several paths through which the Process can
continue, but only one is actually chosen when the Process is run. There are two
types of Exclusive Gateway:
• Exclusive (Data) - The Sequence Flow is chosen based on an expression using
data from the Process. This type of Gateway is indicated in the Process as
follows:
• Exclusive (Event) - The Sequence Flow is chosen based upon an external event
(for example, a JMS message). This type of Gateway is indicated in the Process
as follows:
The following shows a typical XOR (Data) Gateway:
There is one uncontrolled input Sequence Flow to the Gateway, and conditional
and default output Sequence Flows. This example is compatible for export to the
TIBCO iProcess Modeler (see Import the Process into the TIBCO iProcess Client
on page 116).
Inclusive (OR)
An Inclusive Gateway looks like this:

Flow Objects 53
|
In an Inclusive Gateway used as a fork, each output Sequence Flow is

independently evaluated according to an expression. This means that anywhere
from zero to the maximum output Sequence Flows can be taken. In practice, you
should either provide a default Sequence Flow or ensure that at least one
Sequence Flow evaluates to True.
When used as a Merge, any upstream Sequence Flows are synchronized, but the
Gateway does not wait for all Sequence Flows.
Complex
A Complex Gateway is used to fork or merge depending on how an expression
evaluates. When used as a Decision, the expression determines which of the
outgoing Sequence Flow are chosen for the Process to continue.
When used as a Merge, the expression determines which of the incoming
Sequence Flows is required for the Process to continue. This type of gateway is
indicated in the Process as follows:
Parallel (AND)
A Parallel Gateway is used to fork or merge several parallel paths
(synchronization). When several Sequence Flows enter a parallel gateway, the
process flow waits until all arrive at the gateway before continuing. This type of
gateway is indicated in the Process as follows:

54
Process Components
Process components represent reusable building blocks that encapsulate the

management of a particular item in a business process. The process components
form a reusable library that you can call upon in different contexts. For example,
you might have an item to "verify the caller’s address/contact details" in the
business process for taking out an insurance policy. This could be implemented as
a Sub-Process and this particular Process Component could also be used in the
context of renewing an insurance policy.

Process Fragments 55
|
Process Fragments
The Diagram Fragments view allows you to reuse parts of your Process by
allowing you to drag a group of objects to the Fragment Explorer and save them.
You can then use the "fragment" that you saved to construct another Process.
TIBCO Business Studio also provides some predefined BPMN process fragments
that you can drag and drop onto your Processes.
For more information, see Using Process Fragments on page 104.

56
Project Objects
Before you can create business processes, you must create a Project and a Package.
Project
Projects help to facilitate sharing and organization of resources. Each Project has a
corresponding directory in the file system (specified when you create the Project).
Package
A Package consists of one or more Business Processes. The Package and any
Processes stored in it are saved in XPDL format. You can Export a package and its
Processes and then import them into the TIBCO iProcess Modeler for
implementation.
When you create a Project, you have the option of creating a special Packages
folder. By doing this, you can utilize special features of the Project Explorer such
as being able to view the Participants, Data Fields and so on. If you do not use a
special Packages folder, you only see the XPDL file for the Package in the Project
Explorer.
You can toggle the use of the Packages folder by highlighting the Packages folder
in the Project Explorer and selecting Special Folders > Do not use as Packages
Folder, which results in a view of the Package like this:
Alternatively, you can enable the use of the special Packages folder by
highlighting the Packages folder in the Project Explorer and selecting Special
Folders > Use as Packages Folder. This results in a view of the Package like this:
Process
TIBCO Business Studio allows you to create a Process that models actual and
future business processes in your organization. Each Process contains one or more
Activities, which are linked together via Sequence Flows.

Project Objects 57
|
Extended Attributes
Extended attributes can be used to add extra information to the schema such as:
• XML
• Plain text descriptions
• Supply Chain Management (SCM) metrics and best practices
They are added either on the Extended tab of the Properties view for those objects
that support extended attributes, or on the Extended Attributes dialog in the New
Process wizard.
Data Fields
Data Fields are used to represent the data that is used internally in a Process as
either input to or output from an Activity. For example, suppose an Activity is to
identify a list of suitable candidates for an available position. You can create Data
Fields to represent the pool of candidates going into the Activity and the suitable
candidates that have been identified.
If you intend to execute a Process in the TIBCO iProcess Engine, be aware that
Data Fields or Parameters with spaces in their names cannot be used for
mapping (for example, mapping to Parameters in a web service).
There are several ways of defining a Data Field:

• Array - by selecting the Array checkbox, you can define a Data Field to be an
array of the Basic Type that is selected. For example, if you select the Array
checkbox and String, you are defining the Data Field as an array of strings.
• Basic Type - the following types; each denoted with a unique icon:
• Declared Type - you can define the Data Field to be a Declared Type that you
have already defined.
• External Reference - to a concept defined in the Concept Modeler.

58
Declared Type
Declared Types are used if you want to re-use a definition either when creating a
Data Field or Parameter. For example, you could create a Declared Type that is a
string that represents a telephone number:
This Declared Type is then available for use in defining Data Fields or Parameters.
For example:
Parameters
Parameters are similar to Data Fields but are either input to or output from an
external source. For example, during simulation Parameters are either created by
TIBCO Business Studio or imported from a file. Parameters can be any of the
following types:

Project Objects 59
|
• Basic type -
— Boolean - true or false
— Date Time - combination of date/time
— Decimal Number - decimal number of the specified length and decimal
places (for example, 130.34)
— Integer Number - integer value of the specified length (for example, 345)
— Performer - is a text field that you want to use as a Participant
— String - alphanumeric characters of the specified length
• Declared Type - you can define the Data Field to be a Declared Type that you
have already defined.
• External Reference - to a concept defined in the Concept Modeler.
Parameters can also be specified as input, output or both by selecting the Mode
(In, Out, or In/Out). The mode is indicated by the icon next to the Parameter:
Participants
Participants are used to identify who or what performs an Activity. For example,
in a hiring process, a person (Human Participant) interviews the candidate and an
email system (System Participant) sends out an automatic follow-up reminder.
There are several types of Participant:
• Role - identifies the role responsible for performing an Activity. For example,
in a financial institution there may be roles such as Reconciler, Manager, and
so on.
• Organizational Unit - identifies the department or unit within an
organization that performs an Activity. For example, Legal, Marketing and so
on.
• Human - identifies a specific person or user that performs an Activity.
• System - identifies an activity that is performed by the system.

60
The iProcess Modeler concept of a Role is different to that in BPMN. A BPMN role
(as modelled in TIBCO Business Studio) represents a group of behaviors. For
example, one individual could have the roles of second line support as well as
project manager, and others can hold those roles too. In many cases there is no
reason to choose one person over another if they both share the same role (for
example, both are project managers). In the iProcess Modeler, a role corresponds
to only one person. Therefore, one individual having the role of project manager
prohibits anyone else having that role.
Though both human and role in Studio appear in the Users column in the iProcess
Modeler, in fact the former is mapped to an iProcess user (an individual) and the
latter is mapped to an iProcess group.
Assets
Assets include XPDL package files, WSDL files, documents, Decision Tables,
Concept Models, and so on that relate to the Project. These are usually stored in
Special Folders under the Project and include the following:
• Business Assets
• Business Process Assets
• Concept Model Assets
• Service Assets
Because TIBCO Business Studio is extensible, there may be other types of Assets
displayed.
Business Assets
Business Assets include any documents, spreadsheets, and so on that are relevant
to the project.

Project Objects 61
|
Prince2 Assets
TIBCO Business Studio provides Assets to support Prince2 project management
methodology. To add these to your Project, expand the Project, right-click
Business Assets and select Create Prince2 Template. For example:
You can add a new Stage File by right-clicking Business Assets > Prince2 and
selecting New Stage File.
Ad-hoc Assets
Ad-hoc Assets include Microsoft Office documents and image files not recognized
as Project Management Assets. You can add Business Assets by right-clicking and
selecting New > Folder or New > File, and selecting the appropriate Parent
Folder.
To view the folder or files you have created, go to the Navigator view. In the
Navigator view, you can also drag files and folders to different locations.
Business Process Assets

Business Process Assets include the XPDL Package file and all the associated
Processes, Data Fields, Parameters, and so on. The default Special Folder for
Business Processes is called Process Packages. For more information about
Special Folders, see Working With Special Folders on page 86.
Concept Model Assets

Concept Model Assets include the files for any Concept Models that you create.
These have the file extension .concepts. The default Special Folder for Concept
Models is called Concept Models. For more information about Special Folders,
see Working With Special Folders on page 86.

62
Service Assets
Service Assets include the WDSL files for any Web Services that you import into
your Project. The default Special Folder for these assets is called Services. For
more information about Special Folders, see Working With Special Folders on
page 86.

Special Folders 63
|
Special Folders
A Special Folder is a folder in the Project Explorer under which you can store the
Assets for your Project. When you create the Project, you can decide which types
of Assets to include and also designate a Special Folder for each Asset type. A
Special Folder can have unique behavior such as the Services folder which allows
you to expand the operations of contained WSDLs:
The following table shows the Asset Types and the default Special Folder for each.
Asset Type Default Special Folder

Business Process Process Packages
Concept Models Concept Models
Services Service Descriptors

64
Standards Support
TIBCO Business Studio supports several industry standards, namely Business

Process Modeling Notation (BPMN) and XML Process Definition Language
(XPDL).
Business Process Modeling Notation (BPMN)

BPMN is a graphical notation developed by the Business Process Management
Initiative (BPMI) for representing the steps and flow of business procedures. The
TIBCO Business Studio Process Editor supports the core set of this notation and
the Properties View supports the complete set.
For more information, see http://www.bpmn.org.
XML Process Definition Language (XPDL)

XPDL is used to represent the underlying structure of a business process to
TIBCO Business Studio. Packages are stored in XPDL format. Normally, you do
not use XPDL directly, but indirectly by creating a business process using the
Process Editor or by creating a Package. This version of the TIBCO Business
Studio provides support for XPDL2 and uses XPDL1 for deployment to the
iProcess Engine.

Swimlanes 65
|
Swimlanes
Swimlanes consist of Lanes and Pools.
Lanes
A Lane is a subdivision of a Pool that is used as a container for partitioning
Processes. How you use Lanes is specific to your business. A Lane can be Normal
or Closed. The contents of a Normal Lane are visible. The contents of a Closed
Lane are not visible and are used for "black-box" Processes where you do not
know the details of the contained Processes.
If you delete a Lane in TIBCO Business Studio, all the objects in that Lane are
also deleted. If you do this inadvertently, press Ctrl+Z to restore the contents of
the Lane.
Examples
Suppose the back office of a financial institution has a Process in which the
Securities Reconciliations Department, the Cash Reconciliations Department, the
Legal Department and a custodian are all involved. When defining this process,
they can be represented by lanes within the pool:

66

Swimlanes 67
|
Sequence Flow can connect objects in different Lanes:

68
The previous example shows a securities trade between a Broker and a Custodian.
The same trade could be represented as follows:
This shows the Custodian Lane in a Normal state and the Broker Lane in a Closed
state. The trade might be represented this way because it is documenting the
Custodian’s part in the trade and the Custodian has no knowledge of the internal
processes of the Broker.
Pools
A Pool is used as a container for partitioning Processes in ways that make sense
for your business. They are used in conjunction with Lanes. Messages can also be
used to show message flow between objects in different Pools.

| 69
Chapter 3 Tasks
This section of the help describes some of the common tasks that you perform
using TIBCO Business Studio, including:
Topics
• Migrating Processes Created in Previous Versions, page 70

• Creating a Package, page 72
• Copying a Package, page 74
• Creating a Process, page 75
• Creating Data Fields, page 79
• Creating Participants, page 80
• Deleting Data Fields, Parameters, Participants, and Type Declarations, page 82
• Creating Extended Attributes, page 83
• Working With Special Folders, page 86
• Workflow Patterns in Business Processes, page 87
• Reusing Processes, page 94
• Using Throw and Catch Error Events, page 108
• Importing a TIBCO iProcess Modeler Package, page 110
• Source Controlling Processes, page 112
• Emailing Processes, page 114
• Integrating with the TIBCO iProcess Suite, page 115
• Integrating with Aris Software, page 117
• Creating Process Package Documentation, page 121
• Setting the Validation Preferences, page 125

70
| Chapter 3 Tasks
Migrating Processes Created in Previous Versions
Processes created in previous versions of TIBCO Business Studio must be

migrated to the current version before they can be opened. The migration process
is different depending on which version of TIBCO Business Studio you are
migrating from.
Migrating from Version 1.1

To migrate from Version 1.1, do the following:
1. Depending on whether you ar e migrating a workspace or a Package, do the
following:
— To migrate a workspace, select File > Switch Workspace, browse for the
location of the Version 1.1 workspace, and when prompted, restart TIBCO
Business Studio.
— If you want to migrate only one Package, and not an entire workspace,
either copy the Package into the Project Explorer or select File > Import,
expand General, select Existing Projects into the Workspace, and follow
the instructions in the wizard to import the Project.
Whilst the Project folders are present, the Project Explorer displays the
contained XPDL files only, without the standard TIBCO Business Studio
Project Explorer branches such as Process Packages Folders, Data Fields,
and so on.
2. Right-click a Project you want to migrate and select Migrate Project to

Current Version. The icon on the Project in the Project Explorer changes and
the Project Explorer folder is added.
3. In the Problems view for each Package that you migrated, the following error
message is displayed:
Right-click and select Quick Fix. When you have resolved the problems, you
can open the Process in the Process Editor.
You can correct several migration problems at once from the Quick Fix dialog by
clicking Find Similar Problems, selecting them, and clicking OK to apply the fix.
The number of similar problems found depends on the filtering that you have set
up in the Problems view (see Problems View on page 157).

Migrating Processes Created in Previous Versions 71
|
Migrating from Version 2.0

1. Copy the Package containing the Process into a Packages special folder (see
Enabling and Disabling Special Folders on page 86).
2. Either start TIBCO Business Studio, or if it is already open, refresh the Project
Explorer.

72
| Chapter 3 Tasks
Creating a Package
To create a Package, do the following:
You can create a Package and Process as part of creating a Project (see Creating a
Project, Package and Process on page 8).
1. Right-click the Project under which you want to create the Package and select
New > Process Package.
2. If you want to change the Project Packages Folder under which the Package is
created, click Browse.
3. Enter the name of the Package or accept the default filename. The filename
must have .xpdl as the extension. Click Next.
4. The Package Information dialog shows the name of the Package. Either click
Next to accept the defaults or modify these as necessary:
— Package - name of the Package that will be displayed in the Project
Explorer. This does not have to be the same as the filename for the XPDL
package.
— Author - username of the user who created the Package.
— Created - displays the date/time that the Package was created.
— Description - text description of the package.
— Documentation Location - URL or filename of any supporting
documentation.
— Status - project life cycle status for informational purposes. How or
whether you use life cycle statuses is up to you, but they are typically used
as follows:
UNDER_REVISION - for packages in development
UNDER_TEST - for packages in User Acceptance Testing (UAT)
RELEASED - for packages in production
— Business Version - version information about the Package.
The version you specify in this field is unrelated to any source control
system and Business Versions are entirely user-defined.

Creating a Package 73
|
5. Click Finish to create an empty Package, or select the Create a package using
one of the following templates checkbox to create a Process. Select one of the
following templates:
— An empty process - Selecting this option creates a Packages folder and an
empty Process (with no Activities, Events, etc.).
— An empty iProcess process - Selecting this option creates a Packages Folder
with a Process intended for eventual execution in iProcess. The Process has
sw_starter as a Participant and iProcess Engine and iProcess Modeler
selected as Destination Environments.
— A package with a simple process - Selecting this option creates a Package
and a Process with a Start Event, an Activity and an End Event.
— A simple two Pool process - Selecting this option creates a Package and a
Process with two Pools and Message Flow between them.
— A simple workflow process - Selecting this option creates a Packages
Folder with a simple workflow Process intended for eventual execution in
iProcess. The Process has sw_starter as a Participant and iProcess Engine
and iProcess Modeler selected as Destination Environments.
— A simple integration process - Selecting this option creates a Packages
Folder with a simple process for implementing the typical steps of an
integration-style process
— A case working process - Selecting this option creates a Packages Folder
with a simple process for the management of cases.

74
| Chapter 3 Tasks
Copying a Package
You can copy a Package into the same Project, or into a different Project in your
workspace as follows:
1. In the Project Explorer, highlight the Package file you want to copy.
2. Press Ctrl + C to copy the Package.
3. Open the Project into which you want to copy the Package.
4. Press Ctrl + V to paste the Package. If a Package of the same name already
exists in the same Project, you are prompted to enter a new name for the
Package file. If a Package of the same name already exists in a different
Project, you are prompted to overwrite the file.
After copying a Package, errors similar to the following are displayed in the
Problems view:
To correct this, right-click the problem, and select Quick Fix. Accept the
suggested fix for this problem to resolve the duplicate IDs.

Creating a Process 75
|
Creating a Process
To create a Process, do the following:
You can create a Process and its containing Package and Project in one operation
(see Creating a Project, Package and Process on page 8).
1. Before creating a Process, you must create a Project and a Package to contain
your Process.
2. In the Project Explorer, select the Package you created, right-click and select
New Process.
3. The New Process wizard is displayed.
4. If necessary, browse to change the Packages Folder and Package then click
Next.
5. Enter the Name of the Process and click Next.
6. Select the Destination Environment (optional). This controls the validation
that TIBCO Business Studio performs when you save the Process:
— If you select iProcess Engine, the Process will be validated for direct
deployment to the TIBCO iProcess Engine.
— If you select Simulation, the Process will be validated for simulation in
TIBCO Business Studio as well as for BPMN correctness.
— If you select iProcess Modeler, the Process will be validated for future
import into the TIBCO iProcess Modeler as well as for BPMN correctness.
— If you do not select a destination environment, basic BPMN validation will
be performed.
You can change or select the destination environment after the Process has
been completed on the Advanced tab of the Process Properties.
7. Click Next.
8. The Extended Attribute dialog is displayed. This allows you to add any
supplemental information to the XPDL for the Process. For more information
see Extended Attributes on page 57.

76
| Chapter 3 Tasks
Click Add to add a new extended attribute. Modify the following:

— Name - provide a Name for the attribute (you cannot include spaces in the
name).
— Value - add any text for the Value.
— Escape Body - select this check box if you want the parser to interpret the
contents of the attribute.
— Body - enter whatever text or XML you want to make up the body of the
attribute.
9. Click Finish.
10. When you start the Process Editor, you see the following window (the Palette
might be collapsed; if so, click the black arrow to expand it):
You can expand this window to fill your screen by double-clicking the title bar
(in this example, the area labeled MyProcess1).
The Process Editor provides a Pool and Lane that you can rename if you plan
on using Pools and Lanes. You add elements of your business process using
the Palette.

Deleting a Process 77
|
Deleting a Process
To delete a Process:
1. Do one of the following:
— Right-click the Process in the Project Explorer, and select Delete.
— Highlight the Process and select Edit > Delete.
— Highlight the Process and press Delete:
2. If the Process you are deleting is referenced in the parent Package (for
example, you are deleting a Sub-Process), the following dialog is displayed:
— If you are sure that you want to invalidate the Process that is referring the
the Process you are deleting, click Yes.
— If you do not want to delete the Process, click No.
3. If the Process you are deleting is not referenced in the parent Package, it is still
possible that it is referenced by a Process in a different Package. TIBCO
Business Studio cannot validate against this however and the following dialog
is displayed:
— If you are sure that Processes in different Packages do not reference the
Process you are deleting, click Yes.
— If you do not want to delete the Process, click No.

78
| Chapter 3 Tasks
It is also possible to delete a Process by deleting the XPDL file of the Package that
contains the Process in Windows Explorer. This will delete all Processes in that
Package. If you delete a Package while TIBCO Business Studio is open, you must
refresh the Project Explorer to see an updated view of the workspace.

Creating Data Fields 79
|
Creating Data Fields
Data Fields identify the inputs and outputs of an Activity. For example, an
Activity called "Process Student Course Request" could require a form with the
list of courses the student wants to take as input. The availability is checked and a
form that lists the courses they are enrolled in is output.
To create a new Data Field, do the following:
1. In the Project Explorer, expand the Package where you want to add a Data
Field.
2. Right-click Data Fields and select New Data Field. The New Data Field
dialog is displayed.
3. The dialog displays the name of the Project and Package where the Data Field
will be created. If you want to change either, click the Project or Package
button to browse.
Data Fields can be created at either the Package level or at the Process level.
Creating them at the Package level enables them to be shared amongst
Processes. Select the Process checkbox and specify a Process if you want to
create the Data Field at the Process level.
Click Next.
4. Specify the Name, Type, and Initial Value (optional) of the Data Field, select
whether it is an Array, and click Finish.
The Data Field that you created appears in the Project Explorer.

80
| Chapter 3 Tasks
Creating Participants
Participants are used to identify who or what performs an Activity.

To create a new Participant, do the following:
1. In the Project Explorer, expand the Package where you want to add a
Participant.
2. Right-click Participants and select New Participant. The New Participant
dialog is displayed.
3. The dialog displays the name of the Project and Package where the
Participant will be created. If you want to change either, click the Project or
Package button.
Participants can be created at either the Package level or at the Process level.
Creating them at the Package level enables them to be shared amongst
Processes. Select the Process checkbox and specify a Process if you want to
create the Data Field at the Process level.
Click Next.
4. Specify the Name and Type (see Participants on page 59) of the Participant
and click Finish.
The Participant that you created appears in the Project Explorer.
Associating Participants with Activities

By associating a Participant with an Activity you can identify who or what
performs the Activity.
To associate a Participant with an Activity do the following:
1. In the Process Editor, highlight the desired Activity.
2. Either:
— In the Properties view, browse for the desired Participant and click OK.
— Right-click the Activity, select Participant, browse for the Participant and
click OK.
• You can select multiple Participants by pressing either the Ctrl or Shift keys
while making your selection.
• You an also select as a Participant a Data Field of the type Performer.

Creating Participants 81
|
3. The Participants you selected are displayed in the Properties view and also
when you hover the pointer over the Activity in the Process Editor.

82
| Chapter 3 Tasks
Deleting Data Fields, Parameters, Participants, and Type

Declarations
You can delete a Project object such as a Data Field, Parameter, Participant, or
Type Declaration by right-clicking it in the Project Explorer and selecting Delete.
However, if the Project object has been associated with another object such as an
Activity or a Sequence Flow, the following message is displayed:
If you click Yes, the Project object (in this example, a Data Field) is deleted, but it
will still be referenced in XPDL for the Project, which can cause problems. If you
click No, the Project object is not deleted. You can then go to the Properties view
and examine the References to that object:
In this example, the Data Field is referenced in the User Task Notify Supervisor.
Click Go To to show that Task in the Process Editor.

Creating Extended Attributes 83
|
Creating Extended Attributes
Extended attributes can be used to add extra information to the schema such as:
• XML
• Plain text descriptions
• Supply Chain Management (SCM) metrics and best practices
To add extended attributes to an object, do the following:
You can also add extended attributes when creating a new Process as described in
Creating a Process on page 75.
1. Click the Extended tab.
This tab is only available on the Properties view for objects that support extended
attributes.
2. Click Add to add a new extended attribute.

3. Modify the following:
— Name - provide a Name for the attribute (you cannot include spaces in the
name).
— Value - add any text for the Value.
— Escape Body - select this check box if you want the parser to interpret the
contents of the attribute.
— Body - enter whatever text or XML you want to make up the body of
attribute.
4. Save the Package that contains the Process.

84
| Chapter 3 Tasks
Configuring Timer Event Scripts
You can specify that a script is executed for a Start Timer Event or an Intermediate
Timer Event (either inflow or on a Task boundary).
Some Destination Environments do not support Timer Event Scripts.
For example, the following Intermediate Timer Event has been placed on a Task
boundary:
In the Properties view, you can choose a script types from the Script Defined As
list:
Depending on the Destination Environments selected, there can be other script

types in the Script Defined As list (for example, JavaScript for the iProcess
Engine, iProcess Modeler, and Simulation Destination Environment).
Select one of the script types:

• Text - if you want to leave the implementation of the script for the Process
Developer, you can select Text and use this area provided to describe the
desired behavior for the script.
• Constant Period - this allows you to specify the timeout period after the event
is initiated using the following time units. For the iProcess Engine Destination

Configuring Timer Event Scripts 85
|
Environment, this Constant Period that you specify is translated into a

Deadline Expression:
Not all time units are available for all Destination Environments. For example,
Seconds and Micro Seconds are not valid in an iProcess Deadline
specification, so you can specify these units for a Process that will be deployed
to the iProcess Engine.
• JavaScript - this script type is available for the iProcess Engine, Modeler, and
Simulation Destination Environments. It allows you to enter JavaScript
statements in the space provided. For more information, see TIBCO Business
Studio Process Developer’s Guide.

86
| Chapter 3 Tasks
Working With Special Folders
Special Folders are folders in the Project Explorer that are reserved for storing
specific types of Assets. For example, the Process Packages folder is the default
Special Folder for storing Processes and the Packages that contain them.
When you create a Project, you have the option of creating a Special Folder for
each type of Asset that you include in your Project. By doing this, you can utilize
special features of the Project Explorer. For example, enabling a Special Folder for
Business Processes allows you to view the Participants, Data Fields and so on. If
you do not use a special Packages folder, you only see the XPDL file for the
Package in the Project Explorer.
Enabling and Disabling Special Folders

You can disable a Special Folder by highlighting it in the Project Explorer,
right-clicking, and selecting Special Folders > Do not use as SpecialFolderType.
The following example uses the Special Folder for Business Processes as an
example, however the Special Folders for other Asset Types are enabled and
disabled in the same manner.
For example, disable the Packages folder by highlighting the Process Packages
folder in the Project Explorer and selecting Special Folders > Do not use as
Packages Folder, which results in a view of the Package like this:
Alternatively, you can enable the use of the special Packages folder by
highlighting the Packages folder in the Project Explorer and selecting Special
Folders > Use as Packages Folder. This results in a view of the Package like this:

Workflow Patterns in Business Processes 87
|
Workflow Patterns in Business Processes
This section describes some typical workflow patterns1 and how you can
implement them in a TIBCO Business Studio Process.
Forking
It is likely that when creating your Process you want an Activity to lead to two or
more other Activities to be performed in parallel (concurrently). For example,
when a customer order is dispatched, the inventory is updated and an invoice
sent to the customer.
1. Barros, Kiepuszewski, ter Hofstede, van der Aalst

(http://is.tm.tue.nl/research/patterns/)

88
| Chapter 3 Tasks
BPMN uses the term “fork” to refer to the dividing of a path into two or more
parallel paths. In TIBCO Business Studio, there are two ways to create a fork in
the Process, either with two outgoing, uncontrolled Sequence Flows from an
Activity or with a Parallel Gateway:
You specify that a Gateway is Parallel by selecting the Gateway Type on the
Properties view.
These two methods of forking achieve the same result.
Combining Sequence Flow

There are several ways to combine Sequence Flows:
• Joining
• Merging
If the flow should take one or more different paths, Decisions might be required.

|
Joining
Joining represents the merging or synchronizing of two or more parallel paths in
the Process. Use a join for example, if Activity A and B must be completed before
Activity C can begin.
This is achieved in TIBCO Business Studio by using a Parallel Gateway as follows:
You specify that a Gateway is Parallel by selecting the Gateway Type on the
Properties view.
Merging
There are three types of Merge:
• Simple Merge - alternative paths are combined, but only one of the input
Sequence Flows is possible at runtime, so the target Activity is performed only
once.
• Multiple Merge - multiple Sequence Flows are combined, but without any
control on the input to the target Activity (as a result, the target Activity could
be performed more than once).
• Complex Merge - multiple Sequence Flows merge at a Complex Gateway. You
specify a condition in the Gateway that controls which or how many Flows
proceed through the Gateway.

90
| Chapter 3 Tasks
A Simple Merge is accomplished in TIBCO Business Studio like this:
A Multiple Merge looks like this:
The key difference between these two types of merge is that a Simple Merge has
flow control upstream in the Process, so the target Activity (Activity D) is
executed only once. With a Multiple Merge, however, there is no flow control
upstream and the target Activity may be executed more than once.

|
A Complex Merge looks like this:
The condition associated with the Complex Gateway specifies what is required to
pass the Gateway. For example, it could specify that any two of Activities A, B or
C must be completed before proceeding with Activity D. Another alternative
would be for Activity A and either Activity B or C to complete before Activity D
can begin.
Decisions
Decisions points in the Process are achieved with Gateways. There are several
types of decisions:
• Multiple Choice
• Exclusive Choice

92
| Chapter 3 Tasks
Multiple Choice
There are two ways to provide for a multiple choice type decision, either with
conditional Sequence Flows, or with an Inclusive Gateway:
In the previous example, the conditions on the Sequence Flows determine

whether Activity B, C or both are chosen.
When an Inclusive Gateway is used, Boolean conditions on the outgoing

Sequence Flows determine which Activity is chosen.

|
Exclusive Choice
An exclusive choice is represented by using an Exclusive Data-Based Gateway:
In this example, either Activity B or C is chosen, depending on a Boolean

condition associated with each outgoing Sequence Flow.

94
| Chapter 3 Tasks
Reusing Processes
When identifying the Process Components you require for your business process,
it is important to analyze the entire business. One way to do this is by thinking in
terms of the products, services and resources (by considering the specifications
for each).
To facilitate the re-use of Process Components, an Activity (or several Activities)
can call another Process as an Independent Sub-Process. The Independent
Sub-Process could be a Process that you have already created, or you can refactor
Activities in your current Process into an Independent Sub-Process (see
Refactoring Sub-Processes on page 97).
If the main Process is imported into the TIBCO iProcess Modeler, any
Sub-Processes are imported as sub-procedures.
Independent Sub-Processes
To call an Independent Sub-Process, do the following:
You can also create an Independent Sub-Process from objects in your Process by
refactoring (see Refactoring Sub-Processes on page 97)
1. In the Process Editor, select the Independent Sub-Process tool.

2. Click in the Process where you want to place the Activity that calls the
Sub-Process.
3. On the Properties view for the Activity, browse for the Process you want to
call as a Sub-Process.
Example
The following example demonstrates how a top-level Process could use
Sub-Processes in an insurance environment:

Reusing Processes 95
|
This is the top-level Process. Because of its Destination Environment setting, this
Process is not executed in the TIBCO iProcess Engine. The Destination
Environment is set when creating a Process or in the Properties view of the
Process.
Each of the Activities in the Process call Sub-Processes that are executed in the
TIBCO iProcess Engine (its Destination Environment). For example, the
Sub-Process called from the Claims Management Activity could look like this:
This Sub-Process is executed in the TIBCO iProcess Engine, and calls other
Sub-Processes. Note the following about this Sub-Process:
• The Validate Policy Sub-Process can be re-used. For example, when a
customer calls to renew their policy, the first step of the Renewal Process
could be to confirm that they have an existing policy. The Validate Policy
Activity could be re-used for this purpose in the Renewal Process.
• The Process Claimant Activity has a Loop Activity Marker, that indicates that
the Activity is repeated for each Claimant.
• The actual Sub-Process called by the Assess Liability Activity is a manual
Process. However, the to be Sub-Process (planned for the future), could be
implemented as an automatic Process that consists of a series of questions
used to determine liability. Simulation could be used to demonstrate the
performance and cost-savings of migrating the Assess Liability Activity to an
automatic Process.

96
| Chapter 3 Tasks
Expanding a Sub-Process
An Activity that calls a Sub-Process looks like this:
To expand the Sub-Process associated with this Activity, do the following:

1. In the Process Editor, select the Activity that calls the Sub-Process.
2. In the Properties view, select the General tab.
3. Click Open Sub-Process:
4. The Sub-Process opens in the Process Editor.
Embedded Sub-Processes
An Embedded Sub-Process is one that is fully contained within the parent
Process; it does not exist as a separate Process:
In this example, Run Credit Check is an embedded Sub-Process. This implies that
running a credit check is an activity that is not needed by other Processes. If you
subsequently decide that you want to be able to run a credit check from within
other Processes, you can expose the Embedded Sub-Process as an Independent
Sub-Process by refactoring it. See Refactoring Sub-Processes.
To create an embedded Sub-Process, do the following:

|
Refactoring Sub-Processes
Refactoring a Sub-Process allows you to do the following:
• Create a new Embedded Sub-Process from selected objects.
• Create a new Independent Sub-Process from selected objects and replace the
selected objects with a call to the newly created Sub-Process.
• Convert an existing Embedded Sub-Process (and its contents) into an
Independent Sub-Process and replace it with a call to the newly created
Sub-Process.
Creating a New Embedded Sub-Process

To create a new Embedded Sub-Process from objects in your Process, do the
following:
1. Select the objects that you want to put in the Embedded Sub-Process. For
example:
2. Right-click and select Refactor > Move into New Embedded Sub-Process.

98
| Chapter 3 Tasks

— Enter a name for the Embedded Sub-Process that you want to create.
— Select the New Sub-Process is a transaction checkbox if you want the new
Sub-Process to become a transaction and therefore be under transaction
control (see Transactions on page 47).
— Select the Insert start event in new sub-process and Insert end event in
new sub-process checkboxes to control whether Start and End events are
added to the refactored Sub-Process.
4. Click Finish. The objects that you selected are placed within a new Embedded
Sub-Process (with Start and End events if those options were selected):

|
Creating a New Independent Sub-Process

To create a new Independent Sub-Process from objects in your Process, do the
following:
1. Select the objects that you want to put in the Independent Sub-Process. For
example:
In this example, the User Task has the following Parameters (two Data Fields
and one Formal Parameter):
2. Right-click and select Refactor > Extract into New Independent Sub-Process.

100
| Chapter 3 Tasks
3. Because the Data Fields are only referenced in this Activity (and not used by
any other Activities), the following message is displayed:
— If you select the Data Fields, they are moved into the Sub-Process.
— If you do not select the Data Fields, they are created as Formal Parameters
in the Sub-Process (and mapped to those Formal Parameters). For more
information, see Data Fields and Participants on page 104.

|

— Enter a name for the Independent Sub-Process that you want to create.
— Select the New Sub-Process is a transaction checkbox if you want the new
Sub-Process to become a transaction and therefore be under transaction
control (see Transactions on page 47).
— Select the Insert start event in new sub-process and Insert end event in
new sub-process checkboxes to control whether Start and End events are
added to the refactored Sub-Process.
5. Click Finish. The objects that you selected are copied to the new Sub-Process
and the selected objects are replaced with a Task that calls the Independent
Sub-Process.
If you chose to create Formal Parameters for the Data Fields, you can see them
in the Project Explorer, under the Sub-Process:
In addition, if you click Task in the parent Process that calls the Sub-Process
and go to the Properties view, you can see the mappings that have been
created between Data Fields and Formal Parameters of the parent Process and
the Formal Parameters created in the Sub-Process:
Notes on Refactoring Objects into Independent Sub-Processes

Note the following when refactoring Objects into Independent Sub-Processes:

102
| Chapter 3 Tasks
• Formal Parameters in the parent Process are created as Formal Parameters in

the Sub-Process.
• If a Data Field is referenced only in the selection that you are refactoring, you
have the option of moving or copying it (see Data Fields and Participants on
page 104). Data Fields that are copied into the Sub-Process are created as
Formal Parameters. Data Fields that are moved into the Sub-Process are created
as Data Fields.
• A mapping is created between Data Fields and Formal Parameters of the
Sub-Process and any corresponding Formal Parameters that are created in the
Sub-Process. You can view this mapping by selecting the Task that calls the
Sub-Process and clicking the Mapping In and Mapping Out tabs in the
Properties view.
Changes in Process Logic

When refactoring objects into an Independent Sub-Process, you can potentially
change the logic of the Process flow. Consider the following Process:

|
In this Process, flow Proceeds from User Task 1 to the Gateway without
necessarily waiting for Task A to finish. If User Task 1 and Task A are refactored
into an Independent Sub-Process, an End Event is inserted into the Sub-Process,
effectively synchronizing the flow. TIBCO Business Studio prompts you to
confirm this change to the Process:

104
| Chapter 3 Tasks
Data Fields and Participants

If a Participant or Data Field is only associated with the selected object, TIBCO
Business Studio gives you the option of either moving this Participant into the
Independent Sub-Process, or duplicating the Participant in both the parent
Process and the Sub-Process:
Using Process Fragments

Rather than reusing an entire process, you can use the Diagram Fragments view
to quickly create new Processes. TIBCO Business Studio provides some
predefined BPMN process fragments and you can also create your own process
fragments. For example, there may be process patterns that you frequently use. By
storing these patterns or "fragments" you can easily use them to construct new
Processes.

|
Using the Predefined Fragments

TIBCO Business Studio provides predefined Fragments in the folder BPMN
Process Fragments. For example, Basic Fragments contains simple fragments
such as an Embedded Sub-Process, Conditional Split, and Task Sequence.
External Systems contains more complex fragments such as a Service Process
Template.
To use one of the predefined Fragments, do the following:
1. Open the Process.
3. In the Diagram Fragments view, there is a treeview that looks similar to the
Project Explorer. This is the Fragment Explorer. Expand BPMN Process
Fragments folder. This contains Categories of BPMN Process Fragments.
4. Expand the Category that contains the Fragment you want to use.
5. Select the Fragment.
6. Drag the Fragment onto the Process.
You can also use the Copy and Paste menu options either by right-clicking or by
selecting from the Edit menu.
Creating Custom Fragments

If a portion of your Process is one that you are likely to reuse in other Processes,
you can capture the useful part of the Process and save it as a Custom Fragment
as follows:
1. Create a new Category by either right-clicking a folder in the Fragment
Explorer and selecting New > New Fragment Category or by clicking the
Create Custom Fragment Category button ( ).
2. Click in the name field of the newly added Category and enter a name:
3. Holding down the Ctrl key, select the Activities and Sequence Flows in the
Process that comprise the Fragment.

106
| Chapter 3 Tasks
4. Press Ctrl and drag the selection into the Diagram Fragments view or copy
and paste it into the view:
The Fragment that you created is stored in that Category and can be used to create
new Processes.
You can drag Fragments and drop them into other Categories.
How Projects, Packages and Processes Support Reuse

• Project - The container for all project life cycle artifacts.
• Packages - A mandatory container for Processes and their infrastructure
(Participants and Data Fields). Can be organized along project or
departmental lines, depending on business requirements.
• Processes - model actual and future business processes in your organization.
Processes can be shared between Packages so libraries of process components
can be created and reused.
Example
The following example shows a Project and the associated Packages and
Processes used in an insurance environment.

|
In this example, the Validate Policy Process might call a Sub-Process in another
Package (for example, the Search Claim History Process). This Sub-Process is in
the same Project in this example, but it could be located in a different Project.

108
| Chapter 3 Tasks
Using Throw and Catch Error Events
In BPMN, when an event of any type on the boundary of a Task fires, the Task is
cancelled and the exception flow from that event is followed. For example:
In this example, if the Message Event is fired, the Task to which it is attached is
cancelled and the Sequence Flow to Task 2 is followed.
With a Throw/Catch Error Event pair, an inflow Error Event "throws" or fires the
error, and if there is an active Task with an Error Event on the Task boundary, that
event "catches" the error, cancelling the Task and following the exception flow. For
example:

Using Throw and Catch Error Events 109
|
In this example, if the default flow for the XOR Gateway is taken, the inflow Error
Event throws an error. If the Task with the Error Event on its boundary is active, it
will catch the error, cancel the Task and proceed with Task 2.
A Throw and Catch Error Event pair functions like a Withdraw Link in an
iProcess procedure.
You can also specify an error code with either a Throw or Catch Error Event:
• If a Catch Error Event has no error code specified, it catches any thrown Error
Events in the Process (while the Task it is attached to is active).
• If a Catch Error Event has an error code specified, it only catches Error Events
that throw that error code.
• A Throw Error Event in a Process that is being exported to the iProcess
Modeler or deployed to the iProcess Engine must specify an error code.
When you specify error codes in the Properties view for Error Events, you can use
content assist. This means for example, that if you have entered ERROR1 for a
Throw Error Event, when you specify the error code for the Catch Error Event
you can press Ctrl + Space and the available error codes are displayed from
which you can select one.
An Error End Event functions just like any other inflow Error Event, except that
when one fires, if there are more Tasks that need to complete as the result of
exception flow, the outstanding Tasks complete; if there are no more Tasks that
need to be completed, the Process ends.

110
| Chapter 3 Tasks
Importing a TIBCO iProcess Modeler Package
Processes and the Packages that contain them are stored in XPDL format. This
section describes how to import a TIBCO iProcess Modeler XPDL Package.
Restrictions
The procedure described in this section is only for importing a TIBCO iProcess
Modeler XPDL Package that was created in TIBCO iProcess Modeler. You cannot
use the Import menu option to do the following:
• Import TIBCO Business Studio XPDL files created using previous versions of
TIBCO Business Studio. To use them with the current version of TIBCO
Business Studio, manually copy the Package into your workspace and migrate
the Processes as described in Migrating Processes Created in Previous
Versions on page 70.
• You cannot import XPDL files that were created using the TIBCO Business
Studio Export > TIBCO iProcess Modeler XPDL option. Only iProcess
Modeler XPDL files exported from the TIBCO iProcess Modeler can be
imported.
When you import a TIBCO iProcess Modeler XPDL file into TIBCO Business
Studio, only the basic Analyst features of the Process are imported, and some
Implementation details may be lost.
Procedure
The easiest way to import a Process and the Package that contains it is by
dragging the XPDL file of the package onto the desired location in the Project
Explorer View. Alternatively, you can do the following:
1. Select File > Import.
2. In the Import dialog, select TIBCO iProcess Modeler Analyst process and
click Next.

Importing a TIBCO iProcess Modeler Package 111
|
3. Enter the following:

a. Click Browse to select the From Directory where the XPDL file you want
to import is located.
b. Click Browse to select the Into folder where you want the imported
package to be placed.
c. Select Overwrite existing resources without warning if you want to
automatically overwrite any existing Packages or Processes with the same
name.
d. Click Finish.
4. The Package/Processes that you have imported are shown in the Project
Explorer.

112
| Chapter 3 Tasks
Source Controlling Processes
One problem that occurs when dealing with Processes across their normal life
cycle (from creation, testing, rollout to maintenance) is how to know that a given
Process created by the Analyst, elaborated by the Process Developer and signed
off by the process owner is exactly the one that is in use in a given environment
(for example, a development, user-acceptance or production environment).
Particularly in large/complex projects where data is shared or modified by
several people, a source control system becomes necessary. Most enterprises have
one or more products for Source Configuration Management (SCM). This may be
a commercial product such as Perforce, Rational's Clearcase or an open source
solution such as:
• Concurrent Versions System (CVS) (http://www.nongnu.org/cvs/) or
• Subversion (http://subclipse.tigris.org/).
TIBCO does not provide its own SCM product, preferring to integrate with the
Enterprise's choice for SCM. The Eclipse feature for integrating with such an SCM
product is known as the Team Synchronization (see the Eclipse help). Since
Eclipse provides CVS by default, the following section describes how to use
Subversion; you should contact your SCM vendor for commercial plug-ins.
SCM is one part of Application Lifecycle Management (ALM) dealing only with
the preservation of revisions of software at different times, not the editorial and
approval processes that drive those different revisions.
Using Subversion with TIBCO Business Studio

This section describes how to use Subclipse for source control. Subclipse is an
Eclipse plug-in that adds Subversion integration to the Eclipse environment, and
is bundled with TIBCO Business Studio.
This section assumes that you or your Subversion administrator have installed an
SVN server (see http://subversion.tigris.org/) or that you are using the version
bundled with TIBCO Business Studio (Asset Central).
Right-click an existing project that contains items you wish to source control.
Select Team > Share Project. Obtain the URL for the Repository Location from
your Subversion administrator.

Source Controlling Processes 113
|
Creating a Project from an Existing Project in Source Control

1. Select File > Import. The Import wizard is displayed.
2. Select Checkout projects from SVN and click Next.
3. Set up the repository with the assistance of your Subversion administrator,
(this should point to the parent directory to the one containing the Project
folder) and click Next.
4. Select the Project folder and click Next.
5. Select the method for checking out the Project and click Next.
6. Either use the default workspace or click Browse to check out the Project
elsewhere.
7. Click Finish. The Project is checked out to your workspace.
Browsing SVN Repositories

You can browse SVN repositories as follows:
1. Select Window > Open Perspective > Other.
2. Select SVN Repository Exploring.
3. This opens a perspective from which you can browse SVN repositories. For
example:
Deleting Projects from SVN Repositories with Asset Central

If you are using Asset Central and want to delete a Project that you have put in
Subversion, it may appear that you have deleted the Project using Asset Central,
however it remains in the Subversion repository until you delete it using another
tool such as TortoiseSVN, the command line interface to Subversion, or a
web-based tool.

114
| Chapter 3 Tasks
Emailing Processes
The XPDL package files and the processes contained within can be sent using
email.
To send a Process:
1. In the Project Explorer, find the name of the package that contains the process
you want to send.
2. Right-click the Package and select Properties from the context menu. The
resulting dialog displays the Location of the Package.
3. Navigate to the indicated directory.
The default workspace location is C:\Documents and

Settings\username\workspace. However, you may have selected an
alternate location when you first started TIBCO Business Studio.
4. Drag and drop the Package directly onto your email message or otherwise
attach it (for example by pasting the Location value identified earlier).
If you receive a Process:

There are three different ways to get a Process into TIBCO Business Studio:
• Save the attachment directly into your workspace and refresh the Project
Explorer.
Be careful of overwriting existing Packages with the same name.
• Save the attachment to a file. In Windows Explorer press Ctrl+C to copy it,
return to TIBCO Business Studio, and press Ctrl+V to paste it into the Project
Explorer.
• Drag the package from Windows Explorer into the appropriate Project in the
Navigator view in TIBCO Business Studio. When you return to the Project
Explorer view you can see the Package and its processes.

Integrating with the TIBCO iProcess Suite 115
|
Integrating with the TIBCO iProcess Suite
If after modeling your business process, you plan to execute it in the TIBCO
iProcess Engine, you must perform the following steps:
• Correct any Validation Errors
• Export the Process from TIBCO Business Studio
• Import the Process into the TIBCO iProcess Client
It is also possible to deploy a Process from TIBCO Business Studio directly to the
TIBCO iProcess Engine. For more information, see the TIBCO Business Studio
Process Developer’s Guide.
Task A Correct any Validation Errors

1. Go to the Properties View for the Process and click the Advanced tab.
2. Select the TIBCO iProcess Modeler as the Destination Environment.
3. Save the Package you want to export.
The Process is validated for potential import into the TIBCO iProcess Modeler
and any errors are reported in the To see this view, select Window > Show
View > Project Explorer.. For more information about the validation that is
performed, see Process Validation on page 144.
To correct a problem do one of the following:
— Right-click the problem and select Quick Fix (if enabled for the current
problem). This gives you the option of having TIBCO Business Studio
automatically correct the problem for you.
— Double-click the problem or right-click the problem and select Go To. This
displays the Process in the Process Editor, highlighting the offending object
and allowing you to manually correct the problem.
Task B Export the Process from TIBCO Business Studio

TIBCO Business Studio can export Packages/Processes in XPDL format which
can be read by the TIBCO iProcess Modeler.
To export a Process, do the following:
1. Select the Packages you want to export.
2. Select File > Export. The Export dialog is displayed.

116
| Chapter 3 Tasks
3. Expand Business Process Management and select TIBCO iProcess Modeler

XPDL and click Next.
4. Change your package selection if required.
5. Select a destination for the export by either:
— Selecting Project (to put the export in the Exports\iProcess Modeler XPDL
sub-directory within your Project directory), or
— Selecting Path: and clicking Browse... to specify a directory for the export.
6. Click Finish.
Task C Import the Process into the TIBCO iProcess Client

Import your TIBCO Business Studio Process as you would any other Process (see
the TIBCO iProcess Modeler: Procedure Management Guide for more information).
See Object Mappings - TIBCO iProcess Modeler on page 145 for information
about how the TIBCO Business Studio objects are mapped into TIBCO iProcess
objects.
Open the Process in the TIBCO iProcess Modeler and complete its detailed
implementation. Then execute and test the Process.

Integrating with Aris Software 117
|
Integrating with Aris Software
You can import processes created with Aris 6.2 or 7.0 software into TIBCO
Business Studio. First, you must use the XML Export Wizard in Aris to create an
XML file. Then use the Import Wizard in TIBCO Business Studio to import the
XML into TIBCO Business Studio.
• Only eEPC (Extended event-driven process chain) type processes and

associated FADs (Function Allocation Diagrams) created using the Aris
Toolset can be imported.
• Regardless of whether you have selected processes from several different
groups in Aris, they are imported under one Package in TIBCO Business
Studio.
For more information, see Object Mappings - Aris Software on page 150.
Creating Custom Symbols in Aris (Optional)

You can create custom symbols in Aris processes that you want to export. For
example, you can specify that a certain type of Aris object displays a graphic of
your choice rather than the default graphic.
1. Log in to the Aris database that contains the data you want to export.
2. Expand Configuration and click Method.
3. Click the Symbols tab.
4. Right-click the object for which you want to specify a different symbol and
select New > Symbol.
5. Browse to select a graphic of the type AMF, WMF, or EMF.
6. Click Next and change the Name of the object if desired.
7. After you have created the object, log out of the database.
8. Choose Configuration > Update Configuration.
9. Log in to the Aris database.
Using Custom Symbols in TIBCO Business Studio

If you have created custom symbols in Aris, you must perform the configuration
described in this section before you can use those symbols with Aris processes
that you import.

118
| Chapter 3 Tasks
1. Navigate to the \LocalServer\sysconfig subdirectory of the Aris installation

directory.
2. Open the methodextension.cpf file. This file contains a universal ID (Guid)
for each custom symbol that you have defined. For example:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<SCSMethodExtension version="1" >
<UserDefName KindNum="1" ItemTypeNum="66218" LocaleId="1033"
Name="Actor (sample)"/>
<MetaFile Guid="da459755-894d-4a86-86bb-66624fde7434"
NewSN="65549" RefSN="13" size="12036" Amf="false"/>
<MetaFile Guid="b783fa5d-a484-46f6-a357-b848ef6e328c"
<MetaFile Guid="9616e674-0dcb-40ac-b370-e7bc28271949"
</SCSMethodExtension>
The Guids listed in the file correspond to graphics files located in the same
directory.
3. Locate the graphics files listed in the methodextension.cpf file and copy them
to a temporary directory.
4. Rename the graphics files to .emf or .wmf file extensions.
5. Open each image and save it to Portable Network Graphics (PNG) format.
6. In TIBCO Business Studio, create a folder called images in the Project into
which you will import the Aris Process.
7. Copy the PNG versions of the graphics into the images folder.
8. Export the Aris process and then import it into TIBCO Business Studio as
described in this chapter. The custom symbols you created in Aris should be
displayed in TIBCO Business Studio.
If the symbol does not display correctly, click the Data Object and check that
the file specified for External References is correct.
Exporting from Aris
Pre-Export Tasks
If any of the Processes or groups of Processes that you want to export contain
FADs, do the following:
2. Open the main process.

Integrating with Aris Software 119
|
3. Select the function type that contains the FAD.

4. Right-click and choose Select > Select All Objects of the ’Function’ Type.
5. Right-click the selection and select Assignments > Show.
6. Save the process and perform the export as described in the following section.
Performing the Export

To export the Aris data, do the following:
2. Highlight the group or Business Processes that you want to export.
3. Right-click and select Export/Import > XML Export. The Select Attribute
Language dialog is displayed.
4. Select the language and click Next. The Select Export File dialog is displayed.
5. Browse for the location for the Export.
6. Click Finish to complete the export.
Importing Aris into TIBCO Business Studio

To import an Aris XML file into TIBCO Business Studio, do the following:
1. Select File > Import. The Import Wizard is displayed.
2. Select ARIS XML and click Next.
3. Browse for the Directory where the Aris XML file is located.
4. Browse for the Project folder into which you want to import the ARIS XML
file and click Finish to complete the import.

120
| Chapter 3 Tasks
Example
In Aris Version 6.2, in the Demo62 database, there are several examples of eEPC
processes. The following example shows the TIBCO Business Studio import of the
Aris example process Ticket Reservation (in Movie Palace > Business processes
> Customer service >Ticket reservation).

Creating Process Package Documentation 121
|
Creating Process Package Documentation
From within TIBCO Business Studio you can export information about your
Process and the Package that contains it to an HTML file. This is similar to the
procedure documentation that is generated in iProcess Modeler. You can also use
the command line to create Process documentation.
From Within TIBCO Business Studio

To export documentation about your Process:
1. Select File > Export.
2. Expand Business Process Management and select Process Package
Documentation and click Next.
3. Select the Package or Process you wish to export. If you select a Process, the
containing Package is exported as well.
4. Select a destination for the export by either:
— Selecting Project (to put the export in the \Exports\Process
Documentation sub-directory within your Project directory), or
— Selecting Path: and clicking Browse... to specific a directory for the export.

122
| Chapter 3 Tasks
5. Click Next. The Process Documentation Options dialog is displayed.
6. Select the elements of the Process that you want to include in the generated
Process Documentation. When you have finished customizing the Process
Documentation, click Finish.
7. The Process Documentation is saved to the location you specified. See
Viewing Process Package Documentation for more information.
From the Command Line

To create Process Package documentation from the command line, do the
following:
1. Navigate to the directory that contains the TIBCO Business Studio executable
file. For example:
C:\Program Files\TIBCO\BusinessStudio
2. Enter a command in the following format:

TIBCOBusinessStudio.exe -application
com.tibco.xpd.procdoc.rcp.document -nosplash

Creating Process Package Documentation 123
|
[-data <workspace>] [-<contentoption1> on | off
-<contentoption2> on | off...] <XPDLpath\file> <HTMLpath\file>
Where:
— <workspace> is the path to the workspace where the Process Package from
which you want to generate the Process documentation is located. This
parameter is optional.
— <XPDLpath\file> is the location of the XPDL package file from which you
want to create the Process documentation. If you specified a workspace,
this parameter can specify either the full path or the relative path from the
workspace. If you did not specify a workspace, this parameter must specify
the full path to the XPDL file. If there are spaces in the path, you must
enclose the path within quotes ("").
— <HTMLpath\file> should be the full absolute path, including the .html
extension, of the file to which the HTML will be written. Supporting image
files and the stylesheet will also be created in the same folder as the HTML
file. If there are spaces in the path, you must enclose the path within quotes
("").
— <contentoption> allows you to specify options that control the content of
the generated HTML. You can specify any of the following options. Each
must be set to either on or off.
-all - This option switches all options on or off hence, if used, should appear
before all other options. This is useful for example if you want to start with
either a minimum or maximum set of options and then add or subtract
options with subsequent parameters.
-ShowProcessImages
-ShowParticipants
-ShowTypeDeclarations
-ShowDataFields
-ShowFormalParameters
-ShowFlows
-ShowImplementations
-ShowExtendedAttributes
Examples
The following command exports the default Process Package documentation:
com.tibco.xpd.procdoc.rcp.document -nosplash

124
| Chapter 3 Tasks
-data "C:\Documents and Settings\jones\workspace"

"Project\Process Packages\ProcessPackage.xpdl"
C:\reports\ProcessReport.html
The following command exports the most basic information possible (-all off) as
well as Process images and Sequence Flow details:
com.tibco.xpd.procdoc.rcp.document
-data c:\workspaces\myWorkspace -all off -ShowProcessImages on
-ShowFlows on "MyProject/Process Packages/ProcessPackage.xpdl"
"c:\temp\MyProcDoc\ProcessPackage.html"
The following command exports the most detailed information possible (-all on)
except for Process images and extended attributes:
com.tibco.xpd.procdoc.rcp.document -data
c:\workspaces\myWorkspace -all on -ShowProcessImages off
-ExtendedAttributes off "MyProject/Process
Packages/ProcessPackage.xpdl"
"c:\temp\MyProcDoc\ProcessPackage.html"
Viewing Process Package Documentation

To view Process Package documentation:
1. Export the documentation as described in Creating Process Package
Documentation.
2. If you created the Process Package documentation from within TIBCO
Business Studio:
— In the Project Explorer, expand Exports > Process Package
Documentation.
— Right-click the HTML file for the package and select Open With > Web
Browser.
If you created the Process Package documentation from the command line:
— Navigate to the directory where you created the HTML file and open it in
a web browser.
— If you created the HTML file in a directory in your workspace, you can
refresh the Project Explorer, right-click the HTML file for the package and
select Open With > Web Browser.
3. Note that the sections of the Process Package documentation are hyperlinked
as well as the image of the Process (for example, clicking a Task displays the
section that describes that Task).

Setting the Validation Preferences 125
|
Setting the Validation Preferences
You can customize the validation that is performed in the Process Editor.
Specifically, for each validation error you can specify its severity level as Error,
Warning, Info, or Ignore. To customize the Process Editor validation, do the
following:
1. Select Window > Preferences.
2. Expand Process Editor and select Errors/Warnings. The following dialog is
displayed:
3. If you want to change the severity level for a Process Editor problem, select
from the drop-down list. When you have finished, click Apply to effect any
changes you have made.
You can downgrade the severity of BPMN errors, however you cannot
downgrade TIBCO Business Studio errors (for example iProcess Engine
validation errors) because they are not displayed in this dialog.

126
| Chapter 3 Tasks
— Click Yes to revalidate your workspace. Depending on the size of the

workspace and the number of errors, there is a delay while the revalidation
occurs.
— Click No to revalidate your workspace later. The revalidation will take
place when the concept file next changes or is saved, or when you explicitly
request a rebuild of the project or workspace.
— Click Cancel if you do not wish to apply your changes.
At the top of the dialog there is a drop-down list that allows you to select either
BPMN or Simulation. For more information about customizing the simulation
validation, see TIBCO Business Studio Simulation User’s Guide.

| 127
Chapter 4 Reference
This section of the help describes the major parts of the TIBCO Business Studio
user interface, including the perspectives and views that are provided.
Topics
• Overview, page 128

• The TIBCO Business Studio Modeling Perspective, page 129
• Process Validation, page 144

128
| Chapter 4 Reference
Overview
These are some of the main components of TIBCO Business Studio:

Project Explorer view
Process Editor Buttons to quickly switch
perspectives
Palette
Outline view Properties view of the current object (for Context help - available by pressing F1
example, Activity)

The TIBCO Business Studio Modeling Perspective 129
|
The TIBCO Business Studio Modeling Perspective
In Eclipse, a Perspective includes the views and set of editors that you commonly
use for a specific type of work. TIBCO has created several TIBCO Business Studio
perspectives that include the views and editors you commonly use when creating
business processes. The Modeling Perspective includes the following:
• Project Explorer View
• Problems View
• Outline View
• Diagram Fragments View
• Properties View
• Cheat Sheets View
Project Explorer View

This shows a view of the Project in which you can view the Packages and Assets
such as Services. In contrast to the Navigator view (available within the Resource
Perspective) the Project Explorer view shows a contextual view of the Project.

130
For example, the following shows both the Navigator and Project Explorer views
of the same Project.
To see this view, select Window > Show View > Project Explorer.
Problems View
The Problems view is where the software displays warnings, errors and messages
about the resources used in your Project. To see this view, select Window > Show
View > Problems.
The Problems view also displays error messages that result from validation of
your Process. When you save your Process, it is validated for BPMN correctness
and for export to the TIBCO iProcess Modeler or for simulation (depending on the
Destination Environment setting of the Process).

|
To correct a problem do one of the following:

— Right-click the problem and select Quick Fix (if enabled for the current
problem). This gives you the option of having TIBCO Business Studio
automatically correct the problem for you.
You can correct several problems at once from the Quick Fix dialog by
clicking Find Similar Problems, selecting them, and clicking OK to apply
the fix. The number of similar problems found depends on the filtering that
you have set up in the Problems view (see Problems View on page 157).
— Double-click the problem or right-click the problem and select Go To. This
Example
Outline View
The Outline View allows you to focus on specific areas of a large process. The
Outline View looks like this:

132
Area of the Process

that is shown in the Remainder of Process
Process Editor. (not visible in the
Process Editor).
To see this view, select Window > Show View > Outline. By positioning the
mouse pointer over the shaded area and holding the left mouse button down, you
can reposition the shaded area of the Outline View and thus see different parts of
the process.

|
Diagram Fragments View

The Diagram Fragments view allows you to store selected objects from your
Process and reuse them in a different Process. You can also select predefined
Process Fragments and use them in your Process:
Category Buttons for working with

Fragments
Fragment Explorer Fragment
To see this view, select Window > Show View > Diagram Fragments. The buttons
in the upper right of the view allow you to do the following:
- Copy a Diagram Fragment to the clipboard in preparation for pasting it

onto a Process.
- Edit Fragment/Category properties such as the Name and Description.
- Create a Custom Fragment Category in which to store your Fragments.
- Paste a Fragment from clipboard into the Diagram Fragments view or into
the Process.
- Delete a Fragment or Category.
Properties View
The Properties View shows you detailed information about the currently selected
object and allows you to specify the characteristics of an object.

134
The Business Process Modeling Notation (BPMN) complete set is supported by

the Properties View. For example, if you are creating a Gateway in your process
diagram, you can select the type of Gateway you want in the Properties View:
To see this view, select Window > Show View > Properties. To view property
information, you must have an object selected.
Properties related to simulation are only present when Simulation is selected as

the Destination Environment. For more information see the TIBCO Business
Studio Simulation User’s Guide.
Properties related to the implementation of a Process (for example, the Mapping
In and Mapping Out tabs for Service Tasks) are described in the TIBCO Business
Process Properties
When you have selected a Process in the Project Explorer, the following Properties
are available.
Tab Property Description

General Name Name of the Process. You can re-name the
Process here by entering a new name.
Used By Lists any Processes or Tasks that use the

selected Process. For example, if you select
an Independent Sub-Process the Process and
Task that use the Independent Sub-Process
are displayed. Click Go To to display the
referencing object. This field helps prevent
deleting a Process that is used in another.
Note, however that a Process may be used by
other Packages, and these references cannot
be displayed in this field.

|

Destination Enter the target environment for the Process.
When you save the Process, validation is
performed according to this setting:
• If you select iProcess Engine, the Process
will be validated for direct deployment
to the TIBCO iProcess Engine.
• If you select Simulation, the Process will
be validated for simulation in TIBCO
Business Studio as well as for BPMN
correctness.
• If you select iProcess Modeler, the
Process will be validated for future
import into the TIBCO iProcess Modeler
as well as for BPMN correctness.
• If you do not select a destination
environment, basic BPMN validation
will be performed.
Extended Extended attributes can be used to add extra

information to the schema. Click Add to add
a new extended attribute.
Modify the following:
• Name - provide a Name for the attribute
(you cannot include spaces in the name).
• Value - add any text for the Value.
• Escape Body - select this check box if you
want the parser to interpret the contents
of the attribute.
• Body - enter whatever text or XML you
want to make up the body of attribute.

136
Activity Properties
When you have selected an Activity in the Process Editor, the following
Properties are available:

General Name Name of the Activity.
Activity Markers Select from Multiple, Loop, or

Ad-hoc. For more information, see
Activity Markers on page 47.
Participant Specify the Participant responsible

for this Activity (see Participants
on page 59).
Activity Type For example, Task, User Task,

Service Task, and so on. (see
Activities on page 42). If you select
Independent Sub-Process, you
must browse to locate the
Sub-Process.
Referenced Task Shows the name of the Task that is

referenced from the currently
(Activities of type
selected Task. Click Reveal to
Reference Task)
highlight in the Process Editor the
Task to which the current task
refers. Click Back to show the
referring Task.
Is a transaction Select the New Sub-Process is a

transaction checkbox if you want
(Activities of type
the new Sub-Process to become a
Independent or
transaction and therefore be under
Embedded
transaction control (see
Sub-Process)
Transactions on page 47).
Sub-Process Sub-Process location is populated

location with the path to the Sub-Process
name that you select.
(Activities of type
Independent
Sub-Process)

|

Sub-Process name Browse to select the Sub-Process
name.
(Activities of type
Independent
Sub-Process)
Parameters (User Inbound Allows you to select the Data

Task only) Parameter, Fields or Parameters that the Task
Outbound requires as input.
Parameter
Note that Inbound and Outbound
Parameters are from the
perspective of the form, not the user.
This means that Inbound
Parameters are sent to the form by
the Process, not the user. Outbound
Parameters are sent to the form by
the user. For more information, see
the TIBCO Business Studio Process
Mapping In Use this section to create a

mapping from an actual parameter
(Activities of type
(Data Field or Parameter) into the
Independent
formal parameters of the
Sub-Process)
Independent Sub-Process. Create a
mapping by clicking a Parameter,
dragging to the destination
Parameter, then releasing the
mouse button.
Mapping Out Use this section to create a

mapping from a formal parameter
(Activities of type
of an Independent Sub-Process to
Independent
an actual parameter (Data Field or
Sub-Process)
Parameter). Create a mapping
clicking a Parameter, dragging to
the destination Parameter, then
releasing the mouse button.

138

Appearance Line Color Click the button next to Color to
select the line color for the border
of the selected Activity. Click Set
As Default For Type to apply your
current color settings to any new
Activities of that type that you
place on the Process. You can revert
to the default color settings by
clicking Restore Factory Settings.
Fill Color Click the button next to Color to

select the fill color for the selected
Activity. Click Set As Default For
Type to apply your current color
settings to any new Activities of
that type that you place on the
Process. You can revert to the
default color settings by clicking
Restore Factory Settings.
Description Optional textual description of the

Activity.
Extended See the description of the Extended

tab for the Process Properties on
page 134.
Gateway Properties
When you have selected a Gateway in the Process Editor, the following Properties
are available:

General Name Name associated with the
Gateway.
Gateway type Choose the type of Gateway

(see Gateways on page 51 for
more information).

|

Appearance See the description of the
Appearance tab for the
Activity Properties on
page 136.
Description Optional textual description

of the Gateway.
Extended See the description of the

Extended tab for the Process
Properties on page 134.
Sequence Flow Properties

When you have selected a Sequence Flow in the Process Editor, the following
Properties are available:

General Name Name associated with the
Sequence Flow.
Type Choose the type of Sequence

Flow (see Sequence Flows on
page 40 for more
information).

page 136.

of the Sequence Flow.


140
Event Properties
When you have selected an Event in the Process Editor, the following Properties
are available:

General Name Name of the Event.
Trigger Type (for You specify the trigger for a

Start or Start or Intermediate event
Intermediate and the result for an End
events) or Result event. The properties
Type (for End displayed on this page
events) depend on the Trigger Type
or Result Type you have
selected. For more
information about the types
of events, see Events on
page 48.

page 136.

of the Event.

Lane Properties
When you have selected a Lane in the Process Editor, the following Properties are
available:

General Name Name of the Lane.

page 136.

|
Cheat Sheets View

When you first start TIBCO Business Studio, a Welcome Cheat Sheet is displayed.
You can view TIBCO Cheat Sheets and other Cheat Sheets by selecting Help >
Cheat Sheets and selecting from the list.
Process Editor
The Process Editor is where you create your business process. It includes a Palette
that contains the tools you use to create your Process.
Palette
You can create your Process using the tools on the Palette. The Business Process
Modeling Notation (BPMN) core set is supported by the Palette, which contains
the following tools:
Palette Item Description

Allows you to select objects.
Allows you to select several objects by drawing a box

around them.
Allows you to indicate the flow of messages between

objects in separate Pools or between Pools.
Visually connects a Text Annotation or Data Object to a

Flow Object.
Adds Sequence Flows to the Process. This shows the

order of Activities in a Process.
Indicates the beginning of the Process.
Indicates a message, exception, compensation, and so

on after a Start event and before an End event.
Indicates the end of the Process.
Allows you to add a Task to the Project. A Task is

considered an atomic Activity because the work it
represents cannot be broken down to a finer level of
Process Model detail.

142
Palette Item Description

Allows you to refer to an external Sub-Process that you
want to execute at runtime.
Allows you to execute an internal Sub-Process (one that

is contained within the current Process).
Gateways are used to control the divergence and

convergence of several Sequence Flows. You can insert
Gateways in your Process for branching, forking,
merging and joining of flows.
Adds a Text Annotation to the Process. Annotations are

used for explanation/documentation of the Process.
A Data Object is used for informational purposes to

show how a document or other data relates to the
Process.
Group are used to indicate a relationship between

elements of a Process by enclosing them in a dashed
line. A Group can span Lanes and Pools.
A Pool is used as a container for partitioning Processes

in ways that make sense for your business. They are
used in conjunction with Lanes. Messages can also be
used to show message flow between objects in different
Pools.
A Lane is a sub-division of a Pool. Pools are used to

indicate the Participants in a Process. Within a Pool you
can use Lanes to characterize Activities. Note If you
delete a Lane in TIBCO Business Studio, all the objects
in that Lane are also deleted.
Alignment Tools
For easier alignment of objects in the Process Editor, you can select either or both
of the following options:
• Diagram > Grid - This allows you to align objects to a grid.
• Diagram > Alignment Guides - As you move objects in a Process Editor, a
blue line appears when the center of two objects coincide.

|
You can also align objects that you have selected by choosing options from the
Diagram > Alignment menu. For example, if you have two Activities selected,
you can align them horizontally on their centers by selecting Diagram >
Alignment > Align Middle. Alternatively you can use the alignment buttons on
the toolbar that correspond to the menu options.

144
Process Validation
When you created your Process you specified the Destination Environment. If
you specified the TIBCO iProcess Modeler, when you save your Process, TIBCO
Business Studio performs validation to ensure that the Process can be imported
into the TIBCO iProcess Modeler.
Any error messages resulting from this validation will be displayed in the
Problems View and indicate which parts of your Process need to be changed.
General Rules for Export to the TIBCO iProcess Modeler
This is not an exhaustive list of every problem that can be reported from
validation, but rather some of the more common guidelines.
Events
• A Start event is mandatory, and you should use only one.
• Start events must have a single uncontrolled output sequence flow.
• Inflow error events (throw errors) must have an Error Code specified.
Process Objects
• Send Tasks are not supported; all other Task Types are allowed (see Activities).
• Multiple Receive Tasks with no Sequence Flow input are permitted.
• Conditional Sequence Flows can only be used from a Gateway, and the
Gateway must have only one input, only one conditional output sequence
flow, and optionally only one default output Sequence Flow. Note that a
default Sequence Flow can only be used in conjunction with a Conditional
Sequence Flow.
• Parallel Gateways can only have non-conditional Sequence Flows (input and
output).
• Sub-Processes should be in the same Package as the calling Process.
• The first eight alphanumeric characters of the Process name should be unique.
• Validation is performed on the names of Data Fields and Parameters,
depending on their type. For example, the first 15 alphanumeric characters of
single-instance Data Field names should be unique within the Process and its
containing Package.

Process Validation 145
|
Correcting Validation Errors

Any problems that result from validation are shown in the Problems view. To
correct the problem do one of the following:
• Right-click the problem and select Quick Fix (if enabled for the current
problem). The gives you the option of having TIBCO Business Studio correct
the problem for you.
• Double-click the problem or right-click the problem and select Go To. This
Object Mappings - TIBCO iProcess Modeler

When you import a Process into the TIBCO iProcess Modeler, the original objects
(from the TIBCO Business Studio version) are mapped into objects that the TIBCO
iProcess Modeler supports. This section describes the mapping between TIBCO
Business Studio and TIBCO iProcess Modeler objects.

146
Project Objects
Corresponding TIBCO iProcess

TIBCO Business Studio Object Modeler Object
Project None
Package None (used when importing to the

TIBCO iProcess engine, but no
equivalent object)
Process Procedure
Sub-Process (Process referenced Sub-Procedure

by an Independent Sub-Process
call or a Process that has Formal
Parameters)
Participant Reference to an iProcess user/group or

role. An additional administrative task in
the iProcess Engine is to create the
iProcess users/groups.
Data Field (Package and Process) Field. Package level Data Fields are
created as fields in each Procedure. A
Date Time Data Field is exported as two
separate date and time fields in the
iProcess Engine (suffixed "_D" and "_T").
Process Formal Parameter I/O parameter and field. A Date Time

Parameter is exported as two separate
date and time fields in the iProcess
Engine (suffixed "_D" and "_T").
Group None
Activities and Tasks
TIBCO Business
Corresponding TIBCO iProcess Modeler Object
Studio Object
Independent Sub-Procedure call
Sub-Process
Service Tasks Enterprise Application Integration (EAI) step with

the appropriate type set

|
TIBCO Business Corresponding TIBCO iProcess Modeler Object

Studio Object
Script Task EAI Script step. If you plan on having someone else
implement the script and export or deploy it, use
the Text script type to describe the behavior of the
script that you want the Process Developer to
implement.
You cannot export or deploy Script Tasks with the
script type set to Text. For more information about
implementing Script Tasks, see TIBCO Business
Task Type (None) Complex router. Note: If the Process is re-imported

into TIBCO Business Studio, the complex router
becomes a Gateway (this is expected and provides
functionally equivalent behavior).
Receive Task iProcess Event
User Task Work Item Step
User Task Participant Work item addressee depending on the Participant

type (Performer Data Field = Field Addressee, all
other types = User Addressee)
User Task Form URL Formflow Form URL
User Task Parameter Field instance on iProcess form or Formflow

parameter
User Task Script Script object. If you plan on having someone else
implement Open, Close and Submit scripts and
export or deploy the Process, use the Text script
type to describe the behavior of the scripts that you
want the Process Developer to implement.
You cannot export or deploy User Task scripts with
the script type set to Text. For more information
about implementing User Task scripts, see TIBCO
Business Studio Process Developer’s Guide.

148
Events
TIBCO Business Studio Corresponding TIBCO iProcess Modeler

Object Object
Start/End Event Start/Stop
Timer Event (inflow) iProcess Event with deadline link and auto
withdraw deadline
Timer Event Script Deadline expression. If you plan on having

someone else implement the deadline
expression and export or deploy the Process,
use the Text script type to describe the
desired behavior.
You cannot export or deploy Timer Event
scripts with the script type set to Text. For
more information about implementing
Timer Event scripts, see TIBCO Business
Timer Event (on Task Defines deadline for iProcess step. In TIBCO
boundary) Business Studio there are two options you
can select (Withdraw Task on Timeout and
Continue Task on Timeout). These are
equivalent to the iProcess Withdraw flag.
Error Event pair (throw and Withdraw link - the throw event becomes a
catch) complex router and the catch event defines
the Withdraw link between the complex
router and the Task to which it is attached.
Gateways
TIBCO Business Studio Corresponding TIBCO iProcess

Object Modeler Object
AND Gateway (branching) Complex Router
Gateway with one input, one Condition with the Expression defined by
conditional output, and the condition on the conditional Sequence
optionally one default output Flow:

|

Parallel Gateway (multiple Wait
unconditional input)
XOR Gateway with multiple Complex Router

unconditional input

150
Connecting Objects

Association None
Sequence Flows from a Timer Deadlines Link

Event (on an Activity)
Text Annotation Unattached Annotation
Data Object None
Swimlanes
TIBCO Business
Corresponding TIBCO iProcess Modeler Object
Studio Object
Pool Not mapped
Lane Lane
Object Mappings - Aris Software

When you import a Process from Aris Software into TIBCO Business Studio, the
original objects from Aris are mapped into objects that TIBCO Business Studio
supports. This section describes the mapping between Aris objects and TIBCO
Business Studio objects.
Corresponding TIBCO Business

Aris Object
Studio Object
Event Depending on the position of the Event,
a Start Event, Intermediate Event, or
End Event.
Function (User Activity type; for User Task.

example )
Function (System Activity type; for Service Task.

example )
AND Rule Parallel Gateway.

|
Aris Object Corresponding TIBCO Business

Studio Object
Exclusive Data Based Gateway.
XOR Rule
Inclusive Gateway.
OR Rule
Rule Default Gateway.
Organizational Unit Type, Participant of the type Organizational

Organizational Unit, System Unit (multiple Participants are
Organizational Unit, and so on. supported).
Person Type, Internal Person, Participant of the type Human

External Person, Group (multiple Participants are supported).
Position Type, Position, Position Participant of the type Role (multiple

Description Participants are supported).
Application System Type, System Participant of the type System (multiple

Organizational Unit, Module Type Participants are supported).
D Attribute (ERM), K Attribute Data Field.

(ERM), FK Attribute (ERM), COT
Attribute, Technical Term
Non-function object without Data Object.

connections
Non-function object that is not a Data Object.

recognized data type or participant
and has only one connection
(incoming or outgoing) to a
function object

152

| 153
Chapter 5 Tips and Tricks
This chapter contains tips for working with the TIBCO Business Studio user
interface.
Topics
• Process Editor, page 154

• Workbench, page 156
• Problems View, page 157

154
| Chapter 5 Tips and Tricks
Process Editor
The following tips relate to the Process Editor:
I can’t see the Palette. Make sure you are in the Process Editor and
that the Palette is expanded (click the arrow to
the right, top of the scroll bar).
How can I create several Press the Ctrl key while adding the objects to
objects of the same type your Process. For example, if you want to
using the Palette? create several Sequence Flows, press and hold
the Ctrl key while clicking the Flow tool and
adding the Sequence Flows.
How do I align objects in There are two features that allow you to better
the Process Editor? align objects in the Process Editor - Grid and
Alignment Guides. These are both available
from the Diagram menu when using the
Process Editor. Grid allows you to snap objects
to the grid lines, and Alignment Guides shows
a centering line when you have aligned two
objects.
With several objects selected in the Process
Editor you can also select options from the
Diagram > Alignment menu to control the
vertical and horizontal alignment of the
objects.
I’m using Grid alignment Pressing the Alt key while moving an object
in the Process Editor and I allows you to position it between grid lines.
want to place an object
without using the Grid.
I want to see a larger view You can expand the Process Editor to fill your
of my Process. screen by double-clicking its title bar.
How can I easily resize an Pressing the Ctrl key while resizing one side of
Activity in the Process an object automatically resizes the opposite
Editor? side as well.

Process Editor 155
|
I can’t get my Sequence Occasionally when you reposition a Sequence

Flows to look right. Flow several times you create too many
bendpoints and make the flow illegible. To
restore a Sequence Flow, click the flow and
select Reset Bendpoints.
How can I create bendpoints Whilst holding down the left mouse button
when I draw a Sequence and positioning the Sequence Flow, right-click
Flow? to add a bendpoint.
I can’t get a Sequence Flow Sequence Flows are docked at the nearest
to dock where I want it to docking point rather than where you attempt
dock. to dock them. Try repositioning the middle of
the Sequence Flow to change the docking
point.
How can I position Highlight the Sequence Flow, the press the
Sequence Flows using the Period key (.) to move along the bendpoints.
keyboard? With a bendpoint highlighted, use the arrow
keys to position them and change the shape of
the flow. When you are done, press the Return
key.
How can I e-mail someone a Send them the XPDL Package file that contains
Process I am working on? the Process. Locate the Package file name in the
Project Explorer. The Package file is stored in
your workspace (by default this is
C:\Documents and
Settings\username\workspace).

156
Workbench
The following tips relate to the Eclipse Workbench:
How can I quickly change There are buttons in the upper right of the
Perspectives? screen so you can change between the
Simulation and Modeling perspectives. You
can also do this using Ctrl + F8.
My windows are a mess. Select Window > Reset Perspective. This

How can I reset them? restores the current Perspective to its default.
How can I switch to a Select File > Switch Workspace and browse for
different workspace? the location of the workspace. Note that after
you select a workspace and click OK, TIBCO
Business Studio must restart before you can
access the new workspace.

Problems View 157
|
Problems View
The following tips relate to the Problems view:
How can I correct Either:

validation errors?
• Right-click the problem and select Quick
Fix (if enabled for the current problem).
This gives you the option of having TIBCO
Business Studio automatically correct the
problem for you.
- or -
• If no quick fix is available, Double-click the
problem or right-click the problem and
select Go To. This displays the Process in
the Process Editor, highlighting the
offending object and allowing you to
manually correct the problem.
In the Problems view I see Click to display the Filters dialog. This
not only problems for my
allows you to customize the problems display.
Process/Project, but
For example, you can select options to display
problems for all
problems for the selected resource only, or for
Processes/Projects.
any resource in the same Project.

158

Index
| 159
Index
A customer support x
Activity 42
Participant 80
properties 136 D
Activity Marker 47
Aris software Data Field 57
creating custom symbols 117 creating 79
export 118 Data Object 36
import 119 decision behavior 91
integrating with 117 Declared Type 58
Artifact 36 Deploying a Process 33
Asset 60 Diagram Fragments View 133
ad-hoc 61
Concept Model 61
service 62
types 5 E
Association 39
Emailing Processes 114
Embedded Sub-Process 96
creating 97
B errors 144
correcting 145
Business Asset 60 Event 48
Business Process Asset 61 properties 140
Business Process Modeling Notation (BPMN) 64 exporting from Aris 118
business processes patterns 87 exporting to the TIBCO iProcess Modeler 144
Extended Attribute 57
creating 83
C
Cheat Sheets View 141 F
Concept Model Asset 61
creating a Package 10, 72 Flow Object 42
creating a Process 75 forking behavior 87
creating a Project 8 Fragment
creating Data Fields 79 creating 105
creating Participants 80

160
| Index
G P
Gateway 51 Package 4, 56
properties 138 creating 10
Group 38 import 110
Palette 75, 141
using 10
Parameter 58
I Participant 59
associating with Activity 80
importing a Package 110 associating with an Activity 80
importing Aris procedures 119 creating 80
Independent Sub-Process 94 Perspective 129
creating 99 Pool 68
Intermediate Event 49 Problems View 130, 157
Process 4, 56
adding objects to 10
correcting errors 145
L creating 75
exporting to TIBCO iProcess Modeler 144
Lane 65 Fragments 55
properties 140 properties 134
re-use 94
sample 7
selecting objects 11
M validation 144
working with 10
merging behavior 89 Process Component 54
Message Flow 39 Process documentation 124
Modeling perspective 129 Process Editor 75, 141, 154
multiple choice behavior 92 alignment tools 142
tips 154
using 10
Process Fragment 55
O Process Properties 134
Project 4, 56
object mapping - Aris Software 150 creating 8
object mapping - TIBCO iProcess Modeler 145 creating in source control 113
Outline View 131 purpose 8
Project Explorer View 129
Properties View 133

Index
| 161
Q TIBCO Business Studio

audience 2
Quick fixes 145 Modeling perspective 129
object hierarchy 4
online help 6
package import 110
R sample Processes 7
tutorials 12, 16, 30
refactoring Sub-Processes 97 using with Subversion 112
Re-use 94, 106 TIBCO iProcess Modeler
export 144
package import 110
TIBCO iProcess Suite
S integrating with 115
sample Processes 7
selecting Objects 11
Sequence Flow 40 V
combining 88
properties 139 validation errors
using to connect objects 11 correcting 145
source control 112, 113
Special Folder 63
enabling and disabling 86
Start Events 48 W
Sub-Process 45
calling 94 Workbench 156
expanding 96 workflow pattern 87
refactoring 97
Subversion 112
support, contacting x
SVN Repository X
browsing 113
Swimlane 65 XML Process Definition Language (XPDL) 64
T
Task 42, 43
technical support x
Text Annotation 37

162
| Index

Tib Bs Modeler User

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Tib Bs Modeler User

Загружено:

Авторское право:

Доступные форматы

TIBCO Business Studio™

Chapter 1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 2 Concepts and Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

TIBCO Business Studio - Modeling User’s Guide

TIBCO Business Studio - Modeling User’s Guide

Chapter 4 Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

TIBCO Business Studio - Modeling User’s Guide

Chapter 5 Tips and Tricks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

TIBCO Business Studio - Modeling User’s Guide

• Related Documentation, page viii

TIBCO Business Studio - Modeling User’s Guide

This section lists documentation resources you may find useful.

TIBCO Business Studio Documentation

Other TIBCO Product Documentation

TIBCO Business Studio - Modeling User’s Guide

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

bold code Bold code font is used in the following ways:

italic font Italic font is used in the following ways:

TIBCO Business Studio - Modeling User’s Guide

How to Contact TIBCO Support

TIBCO Business Studio - Modeling User’s Guide

Chapter 1 Getting Started

• Who Should Use TIBCO Business Studio?, page 2

TIBCO Business Studio - Modeling User’s Guide

Who Should Use TIBCO Business Studio?

TIBCO Business Studio - Modeling User’s Guide

Modeling a Process can be achieved in several different ways, however the

Define the "As is" Process

Define the "To be" Process (Optional)

Hand Over for Implementation (Optional)

TIBCO Business Studio - Modeling User’s Guide

About Projects, Packages and Processes

In TIBCO Business Studio there is a hierarchy consisting of Project, Package and

TIBCO Business Studio - Modeling User’s Guide

TIBCO Business Studio - Modeling User’s Guide

Getting Help in TIBCO Business Studio

TIBCO Business Studio uses online help and cheat sheets:

TIBCO Business Studio - Modeling User’s Guide

Using the Sample Processes

TIBCO Business Studio - Modeling User’s Guide

Creating a Project, Package and Process

1. Select File > New > Project.

TIBCO Business Studio - Modeling User’s Guide

— Process Name - If necessary, change the name of the Process.

TIBCO Business Studio - Modeling User’s Guide

Working with Processes

3. Click on the Process. The object is added.

TIBCO Business Studio - Modeling User’s Guide

Flow. The pointer changes shape:

3. Draw the Sequence Flow using one of the following methods:

TIBCO Business Studio - Modeling User’s Guide

Tutorial 1: Creating a Simple Process

Task A Create the Project, Package and Process

Task B Customize the Lane

TIBCO Business Studio - Modeling User’s Guide

2. Make the Lane larger:

Task C Add Some Objects to Your Process

2. On the Palette, click Start Event.

TIBCO Business Studio - Modeling User’s Guide

9. Add another Activity in the same manner, naming it Review Application.

Task D Add Flow to the Process

4. Another way to add Sequence Flow is by dragging: click the Receive