The do-not-send operation prevents a field’s value from being sent further in the flow if the defined conditions are met. Instead of transforming the value, it simply removes it from the request or output.
How it works
- You define conditions (e.g. if equals X, if empty, if contains Y).
- When those conditions are true, the field’s value is suppressed and not passed on.
- If the conditions are not met, the field behaves normally and its value is used.
Examples
| Condition | Input | Result |
|---|---|---|
| equals “test” | “test” | value not sent |
| equals “test” | “real” | “real” (unchanged) |
| is-empty | “” | value not sent |
| always | “12345” | value not sent |
Usage in PalDock
Use do-not-send when you need to:
- Block test or dummy values from being sent to production APIs.
- Avoid sending empty or invalid fields.
- Suppress sensitive data if certain rules apply.
- Prevent optional values from being sent unless they meet specific criteria.
Best Practices
- Combine with conditions carefully as do-not-send removes the value entirely.
- Use for fields where missing values are acceptable to the receiving system.
- For debugging, log which values are suppressed to avoid confusion.
- Be careful when using with required fields; suppressing them may cause an API error.
