You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/hyperexecute-projects.md
+23-20Lines changed: 23 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -111,6 +111,29 @@ Within each HyperExecute Project, you can set up one or more workflows. These wo
111
111
112
112
> 📘 Gain a Comprehensive Understanding of how to use connected workflows to create [Test Chains](/support/docs/hyperexecute-test-chains/).
113
113
114
+
**Workflow Variables(Optional) -** Workflow Variables allow you to customize a workflow’s behavior without modifying the underlying YAML configuration. This makes it easy to reuse the same workflow across multiple environments or scenarios by simply providing different values at runtime.
115
+
116
+
#### Key Capabilities:
117
+
- **Define variables at workflow level:** You can add variables when creating or editing a workflow. Each variable requires a key, while the value is optional.
118
+
- **Multiple values per variable:** A key can hold multiple values. The first value is marked as the default, and all values are stored as comma-separated options.
119
+
- **Runtime overrides:** When you run a workflow, a pop-up displays the workflow’s default variables. You can edit them or provide values for empty variables before execution. These runtime changes apply only to the current run and do not overwrite saved defaults.
120
+
- **Case sensitivity:** Variable keys are case-sensitive.
121
+
- **Priority:** Runtime values override workflow-level defaults during execution.
122
+
123
+
#### Example Use Cases:
124
+
- Set `ENVIRONMENT=staging` or `ENVIRONMENT=production` without maintaining separate YAML files.
125
+
- Define `BROWSER=chrome,firefox,safari` at the workflow level, then select or override a browser at runtime.
126
+
- Leave `API_KEY` empty by default and provide it securely at runtime.
127
+
128
+
#### Limits:
129
+
- Up to **100 variables per workflow**.
130
+
- Each variable supports up to **25 values**.
131
+
- Maximum size per workflow’s variable set: **512 KB**.
132
+
- Each value can be up to **500 characters** (excluding commas/spaces).
133
+
134
+
**Access Control:** Permissions for editing workflow variables follow the same role-based access model as secrets.
135
+
136
+
114
137
Click on the **Finish** button and your job will be triggered on the defined day and time.
115
138
116
139
<div className="storylane-iframe">
@@ -153,23 +176,3 @@ In addition to custom projects, HyperExecute supports integration with specializ
With Workflow Variables, you can now customize your workflow execution. This makes it easier to reuse the same workflow across multiple environments and scenarios.
48
+
49
+
-**Workflow-level Variables :** Define reusable variables (e.g., ENVIRONMENT, BROWSER) while creating or editing workflows.
50
+
-**Default & Multiple Values :** Assign defaults or provide multiple values per variable.
51
+
-**Runtime Overrides :** Update variable values at run time without changing saved defaults.
52
+
-**Case-sensitive Keys with clear priority order :** Workflow-level < Runtime-level.
53
+
54
+
> To learn more about Workflow Variables on HyperExecute, refer to our [detailed documentation](/support/docs/hyperexecute-projects/#schedule-your-workflows)
0 commit comments