Business Data Services Glossary

Association is a relationship where all the objects have their own lifecycle and there is no parent. For example: the Teacher-Student relationship. This is the most general of the UML relationships.

A property of a Class, for example an Order class, may contain date and orderNumber attributes, amongst others.

The type of attribute can be one of the following:

• Primitive Type (see below)
• Enumerated Type (see below)
• Class Type (see below)

When choosing a type for an attribute, BOM Editor refers to the BOM Native Types as Primitive Types. Primitive Types which are not pre-defined, for example those that are defined within a BOM, have the package name of the BOM against them when selecting the Type to use. This can be useful, for instance, if there is more than one BOM that contains an OrderId class.

Process Template field values can be of a Basic Type or an External Reference Type that refers to a BOM Class.

The Basic Types are:

• Text
• Floating Point Number
• Fixed Point Number
• Boolean
• Date
• Time
• Date Time

Note: There is no Datetimetz, Duration, BOM Object, URI, or ID type (nor an Attachment type), and the Performer field is a special type of Text field that contains an RQL query string.

The Basic Types are also known as Process Types.

Business Data

See Business Data.

Business Object Model

See Business Object Model (BOM).

An entity in the BOM that represents a particular part of the application data, for example, an Order or a Customer. A BOM Class is a template for a Business Object.

There are 8 predefined primitive types that can be used to build other Primitive Types, or used as types of attributes of classes:

• Boolean, String
• Floating Point Number
• Fixed Point Number
• Date, Datetimetz
• URI, ID

Structured data that contains information about real-world entities that an organization deals with, for example Customer, Order, and Orderline. Each of these entities will have a number of attributes, for example name, address, and date. These objects will also be related to each other in different relationships and with different multiplicities.

An application that is created by deploying a Business Data project. A Business Data application contains the business data generated from the BOM or BOMs in the Business Data project.)

An instance of a BOM Class. For example, for a Customer class, there is a Business Object that represents and holds information about a particular customer. Do not confuse this term with Object BOM Native Type.

The Model representing the structure of the application data created using the BOM editor. A BOM can contain local or case data.

Case Data Manager (CDM) is the component responsible for handling business data in TIBCO BPM Enterprise.

Composition is a specific type of Association used when a Class is a collection or container of other Classes, but the relationship is such that if the Class that functions as the container is destroyed, the Classes representing the contents are destroyed as well.

A type that can have a restricted set of values. For example, DayOfWeek can have the following values:

SUNDAY, MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SATURDAY

In a BOM, it is possible to define a type based on one of the BOM Native Types or another Primitive Type. When these Primitive Types are defined, it is possible to add some limitations using a regular expression or a range.

Data Fields of Primitive Types cannot be used in processes. They must be of BOM Types or Basic Types.

An instance of a flow through a Process Template with data values that reflect the information being processed by this particular instance of the process.

Data that lives within a Process Instance. The object will either be a Business Object or a Basic Type.

The definition of what a process should do.

Basic Type.

See Basic Type.

Resource Query Language – a language for selecting which resources can have access to a UserTask in a process. For example:

resource(name="Clint Hill")

Unified Modeling Language – an international standard modeling language supported by many tools. Identifies different types of relationships that can exist between the objects being modelled, for example: composition, association, and aggregation.

A UserTask is a step in a process that is handled by a user and requires the user to complete a form. On completing the form, the user submits the values causing the changes to the field values to be saved. A user may Close a form so that they can complete it later.