For the complete documentation index, see llms.txt. Markdown versions of documentation pages are available by appending .md to page URLs.
Skip to content

Record Update Request Tickets

The Update Request ticket type is designed to optimize the process of managing updates for workflows that don't involve the creation of new Standalone or TV Show records within the Fabric catalog.

Similar to our existing ticket types, the Record Update Request ticket offers a dedicated section where users can provide details about their request and assign the task to other users. However, instead of the conventional Record table, it incorporates a Description box and Attachments section. Within these fields, users can articulate the specifics of their update request.

Record Update Request Ticket

ℹ️ Ticket Details

Similar to other ticket types, Record Update Requests in Task Manager offer a comprehensive set of details to ensure efficient management and governance of records within the Fabric entertainment catalog. These ticket details provide valuable information and customization options that enable you to effectively track, prioritize, and assign Record Update Requests.

  • Ticket Name: The ticket name serves as a unique identifier for the Record Update Request. It allows you to easily distinguish and reference specific tickets when organizing and searching for records within Task Manager.

  • Ticket Type: The ticket type signifies that it is a Record Update Request, distinct from other ticket types in Task Manager. By specifying the ticket type, you can categorize and classify tickets based on the nature of the ticket.

🪄 Tip: Ticket Type cannot be changed once the ticket has been created. If you wish to change the Ticket Type, please delete the ticket and create a new a new ticket with the desired ticket type in Record Requests.

  • Status: The status of a Record Update Request indicates its current state within the workflow. You can customize and configure different status options to align with their organization's processes. Tracking the status of tickets provides clarity on the progress and completion of tasks associated with the ticket.

🪄 Tip: Manual configuration of statuses coming soon 👀

  • Priority: The priority attribute allows you to assign relative importance to tickets. Prioritizing tickets helps you focus on high-priority tasks. Priority levels may include options like No Priority, Low Priority, Medium Priority, and High Priority, allowing for flexible task management.

  • Assignee: The assignee refers to you or team responsible for handling the tasks associated with the Record Update Request. By assigning tickets to specific individuals or groups, you can delegate responsibility, facilitate collaboration, and ensure accountability throughout the record governance process.

Record Update Request Details

✍️Ticket Description

Instead of adding records using a Record table like users do for Standalone and TV Show Tickets, the Record Update Request features a Description box where users can add the details of their request. This is useful for tasks that don't involve the creation of new records.

Record Update Request Description

📎Attachments

Users can leverage the Attachments section to include spreadsheets or documents needed for the actions that should be performed as part of that workflow. This ensures that assignees can locate all the necessary information and resources within a single, centralized location, thus significantly enhancing the overall efficiency of the workflow.

Please note: The attachments section will only appear after you have saved the Record Update Request Ticket for the first time.

Record Update Request Attachments

💬 Ticket Activity

At the bottom of each ticket, you can find the Activity section. It has two tabs: Comments and History. The comments section will display all comments logged against the Ticket, and the History tab is where you can find the detailed activity log for the ticket from the point it got created.

Comments
History

We hope you found this article helpful.

If you have a technical problem that this article does not address, go to service desk.

Help us improve the Fabric Knowledge Base by giving feedback here: FKB Feedback Form

Last updated