Release Notes > Part I: 2020 > January 2020 > Changed behavior
  

Changed behavior

The January 2020 release of Application Integration includes the following changed behavior:
Improved XML and JSON recognition code in Service Connectors
Effective in the January 2020 release, if the response Content-Type header contains the term application in the first part and the term json in a subsequent part, Application Integration infers the response payload type as JSON. Similarly, if the response Content-Type header has the term text in the first part and the term xml in a subsequent part, Application Integration infers the payload type as XML.
Previously, if the response Content-Type header was application/json, Application Integration inferred the response payload type as JSON. If the response Content-Type header was text/xml, Application Integration inferred the response payload type as XML. If the response Content-Type header did not match the application/json or text/xml values, for example, application/vnd.api#json;charset=UTF-8, Cloud Application Integration treated the response payload as an attachment.
Informatica supports backward compatibility for this changed behavior. Therefore, if you had created a service connector in a previous release in which the response payload was treated as an attachment, after you upgrade to the January 2020 release, the service connector will continue to work as is. However, Informatica recommends that you redesign the service connector to take advantage of the improved content recognition feature. With this feature, you can simplify your service connector to get a normal JSON/XML response instead of working with an attachment.
For more information, see Design.
Support for multiple attachments in Service Connectors
Effective in the January 2020 release, a service connector can handle a multipart response appropriately and create multiple attachments for different response parts. The part related metadata information is available in the attachment properties.
A service connector can also recognize the payload part. The first JSON/XML/Text part is used as the payload. You can extract data from the payload in the output field expressions of the action as you would normally do when you work with non-multipart responses. Note that the selected payload will not be available as an attachment.
In the Output tab, you can use the Get from Attachments option to work with multiple attachments and pass the entire list of attachments to the selected variable except the part used as the payload. The following image shows the Get from Attachments option:
The image shows the Get from Attachments option.
You can also use an expression to work with attachments in service connectors. Several new functions have been introduced to work with attachments. When you open the Expression Editor, you can find the new functions in the Functions tab, under the Output Attachments section as shown in the following image:
The image shows the available functions for output attachments.
When you test a service connector, all the attachments are displayed. You can also download and review them.
For more information, see Design.
Get from Attachment option renaming
Effective in the January 2020 release, in the Get From list in the Output tab, the Attachment option is renamed to Entire Response As Attachment. The following image shows the Entire Response As Attachment option:
The image shows the Entire Response As Attachment option.
Note that only the label name has been changed. The Entire Response As Attachment option preserves backward compatibility. If you had created a service connector with a single attachment in a previous release, it will continue to work as is, and no manual changes are needed.
However, Informatica recommends that you use the new feature of handling multipart responses as multiple attachments to simplify the design. With the new feature, you do not have to manually split attachments. You can also use the processing logic for attachments within the service connector itself instead of doing it within a process. Therefore, you can use a service connector within multiple processes without having to design the processing logic in multiple processes. You can also use the new functions available to work with output attachments.
For more information, see Design.