Create Unique Strings in Scenario Editor Scripts

ToLast createreviewed: September 28, 2026

Use this article when a Scenario Editor script needs unique values for usernames, emails, order IDs, or other test data.

What changed in this article

• Replaced “designer script” wording with Scenario Editor terminology.
• Added examples of when to use timestamp, random number, GUID-style value, or DPL-driven uniqueness.
• Added a warning to avoid unique strings that break downstream cleanup, reporting, or repeatability.

Validation workflow

1. Choose the uniqueness strategy based on the system under test and storecleanup an unique string, addrequirements.
2. Store the followinggenerated entryvalue inif later steps need to reuse it for validation.
3. Run the designerscenario script:twice and confirm each run creates a distinct value without breaking assertions.

Action:Review Store

note:

Accessor:The dyn1

page

Value:now eval('\"Appvance\" + Math.floor(Math.random()*100)')

Nowexplains the valuedata thatstrategy, isnot savedjust ina 'dyn1',code cantrick befor usedgenerating asa an input to textbox etc.string.

Action: setValue

Accessor: textbox("Building.name"), storedVars["dyn1"]