Actions15
Ticket → Add Journal Entry
AI-generatedSummary
Adds a journal entry to a Matrix42 ticket, service request, or incident using its Expression-ObjectID. The entry includes required comments and type, with optional creator, portal visibility, publication, attachments, template parameters, edit-dialog flag, and type-record GUID.
Inputs
- Authentication — Choose Webservice Token (default) or Basic authentication and configure the matching Matrix42 credentials.
- Ticket ID (required) — Expression-ObjectID of the ticket, service request, or incident receiving the entry.
- Comments (required) — Journal entry content.
- Type Name or ID (required) — Journal entry type, selected from the available types or supplied as an ID. The default type option is None (Default).
- Creator Name or ID — User attributed as the creator. If omitted, Matrix42 attributes the entry to the API user.
- Visible in Portal — Whether the entry is visible in the portal; defaults to false.
- Additional Fields: File IDs — JSON array of file IDs to attach to the journal entry; defaults to an empty array.
- Additional Fields: Is From Edit Dialog — Whether the entry originated from an edit dialog; defaults to false.
- Additional Fields: Parameters — Repeatable name/value template parameters with an optional .NET format string. Matrix42 renders these through localized templates for system-generated entry types; they have no visible effect on a plain comment entry.
- Additional Fields: Publish — Whether to publish the journal entry; the UI defaults to true.
- Additional Fields: Type ID — Optional GUID of a journal entry type record. Usually unnecessary when Type is set; a non-GUID value is rejected.
Output shape
One item containing a success message for each input item.
On success, the operation returns
{ "Message": "Success" }; it does not return the created journal entry. With Continue On Fail enabled, failed input items produce an item containing anerrormessage.