Analyzes

📄️ Object: Active Paths

In environment with no long history of executions it can be difficult to determine a list of active objects. This module searches for active objects based on the dependencies to other objects. It looks for paths to schedule objects

📄️ Object: Active Path Analysis

As the module ana.ActivePaths this module searches for active paths of runnable objects. Additionally, the module does further analysis. Therefore it uses executions if available. The period of the executions can be defined by options.

📄️ Object: Compare

To determine the difference of objects in two clients this module can be used. One use case is to analyse the differences between the production and test environment. The objects to analyse must be defined in a b4A object list. There are two different methods support by the module. The basic mode just checks if objects have been moved or removed from the second client. The enhanced mode also compares the attributes of objects.

📄️ Object: Compliance Check

In very environment it is important to follow policies to keep it maintainable to ensure functionality of the authorization rules. Additionally policies help to work easier for operating teams. To ensure that policies are followed this module provides a possibility to automate the check for compliance. Therefore the module provides a set of functions to define the rules. These rules can be stored in a b4A script variable or a b4A script file.

📄️ FileTransfer: Active Paths

To find active objects the usage of the statistic records is the most simple solution. In environment that do not have a lot of records stored in the database this possibility is limited. This module searches for active filetransfers based on the dependencies to other objects. Therefore paths to schedules are located. Additionally the module tries to find details about the transfer. If available statistic records, object referentes in processes and attributes are used.

📄️ Runnable: Find Unused

The module helps finding unused runnable objects. They will be identified by counting the number of executions. If there is no execution or at maximum one execution that is older than a given number of days the object is unused. The results are stored in a file in CSV format.

📄️ Workflow Last Run Analysis

The module analyze the last run of workflows. The quality run will be judged in three stages. The stage is defined be the number of successful runs of the workflow tasks. The results can be stored in a file in CSV format.

📄️ Object: References in Attributes

The module searches for references to objects in all attributes of other objects. The results are stored in a file in CSV format.

📄️ Object: References in Processes

To find objects referenced in processes this module can be used. It reads the processes and searches for objects used in Automation Engine script functions. The module is able to identify object references that are constructed using script variables. This requires that the variables are defined in the same script.

📄️ User: Last Session

This module can be used to determine the last sessions of users that are older than a given number of days. Optionally just last sessions that are not older than another given number of days are returned.