ACTIVITY_TABLE
Description
ACTIVITY_TABLE
allows to refer to the activity table in the data model without using its exact table name. This operator is helpful in data models with multiple activity/case tables.
This function returns a reference to an activity table. The result of this function can then be used at all places where table names are accepted.
Syntax
ACTIVITY_TABLE ( [ expression ] )
When an expression that involves a column of an activity table is passed as an argument, the activity table connected to that column is referenced.
When no argument is passed, the default activity table in the data model is referenced.
Examples
[1] In this example, the data model contains one activity and one case table. By using a column reference as the input expression, we refer to the case table and query one of its columns: | ||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||
|
[2] In this example, the data model contains one activity and one case table. By using an activity table reference as the input expression and | ||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||
|
[3] In this example, the data model contains one activity and one case table. By passing no arguments to the | ||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||
|
[4] In this example, MERGE_EVENTLOG is used to combine two activity tables into one. We can use | |||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||
|