Reuse Shared Logic in Scenario Editor

ToLast reusereviewed: September 21, 2026

Use this article when multiple Scenario Editor tests need to share helper logic, common setup, or reusable validation patterns.

Recommended guidance

• Avoid copying the same helper code into many scenarios.
• Keep shared logic versioned and reviewed.
• Document inputs, outputs, and side effects for every shared helper.

Validation workflow

1. Identify the repeated logic and decide whether it belongs in a functionshared fromhelper, oneDPL, scriptservice incall, another,or wetest includetemplate.
2. Store theshared relevant script using the include Action from Appvance Designer.

   Usage: include relative:-<filename>

   This will be helpful in shortening your designer scripts.

   Call other scripts as functions. This will let users to include other designer script at any given step as shown in below screenshot.

   In the example below, note:
3. The prefix : relative:- just before the login.ds filename on the Value column.

This script can be executed onlyfunctions in the Scenarioapproved Builder.project location.Pass parameters

instead of

hard-coding

Inenvironment-specific values.

Add a small validation scenario to prove the Scenarioshared Builderhelper itworks.Update dependent scenarios when the shared helper changes.

Note: Use shared logic carefully: a broken helper can beaffect addedmany asscenarios shownat belowonce.

The other dependent designer scripts can be added in resources section.

An Example Designer script is attached is this article as well for reference.

activity.ds

login.ds

logout.ds