The HTTP response is a regular one containing JSON data (unlike the request).
It will list the references to the created activity logs in the integration target. BMC Helix Digital Workplace Catalog will store these references in order to avoid duplicates during polling.
{ "created": true, "createdActivityLogs": [ { "id": "AB4F0F2A-C869-46A6-A6B2-DD1DDAAD4B72", "activity": { "id": "DFG234FD4DFQAAA00", "type": "Ticket" } } ] }Note that the connector may choose, in some cases, to generate several "activity log" entries in the integration target. This can be useful if the integration target does not support attachments and comments together as single entities. In that case, the connector will return as many references as necessary in the "createdActivityLogs" property.
{ "created": true, "createdActivityLogs": [ { "id": "AB4F0F2A-C869-46A6-A6B2-DD1DDAAD4B72", "activity": { "id": "DFG234FD4DFQAAA00", "type": "Ticket" } }, { "id": "24A54CAF-5461-4FBF-8450-526B7F961B07", "activity": { "id": "DFG234FD4DFQAAA00", "type": "Ticket" } }, { "id": "562E1D19-FE76-45E5-999B-4080688DE8AC", "activity": { "id": "DFG234FD4DFQAAA00", "type": "Ticket" } } ] }