TCC - Technical information on Documentation - V2

TCC - FAQ on objects external to the Application

Mon, 01 Jan 0001 00:00:00 +0000

Why are objects external to the Application sometimes visible as Transaction End Points?

When more than one Application is analyzed in the same “triplet” of CAST AIP schemas, you may find that rules created for Transaction End Points in a specific Application contain results from both Applications. This is expected behaviour and is due to that fact that objects that are external to an Application (i.e. outside the Application boundary) are always included for Transaction End Points.

TCC - Handling multiple entry points in a call graph

Mon, 01 Jan 0001 00:00:00 +0000

Handling multiple entry points in a call graph

If two entry-points are included in the same call graph, two transactions will be identified for the parts of the call graph that are situated below the entry points. As a consequence, the transaction that is “higher up” could be recorded by the CAST Transaction Configuration Center as empty, whereas the “lower” transaction will be correct. In this case it is recommended to only retain the entry point that is “higher up” so that the the most complete transaction is recorded. As a consequence the number of “empty” transactional functions will decrease.

TCC - How does CAST determine which tables are considered as detail in a Data Entity?

Mon, 01 Jan 0001 00:00:00 +0000

How does CAST determine which tables are considered as detail in a Data Entity?

CAST uses OMG CISQ AFP specifications to determine when the tables that form a Data Entity are considered as “detail” as shown below:

The OMG CISQ AFP specifications states the following:

In order for a data table to be grouped under a master data table, the following tests must be checked in sequence:

The table has primary key with a foreign key constraint to another table. This is a table extension pattern.
The table has a unique index over a foreign key to another table. This is another table extension pattern.
The table is exclusively composed by 2 or 3 foreign key attributes and, optionally, a primary key. This is an associative table. Associative tables are always aggregated with another table. One of the related tables is picked based on the best match algorithm. Associative tables are never considered master tables.
The table has a set of mandatory foreign keys with a cascade delete constraint. This is a classical master detail relation. The master table is chosen based on the best name match.
The table has a set of foreign keys with other tables with similar names (similar suffix and prefix). The master table is chosen based on the best name match

Please see:

TCC - Which links are used to define a transaction?

Mon, 01 Jan 0001 00:00:00 +0000

Which links are used to define a transaction?

For computing the transaction call graph starting from a transaction entry point, the CAST Transaction Configuration Center takes into account all links except those listed below. All the links taken into account are those retrieved from the CTV_LINKS view in the CAST Analysis Service, which in turn reads some of the links present in the Acc table.

The links which are ignored by the CAST Transaction Configuration Center while computing the call graph of a transaction are the following: