Workflow Parameters

Parameterization of data inside a workflow is a powerful tool. There are numerous properties in the workflow language that support parameterized values. When a value has parameterized text, the placeholder will be replaced with actual data supplied at runtime. Some of the most common use cases are:

• Navigate URL
• Find patterns
• Match rules
• Input data

This example illustrates parameterized placeholders for endpoint, username and password:

Header:
  Name: Test Login
  ApplicationName: Bank
  RequiresLogin: False
Actions:
- Navigate:
    Url: '{endpoint}/'
- WaitForContent: {}
- Snapshot: {}
- Click:
    Nearest: Any
    Patterns:
    - Sign In
- WaitForContent: {}
- Snapshot: {}
- FindTextInputs:
    Take: 1
    Nearest: Left
    Patterns:
    - 'Username:'
- SendText:
    Text: '{username}'
- FindElementByXPath:
      Patterns:
          - //*[@id="passw"]
- SendText:
    Text: '{password}'
    Overwrite: true
- Click:
    Nearest: Any
    Patterns:
    - Login
- WaitForContent: {}
- Snapshot: {}

In the above example, three new workflow parameters called "endpoint", "username", and "password" will be created. Concrete values for workflow parameters can be supplied when testing a workflow or inside job templates. Parameterization abstracts hard-coded data that may change over time and allows you to use the same workflow with different values without having to change the workflow itself.

Note: If the name of a parameter contains the word "password", the input data will be masked during data entry for that parameter.