Does the Web Services connector support the concept of enrichment?
My use requirement results due to the REST endpoint that we query accounts from returns normalized data (e.g., instead of returning department name, it returns a department ID that must be mapped).
For example, I would execute one REST call to build a map of department IDs to department names, then execute a second REST call to query all employees and use the data from the initial call to translate their associated department ID to a department name before returning the record?
This procedure would be used to facilitate the account listing operation.
You can make the call to get Department names against ID inside After Operations rule and update the response body to replace department IDs with names
You can achieve it by using the Webservice after operation rule. You can define Account aggregation end point with your REST API call to query all the employee data with their department id. Define a after operation rule, in which you can make another rest API call using java code to get all the department id and name information using httpClient or any other client to call the API. Have your rawResponse of employee data updated with the department name based on it’s id.