Table of Contents maxLevel 3
...
You can send Pipeline parameters to Triggered Tasks in the semantic URL form. When the Parameter Key is defined in the Pipeline Settings, the Parameter Value is rendered into a variable name. For example For example, if the variable name is PATH_INFO, then it must be defined as a parameter value in the Pipeline itself. In the following example, we add the following parameters:
...
- The header must be capitalized in its entirety. Headers are case-sensitive.
- Hyphens must be changed to underscores.
- The HTTP custom headers override both the Task and Pipeline parameters, but the query string parameter has the highest precedence.
For example, if you you pass a tenant ID (X-TENANT-ID) in a header, add the parameter X_TENANT_ID and provide a default or leave it blank. When you configure the expression, refer to the Pipeline argument following standard convention: _X_TENANT_ID. In the HTTP request, you add the header X-TENANT-ID: 123abc, which results in the value 123abc being substituted for the Pipeline argument X_TENANT_ID.
| Info |
|---|
Custom response headers are supported for Ultra Task or Triggered tasks invoked using Ground URLs. They are not supported for Cloud invoked Triggered tasks. |
Example
You can set an HTTP header in a Triggered Task by using the Mapper Snap.
To set the header, add a Mapper Snap to the end of the Pipeline.
...