Execution Data of Executable Objects

Recording the execution data of an executable object is triggered as soon as it is activated and ends when the execution is completed. The execution data lists display real-time data, which means that if the status of an active task or object changes, this is reflected immediately.

When you define an executable object you specify what should happen with it once its execution has been finished. The default setting automatically deactivates tasks as soon as their execution is successfully completed. This means that they are no longer available from the Tasks window in the Process Monitoring perspective, which is important for large installations that deal with thousands of tasks at a time. Of course, you can change this setting (see Automatic Deactivation Section in the Attributes Page description). Also, if you leave the default setting, you can still have deactivated tasks displayed; a setting in the Process Monitoring Filter caters for this (see Filtering for Deactivated Tasks).

Regardless of this definition, every run is recorded and stored in the form of historical data presented in lists. Even when tasks are no longer available by default in the Tasks window, the history of their runs is still accessible.

The Execution data lists are a key audit feature that guarantees full audit capability. Since the system keeps the execution data until explicitly removed from the database, this allows you to trace the development and statuses of your processes.

Execution Data Provided in Different Lists

With historical data on each and every run being recorded, the lists can be huge. To help you find and work with them, historical data is presented in various lists that segregate the data according to the nature of their tasks: