Document toolboxDocument toolbox

Consumable Scenarios

Consumable Scenarios can be used to integrate scenarios and their contents into other scenarios. The advantage is that you do not have to recreate the structure and assign the objects again. Instead, you only have to add the Consumable Scenarios to the respective Scenario. The content of the integrated Consumable Scenario is taken into account during the export and integrated into the documentation.

A Consumable Scenario can be created just like a standard Scenario, by pressing the “New Scenario”-button or via the context menu of a Scenario folder. In order to create a Consumable Scenario, you have to select the respective radio button in the appearing window:

In contrast to the standard Scenarios, Consumable Scenarios can be added into a standard Scenario.
A consumable scenario is then created:

The type of a scenario can also be changed via the context menu "Edit Scenario Properties".

You can only change the type of a scenario if the following conditions have been met:

  • Change standard Scenario to a Consumable Scenario → The standard scenario contains no scenarios. A consumable scenario cannot contain any other Scenarios
  • Change Consumable Scenario to a standard Scenario → The consumable scenario is not used in any standard Scenario.


A consumable Scenario can be added into a standard Scenario via the Scenario Designers Edit Mode. You can insert consumable Scenarios into the structure of a Scenario out of the “Scenarios”-tab via drag-and-drop.


A Consumable Scenario can only be added to a standard Scenario, not into another Consumable Scenario or a Scenario Template!

The table below shows the options available for each scenario type:

Scenario Type

Structure Elements

Entities

Add Scenarios

Standard(Haken)(Haken)(Haken)
Consumable(Haken)(Haken)(Fehler)
Template(Haken)(Haken)(Fehler)

Using the context menu of the Consumable scenario, you can jump directly to the respective scenario to display the structure.

The content of the Consumable Scenario will be inserted into the documentation of the scenario in the following way:

General Structure:

Table of Content (Standard Scenario)

  1. Structure Element A (Standard Scenario)
  2. Structure Element B (Standard Scenario)
    1. Entity A (Standard Scenario)
    2. Entity B (Standard Scenario)
  3. Structure Element C (Standard Scenario)
  4. Title of consumable Scenario (Consumable Scenario)
    1. Structure Element A (Consumable Scenario)
    2. Structure Element B (Consumable Scenario)
      1. Entity A ((Consumable Scenario)
  5. Structure Element D (Standard Scenario)

Consumable Scenarios can be used to create single blocks. Those blocks can be inserted into the structure of a standard scenario.
Create Consumable Scenarios for the following purpose:

  • There is content in a scenario that should be reused more often and should occur in several scenarios.
  • This content can change in the future and should be centrally modifiable.
  • If only the structure (that does not change) is to be reused, a scenario template should be used instead of Consumable Scenarios.

© 2023 bluetelligence GmbH. All rights reserved.
Impressum – Legal Notice: https://bluetelligence.de/en/imprint
Privacy policy: https://performersuite.de/en/privacy-policy
Atlassian privacy policy: https://www.atlassian.com/legal/privacy-policy