Create Unique Strings in Scenario Editor Scripts

Last reviewed: 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 cleanup requirements.
2. Store the generated value if later steps need to reuse it for validation.
3. Run the scenario twice and confirm each run creates a distinct value without breaking assertions.

Review note: The page now explains the data strategy, not just a code trick for generating a string.

Last updated: September 28, 2026

If you have feedback on this topic, contact documentation@appvance.ai.