
Workflow runtime administration covers several transactions that you can use to monitor and control execution of workflows.
Basic Settings
Maintain system administrator for runtime system
The system administrator specified here receives all messages created by workflows for which there is no separate system administrator specified in the workflow definition. They also receive the messages that refer to workflows that have not yet been started.
Configure workflow system RFC destination
The workflow runtime system executes its RFC and tRFC (transactional RFC) calls on a logical destination. This is where you can set up or change a logical destination.
No logical destination is configured for the workflow system tRFC calls as standard.
Customizing workflow runtime
You can make the following settings here:
Check logical system
When this flag is set, the system checks whether the logical system specified in object references agrees with the current system.
Activate container condensation
When this is activated, only field contents that are not initial are saved for container elements that refer to structures.
Specify the maximum number of nested subworkflows permitted at runtime
If this upper limit is exceeded, the workflow assumes the status error.
Specify the maximum number of nodes that can be processed at runtime within a workflow definition
If this upper limit is exceeded, the workflow assumes the status error.
Wait if locking conflict
Here you define how frequently the workflow manager should attempt to set a lock for a work item. If the lock still has not been set after these attempts, the work item is saved. A background job checks these work items periodically and processes them as soon as the locking error ceases to occur.
Deactivate display of agent names in workflow log
When display is deactivated, asterisks (*) are displayed instead of the user names.
Session control for secondary methods
Secondary methods are executed in a separate session. Here you can define whether this session is deleted or whether it remains open after executing the secondary method.
Other Settings
Administrator overview
The administrator overview displays three key figures for monitoring and administrating Workflows. The status icon gives you a good overview of the current situation. The key figures on the General Data and Persistence Data tab pages are snap-shots from when the overview was called. The Background Jobs tab page contains information from the past 24 hours.
Deadline monitoring for work items
Tasks with deadlines also have deadline monitoring based on a background job. You can change the period duration of the background job, change, schedule, display, or execute the background job manually. This background job has a standard scheduled period duration of three minutes.
Error monitoring for work items
If work items have the status ERROR for a long time, they are restarted automatically. This task is performed by a report that is controlled by a background job. You can change the period duration of the background job, schedule, delete, or display the background job. You can also start the report manually using Execute work item error monitoring.
Work item rule monitoring
If conditions are defined for the work item start or work item end for steps in the workflow, these conditions must be regularly checked. This task is performed by a report that is controlled by a background job. You can schedule or display this background job. You can also start the report manually using Execute work item rule monitoring.
Clearing tasks
The background jobs of the workflow system create job protocols that need to be regularly deleted. This task is performed by a report that is controlled by a background job. You can schedule or display this background job. You can also execute the report Execute clearing tasks manually.
Reorganization
These functions include reports for archiving and deleting work items. For more information, see:
During archiving, data that is no longer required in the system is checked using application-specific criteria and put in an archive file. The data is not removed from the database. After the files to be archived have been completely copied to the archive file, they can be deleted from the database in a separate program run.
All interactions in conjunction with archiving are performed using archive management ( ).
All actions or programs are processed in the background. You can schedule the necessary background jobs in archive management.
For more information, see Archiving Application Data.
Display workflows from archive
You can use this report to display a workflow for an application object. After the workflow work item determined using the selection criteria is read from the archive, the system displays the workflow log. However, only limited functions of the workflow log are available.
For more information, choose
.
Delete work item history
This report deletes all workflow log entries relevant to work items (work item history) without archiving. If you do not set the indicator Delete Immediately, the report is only executed on a test basis.
Container handling
You can use the Administrate container persistence function to define whether the data of container elements that refer to a structure is saved in the container table or in another table.
You only need to use this function if you are not using the new container. You use the new container for a workflow if the XML persistence profile is entered in its version-dependent basic data.
You define this saving mode as a standard for all container elements that refer to the same structure. If there is no entry for a structure, container elements that refer to this structure are saved in the container table. The following modes are available:
Transparent table with include structure
The data is saved in a structure-specific table.
Transparent table with XML
The data is converted into an XML document and automatically saved in an XML table by the workflow system.
To improve the performance of the workflow system, define a persistence type for all structures that are used to create forms.
Work items without agents
You can use this function to determine all work items without recipients for a particular selection period. If you double-click on an entry in the list displayed, you go to the work item display.
If recipient determination failed because the possible agents of the task were not added correctly, you can go to assignment of the possible agents by choosing
.
By choosing
you can execute recipient determination again.
As an administrator, you can forward the work item to any users by choosing
. This user must neither belong to the possible agents of the workflow nor must forwarding be permitted for this work item.
Work items with deleted users
This function enables you to determine the work items that are assigned an agent but the relevant user has been deleted.
Work items with monitored deadlines
You can use this function to determine all work items with monitored deadlines for a particular selection period. You can go to the work item display by double-clicking in the list displayed.
Diagnosis of Workflows with Errors
You can use this function to Investigate Workflows with Errors.
Unlock workflows
You can use this function to select and unlock work items that are locked against execution.
Locking tasks against execution is a function in task maintenance.
Execute work item without agent check
You can use this function to Execute a work item as an administrator.
Workflow restart after error
You can use this function to restart workflows with errors.
Continue workflow after system crash
You can use this report to select and continue workflows that have had the status started for longer than a day. This means that workflows that have come to a halt after system errors can be continued.
Synchronize runtime buffer
You can use this function to initialize the main memory buffers used by the workflow system. This reads the current values from the database again so that the current data is used.
You should always refresh the runtime buffer when you have made a change in a task definition.
Execution of this function will initially result in reduced performance for certain workflow functions. This applies until the main memory contains all the necessary data.
Workflow RFC Monitor
You can use this function to display the log file of the transactional RFC.
Check conditions for work items
You can use this function to repeat definition of the recipients for a work item. A rule entered for the determination is also re-executed.
Execute rules for work items
You can use this function to execute the rule for agent determination for a work item again.
You reach all functions for managing the workflow system described here using or using .