Start by executing a multipart/form-data request on the ticket. In the Tickets section the array of one ticket object with the ticket updates includes the change group that has the requirements for the ticket change. The attachmentSet field inside the change group declares what parts to pull in as attachments for the ticket. The brackets in the name of the attachment part ("INVENTORY_FILE[]") allow you us to have multiple parts with the same name, so you can embed up to five attachments in one ticket change.
To retrieve an attachment, you must provide the ticket ID, change ID, and attachment ID. These values can be obtained using the above example, Determine what attachments are available with a ticket:.
Version : 14.0
BasePath : /api/user_notifications
Delete a set of user notifications
|
notificationData required |
|
NotificationIDs optional |
Mark a set of user notifications as read
|
notificationData required |
|
NotificationIDs optional |
Retrieves user notifications for the logged in user
|
UserNotifications optional |
< user_notification > array |
|
body optional |
|
|
new optional |
|
|
notification_id optional |
|
|
notification_type optional |
|
|
time_started optional |
|
|
timestamp optional |
|
|
title optional |
Quest Software creates technology and solutions that build the foundation for enterprise AI. Focused on data management and governance, cybersecurity and platform modernization, Quest helps organizations address their most pressing challenges and make the promise of AI a reality. Around the globe, more than 45,000 companies including over 90% of the Fortune 500 count on Quest Software. For more information, visit www.quest.com or follow Quest Software on X (formerly Twitter) and LinkedIn.
Technical support is available to Quest customers with a valid maintenance contract and customers who have trial versions. You can access the Quest Support Portal at https://support.quest.com.
