Call Transformations
Call Transformations now offers an updated experience for discovering and applying Boomi-developed pre-processing and post-processing policies to API endpoints. Policies handle tasks such as authentication, token validation, content filtering, header injection, IP routing, payload transformation, and caching, and can be applied at two stages of an API request: before the request reaches the backend (pre-processing) and after the backend responds (post-processing).
For example, when a developer makes an XML-RPC call to the client API servers that require REST-based API requests, the Traffic Manager translates the request to REST using specific translation logic. Protocol translation can make the API appear more robust by supporting multiple protocols when, in fact, it only supports a single protocol. Other common use cases include content injection, filtering, and transformation.
ASR (Application Service Registry) services set up in Boomi Cloud API Management will only be available in ASR Picker if they are marked Private. The Services defined for Post methods with no variable set on the path can only be successfully selected on the Call Transformations page. This means that query parameters cannot be added, and none of the endpoint's path values can be dynamically populated at runtime. For details on which EAV and standard fields to include in the ASR request, refer to Analysis on EAV for inclusion in ASR Request.
Legacy vs. New UI
Call Transformations is available in two UI experiences, depending on whether you are an existing or new customer. The following table compares the key differences between the two UI experiences.
| Capability | Legacy UI (Manual Entry) | New UI (Policy Picker) |
|---|---|---|
| Policy entry | Manual text entry of adapter class name. | Searchable dropdown picker. |
| Parameter fields | Freeform pre-inputs and post-inputs. | Auto-populated configuration fields based on the selected policy. |
| Inline guidance | Policy document — you had to look up policy names, adapter class names, and parameter syntax in the Help Docs before configuring a policy. | Help text and field descriptions are displayed inline for each parameter. |
| Validation | None | Mandatory field enforcement; format validation for URLs, numbers, and JSON. |
| Chaining | Manual configuration required. | Enforced automatically. |
| Applies to | Existing configurations. | Default for new customers; available on request for existing customers. |
The new UI is enabled by default for new customers. Existing customers can opt in on request by contacting the Boomi Account Representative.
How Call Transformations work
When the Traffic Manager receives an API request, it runs any configured pre-processing policies in order before forwarding the request to the backend (host API servers). After the backend responds, it runs post-processing policies in order before returning the response to the client API servers.
Legacy UI: Manual chaining
In the legacy UI, chaining multiple policies required manual configuration. You had to explicitly add a chaining processor adapter (Mashery_Proxy_Processor_Chain) in the Processing Adapter field and configure each policy in sequence. Not all policies support chaining; refer to Porting and Chaining to verify compatibility before configuring policies. For a full overview of chaining types and adapter compatibility, refer to Chaining Processors.
New UI: Automatic chaining
In the new UI, you do not need to add a chaining policy manually. When you attach multiple policies to a single endpoint, Cloud API Management automatically chains them in the order you configured them and enforces chaining rules to prevent invalid policy combinations.
Legacy UI field reference
The legacy Call Transformations UI page for an endpoint includes the following fields:
Processing Adapter
Specifies the class file of custom logic that the Traffic Manager uses to perform pre-processing or post-processing of an API call.
Perform Pre-processing
Enables the Traffic Manager to process the API request before forwarding it to the host API servers. When enabled, the Traffic Manager applies custom processing logic to an API call before sending the request to the client API servers.
Data to make available for pre-processing
This field configures the Traffic Manager to add new values or modify the existing values within the incoming API call before passing it to the client API servers.
Perform Post-processing
Enables the Traffic Manager to process the API response from the host API servers before returning it to the client. When enabled, the Traffic Manager applies custom processing logic to responses from the client API servers.
Data to make available for post-processing
This field configures the Traffic Manager to add new values or modify the existing values within the incoming API call before passing it to the client API servers.
New UI field reference
The new Call Transformations UI page for an endpoint includes the following fields:
Pre-Processing and Post-Processing
Each Pre-Processing and Post-Processing panel has its own Add Policy. After you click Add Policy, the New Policy section opens, where you can attach policies.
Policy Type
A searchable dropdown that lists available policies inside the New Policy section. Selecting a policy type auto-populates the configuration fields below it, displays a description of the policy, and indicates whether it supports pre-processing, post-processing, or both.
Configuration fields
Fields that appear after you select a policy type. The fields vary by policy and may include text input fields. You can hover over the info icon for each field to view example values, or refer to the available Policy section for individual policy configuration value examples. Required fields are marked and must be completed before you can save.
Next Steps
Configure Call Transformations for an endpoint depending on whether you are an existing or new customer:
-
If you are a new customer, refer to Configuring Call Transformations in Policy UI.
-
If you are an existing customer using the legacy UI, refer to Configuring Call Transformations in Legacy UI.
