Application analysis configuration - Transactions - Transactions

Overview

The Transactions panel shows detailed information in two sections about the number of transactions and data entities identified in the application during the analysis:

Transactions panel

This expandable section shows detailed information about each transaction identified in the application during the analysis:

Table description

Download

Export the contents of the table to a comma-separated values (CSV) file, which can be viewed using Microsoft Excel or similar.

Filter

Filter the contents of the table, which can be particularly useful if you have a large number of items.

Hide incomplete transactions

Transactions marked in pink are deemed to be incomplete, i.e., they do not reach an end-point or a data entity. These incomplete transactions are “empty Transactional Functions” with a Function Point value of 0. You can see the total number of incomplete transactions, at a glance, in the top left corner:

You can hide these incomplete transactions using the toggle available above the table. When toggled, only complete transactions are shown:

Full Name

Shows the full name of the object/file. Rolling the mouse pointer over the item will show the full name if it is too long to be displayed in the column.

Type

The Type of Transaction

Data Entities

The total number of data entities that the transaction reaches - these data entities will be displayed in detail in the Data Entities section.

End Points

The total number of End Points that the Transaction reaches.

Excluded

Indicates whether the transaction has been “captured” (i.e. identified) by an exclusion rule.

Action menu

Action menu options

Show rules

For each transaction listed in this section, you can view the rules that identified the item as a transaction:

This will then show the rule or rules - you can view more details about the rule in the Rules section:

Show details

For each transaction listed in this section, you can view the details of the transaction (data entities and end-points):

View call graph

For each transaction listed in this section, you can view the full call graph. See Call Graph for more information:

View objects

For each Transaction listed in this section, you can view all objects that are called by the selected transaction, together with their source code:

Objects are displayed in a popup and source code (where available) can be viewed:

Item Description
Download This option will export the contents of the list to a comma-separated values (CSV) file, which can be viewed using Microsoft Excel or similar.
Name/Fullname Name/Fullname of the object calling the selected Transaction.
Type Type of object calling the selected Transaction.
Role Role of the object in the selected Transaction:

  • Entry Point (in case of merged Transaction, this role is displayed only for the Entry Point object of the merged root)
  • Data entities (those issued from user-defined rules will appear before those issued from built-in rules):
    • Data Entity (setup)
    • Data Entity (built-in)/
  • End Point
  • Objects from the reduced call graph
  • Objects from the full call graph

Objects are listed in the order shown above.
Code When the object is “generated” and is therefore outside the application boundary:



When the object is “external” and is therefore outside the application boundary:

View leaves

Available in ≥ 3.4.0-funcrel

Displays a list of objects and their type, that are considered “leaves”, i.e. an object which is not an end-point, not a data entity and does not call any other objects. This can help understand why a call graph is incomplete and where it is broken:

Use the Hide full graph leaves option to remove any objects from the list that match the following:

  • an object in the full call graph of a non-empty Transaction
  • an object in the full call graph of an empty Transaction

Check architecture

For each transaction listed in this section, you can check the objects contained within it against an Architecture Model:

A new screen will open allowing you to select the existing Architecture Model you want to run the check with:

Any objects that form part of the transaction AND that violate the selected Architecture Model will be flagged in the results dialog box:

Data Entities panel

This section shows detailed information about each Data Entity identified in the application during the analysis:

Table description

Name/Fullname

Name/Fullname of the Data Entity (i.e. the file or object).

Type

The Data Entity type.

Excluded

Indicates whether the transaction has been “captured” (i.e. identified) by an exclusion rule.

Download

This option will export the contents of the table to a comma-separated values (CSV) file, which can be viewed using Microsoft Excel or similar.

Filter

This option allows you to filter the contents of the table, which can be particularly useful if you have a large number of items.

Action menu

Action menu options

Show rules

For each Data Entity listed in this section, you can view the rules that identified the item as a Data Entity. See above: this describes the identical feature for transactions.

View call graph

For each Data Entity listed in this section, you can view the full call graph. See Call Graph for more information.

Application analysis configuration - Transactions - Call Graph