Show TOC

 Definition of Scenario Steps

Use

You use this function to define scenario steps. You need scenario steps if the form configuration is not to be processed as a whole at the runtime of the process, rather that depending on the process step involved, different parts of the form configuration are relevant.

You assign scenario steps to a workflow step when defining the process. Only the back-end services and operations that belong to the scenario step, and all previously processed scenario steps that were not saved are run at runtime.

Features

  • A form scenariocan consist of several steps; however, at least one step must exist. You can use a number to determine the step sequence of the scenario steps.

  • You can use attachments and links for additional information on the form depending on steps. This means that for each scenario step you can define which attachments and which links are available.

  • Depending on the step, you can configure the properties of attachments.

  • You assign the form fieldsthat are relevant for this step to scenario steps. A scenario step therefore represents a subset of the defined form fields. As the form fields are assigned to back-end services, a scenario step also represents a subset of the fields and operations defined for the back-end services.

    If you do not explicitly assign a form field to a step, all form fields are understood to be assigned and therefore relevant for the step.

    The assignment of form fields is relevant at runtime, but is also enhanced with the following mechanism:

    During the processing of the process, the form fields that were used in each step are internally documented for the step. Each form field that was used in a step is then automatically also used in all subsequent steps. This additive approach means that the following fields are relevant in a scenario step i:

    • All form fields that are assigned to the scenario step i in the Customizing of the form scenario

    • All form fields that were relevant at runtime in the previous scenario step i-1

  • Depending on the step, you can configure the field properties of form fields.

  • You can display an overview of the back-end operations that are run based on the field assignment.

Activities

  • For each form scenario that you create, the system creates a default scenario step.

  • You should use easily identifiable labels for the scenario steps, since they are used in the workflow to create the text of the work item and appear under this name in the universal worklist (UWL) of the next processor.

  • You define the attachment types to use in the scenario step, and their properties.

    For more information, see Definition of Attachment Types .

  • You define links for additional information on the form.

    For more information, see Creation of Links for Additional Information .

  • You determine which form fields are relevant in the scenario step and define the field properties depending on the step.