Use Relative File Paths for Scenario Editor Uploads
Use Relative File Paths for Scenario Editor Uploads
Use relative file paths only when the execution environment has a controlled project structure and the files are deployed consistently to the Test Node or execution host.
Recommended guidance
- Prefer approved test-data locations over ad hoc local paths.
- Document the base directory used to resolve relative paths.
- Keep upload files versioned with the test assets when appropriate.
- Avoid paths that depend on a specific user profile or workstation.
Validation workflow
- Place the file in the approved project or execution data location.
- Reference the file using the documented relative path.
- Run a small validation execution on the target Test Node.
- Review output if the file cannot be found or uploaded.
Last updated: September 20, 2026