History, reporting and execution
Configure process to record history of data, and reporting and execution properties.
- Record history
Records history of data, such as activity taken and completed.
- Retain indefinitely
By default, the system retains the process indefinitely. You can retain the process for a specific period by defining the retention period. The jobs are automatically deleted once the retention period is over.
To retain the process for a specific period, clear Retain indefinitely and configure the retention period in years, months and days (default: 1 year, Minimum value: 1 day).Deleting is a non-recoverable action.
You can also configure the retention policy at the system level.
- Include in analytics
Allows the data related to jobs for a process to be picked up by Kofax Analytics for TotalAgility reporting so that process data can be analyzed.
- Reporting tag
Allows a reporting tag to be added to a process. This enables Kofax Analytics for TotalAgility to apply a custom filter on a report.
See Add reporting tags.
- Capture process
Allows the process to be considered a capture process so that the data within Kofax Analytics for TotalAgility reports can be used to filter the data returned.
- Thread pool
Thread pool to associate with the map so that the execution of a number of concurrent activities can be controlled. See Thread pools.
- Max loop count
Allows you to define the number of times an activity can be executed in a synchronous job or business rule (default: 1000).
Continuous looping in a synchronous job or business rule can cause high workload on the TotalAgility server. Maximum loop count helps in reducing the workload on the TotalAgility server.
For a process with automatic activity, the job creation fails if the permissible loop count is reached. For a process with a business rule node, if the Synchronous and Maximum loop count properties are set for the Business rule node but not on the map containing the Business rule node, the job gets created but gets suspended when the permissible loop count is reached. A note is added to the job to reference the loop count being reached.
This property is not available for a case map.
By default, the maximum loop count set at the system level is available for all processes. The loop count set at the process level takes precedence over the loop count set at the system level.
- Allocation algorithm
Algorithm options for allocating work to resources:
First Found: Offers the activity to the first available resource (checks for those who are first in the waiting state).
Cost: Checks each available resource and offers the activity to the resource with the lowest cost.
Skill: Checks each available resource and offers the activity to the resource with the highest skill level.
Speed: Checks each available resource and offers the activity to the resource with the highest productivity rating (based upon the actual work compared to the expected work).
- .Net assemblies
The .NET assemblies to associate with the process so that the process can use external assembly components.
On exporting a process, the .NET assemblies associated with the process are also exported.
On importing a process from a version previous to TotalAgility 7.0, all the available .NET assemblies are imported. You can configure the assemblies that are required.
When you view a system map, the process is updated with the associated .NET assemblies.
To add a .NET assembly, click Add, select the assembly and click Done. See .NET assemblies for more information.