Which field in an Integration Procedure can use a function like CONCAT or DATEDIFF?

Which field in an Integration Procedure can use a function like CONCAT or DATEDIFF?

• A. In Procedure Configuration, in a Tracking Custom Data value field.
• B. In a Response Action, in an Additional Input value field.
• C. In a Remote Action, in an Additional Output value field.
• D. In a Remote Action, In a Remote Options value field.

Answer: (B)

The ability to use functions like CONCAT or DATEDIFF comes into play when you’re shaping the data that will be returned or passed along in the flow. In an Integration Procedure, the Response Action’s Additional Input value field is the place where you construct those dynamic values that enter the response payload. By using CONCAT you can combine strings (for example, building a display label), and with DATEDIFF you can compute time differences to include in the response. This field is meant for defining inputs that influence what the client receives back, so it’s the right spot for applying such expressions. Other fields aren’t intended for this kind of value construction: the Remote Action’s Additional Output maps data coming from the remote system into the procedure, not for creating new values to send back; the Remote Action’s Remote Options configures how the call is made; and the Tracking Custom Data value field is for logging or metadata, not for computing response values.

The ability to use functions like CONCAT or DATEDIFF comes into play when you’re shaping the data that will be returned or passed along in the flow. In an Integration Procedure, the Response Action’s Additional Input value field is the place where you construct those dynamic values that enter the response payload. By using CONCAT you can combine strings (for example, building a display label), and with DATEDIFF you can compute time differences to include in the response. This field is meant for defining inputs that influence what the client receives back, so it’s the right spot for applying such expressions.

Other fields aren’t intended for this kind of value construction: the Remote Action’s Additional Output maps data coming from the remote system into the procedure, not for creating new values to send back; the Remote Action’s Remote Options configures how the call is made; and the Tracking Custom Data value field is for logging or metadata, not for computing response values.