Change log for the SAP Hybris Marketing Cloud - Content Management System Integration package

1.0.0 First version delivered with
+ An integration flow template, which can be used to develop an integration flow to integrate a Content Management System (CMS) or a Digital Asset Management (DAM) system with SAP Hybris Marketing Cloud system.
+ A sample implementation, using the Integration Flow template to integrate with OpenText DAM system.

1.0.1 Released a patch
+ The version mismatch with the Generic Splitter component was corrected in the com.sap.mkt.opentext.integration integration flow.

1.1.0 Released with the following enhancements for 1805 cloud release
+ The artifact com.sap.mkt.opentext.integration is renamed as OpenText DAM system Integration
+ The artifact com.sap.mkt.cms.integration.template is renamed as Template for CMS or DAM Integration
+ The integration flow template and the sample integration flow for OpenText are simplified by reducing the number of endpoints from two to one, which reduces the configuration efforts in SAP Hybris Marketing. The integration flows have been restructured by using local integration.
+ The Integration Flow developed from the previous template will continue to function, if the endpoint IFLOW_SEARCH_ENDPOINT invoked with HTTP method HEAD or HTTP method GET without keyword_query header returns the HTTP status code 200. The HTTP status code 200 indicates successful connectivity with the DAM system.

1.2.0 Released with the following enhancements for 2005 cloud release
+ The integration flow template and the sample integration flow for OpenText are enhanced with one more endpoint to read the search sugsestions.
+ The Integration Flow developed from the previous template will continue to function, if the endpoint IFLOW_SEARCH_ENDPOINT invoked with HTTP method GET with keyword_suggestions header returns the HTTP status code 200. The HTTP status code 200 indicates the request was successful and fetches the suggessted keywords from the DAM system.