Project variables are instance
variables defined with project scope. Unlike regular (process) instance
variables, project variables are stored in their own columns in the instance
table of the process execution engine's database.
Because they stored in their own table column,
project instance variables have special advantages and limitations in
comparison to process instance variables:
- You define a project variable once for a given project. The
characteristics of a project variable, such as name, type, or length, will be
the same in any process.
- You can view project variable values in the WorkSpace
Work List panel. Each project variable will show
up as an available column, and the user will be able to select it as a
presentation column.
- You can perform a search or to sort instances based on the value of a
project variable.
- Fewer data types are available for project variables, as described in
the Project Variable Data Types section below.
Project variables are defined during the development phase. After you
have defined a project variable, you should avoid changing its type or name.
Note: Each project variable adds some overhead, so you should avoid using
too many project variables. It is recommended that you use fewer than 10, but
the maximum limit is 256 project variables in a project.
Defining Project Variables as a Business Indicator
You can define a Project Variable as a Business Indicator. A Business
Indicator is used primarily to generate Business Activity Monitoring (BAM) and
Business Activity Data Mart information.
Project Variable Data Types
Project variables support fewer data types than regular instance
variables. For example, neither BPM Objects nor binary values can be stored in
project variables. A project variable can have one of the following data types:
| Data Type
|
Remarks
|
| Bool
|
|
| Decimal
|
Up to 255 digits
|
| Int
|
|
| Real
|
|
| String
|
Up to 255 characters
|
| Time
|
|