On this tab page, you make the fundamental settings for the modeling and execution of this version of the workflow.

If you set the indicator Advance with dialog, you can set the indicator individually for each step definition. If the indicator is not set, it is removed in every step of the workflow definition and cannot be set manually.

If you do not make any specifications for the maximum node number or the maximum subworkflow level, the settings made in Customizing by choosing SAP Web Application Server ® Business Management ® SAP Business Workflow ® Basic Settings (Workflow System) ® Maintain Administration Data for Workflow Runtime System apply.

The system only displays whether this version of the workflow is locked against an instantiation here. You can only change this setting in the classification of the relevant multistep task.

With performance optimization you specify what data is to be logged by the system. The more data you have logged, the more the system performance suffers.

Using the Lock properties of the workflow system, you define at what stage during the execution of a workflow a lock is set. In Locking properties for sequential workflows, a lock is set at the start of a work item that lasts as long as a synchronous chain. In the standard procedure, a lock is set every time a work item is executed. The first alternative has better performance, but SAP recommends that you only use this if the workflow does not contain any parallel sections, because these can lead to lock conflicts.

In the persistence profile, you specify whether the containers for the workflow are saved in normal tables or in an XML table. For compatibility reasons, structure persistence is activated for workflows from earlier releases (compatibility mode). For new workflows, XML persistence is used as standard.