The replace operation simply replaces the input value with a predefined output value. It does not check the content of the original input. Once the operation is applied, the original value is discarded and the specified output is returned.
How it works
- You define a replacement value in the operation settings.
- Whenever the condition for this modification is met, the original field value is ignored and replaced by the new value.
- The replacement can be:
- A fixed string (e.g. “APPROVED”)
- A numeric constant (e.g. 0, 100)
- A value from another field
Examples
Input | Condition | Operation | Output |
---|---|---|---|
“pending” | equals pending | replace | “approved” |
12345 | always | replace | 0 |
“yes” | string-contains y | replace | “true” |
Usage in PalDock
Use replace when you need to:
- Standardize field values (e.g. replace “pending” or “in_progress” with “open”).
- Map human-readable input to codes (e.g. “yes” → 1, “no” → 0).
- Simplify values for external APIs that only accept predefined constants.
- Normalize inconsistent inputs (e.g. multiple statuses mapped into one common status).
Best Practices
- Combine replace with conditions to only apply it for specific cases (e.g. replace “rejected” with “0”, but leave other statuses unchanged).
- Use replace for simple one-to-one mappings. For more complex substitutions (patterns, partial matches), use Regex-replace
- Be careful not to overwrite meaningful values unintentionally. If no condition is set, all inputs will be replaced.