Standalone Tickets
These tickets are suitable for managing individual entities that don't have a hierarchical structure, such as Features, Short-form Content, Specials, and Supplemental Content. Standalone tickets provide a simple and focused approach for adding and managing these records in your catalog.

âđïļ Ticket Details
Standalone tickets in Task Manager offer a comprehensive set of details to ensure efficient management and governance of records within the Fabric catalog. These ticket details provide valuable information and customization options that enable users to effectively track, prioritize, and assign tasks associated with standalone records.
Ticket Name: The ticket name serves as an identifier for the standalone ticket. It allows users to easily distinguish and reference specific tickets when organizing and searching for them in Task Manager.
Ticket Type: The ticket type signifies that it is a standalone ticket, distinct from other ticket types in Task Manager, such as TV show tickets. By specifying the ticket type, users can categorize and classify tickets based on the nature of the records they contain.
Status: The status of a standalone ticket indicates its current state within the workflow. Users 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 standalone records.
Priority: The priority attribute allows users to assign relative importance to tickets. Prioritizing tickets helps users focus on high-priority tasks, ensuring that critical record creation, updates, and edits are addressed promptly. The options are: No Priority, Low Priority, Medium Priority, and High Priority.
Assignee: The assignee refers to the user responsible for handling the tasks associated with the Standalone ticket. By assigning tickets to specific individuals, users can delegate responsibility, facilitate collaboration, and ensure accountability throughout the record governance process.

ð§Đ Ticket Table
In standalone tickets, users have the ability to add records to the Standalone Ticket Table, which serves as a central repository for managing individual records within the ticket. When adding records, users are required to fill in mandatory fields to ensure comprehensive data for each record. These mandatory fields may include information such as Release Year, Primary Language, Country of Origin, and more, depending on the specific requirements from the client.
To add records, users have two options: manual entry and bulk upload.
Manual Entry: Users can manually add records by clicking on the "Add Record" button, which brings up forms where they can input the necessary details for each record. This allows for a more hands-on approach, providing users with the flexibility to input data directly into the forms and ensure accuracy.
Bulk Upload: For streamlined and efficient record addition, users have the option to upload records in bulk using the "Upload Record Sheet" button. Fabric provides templates in the form of CSV (comma-separated values) or XLS (Excel spreadsheet) files to facilitate the bulk upload process. Users can populate the template with the relevant record information and then upload the file to Task Manager, saving time and effort when dealing with multiple records.

â Record Table Bulk Actions
Introducing Record Table Bulk Actions in your ticket management toolbox! Now, you have the power to manage multiple records effortlessly using the checkboxes in the table and the new Actions Menu. Let's take a look at what you can achieve:
Remove from Ticket: Tidy up your ticket by removing multiple records at once. Just select the checkboxes, choose this action, and voilà â they're gone!
Add to Collection: Want to associate your selected Records to a Franchise or Collection? You got it! Choose the records, and add them to a Collection or Franchise.
Remove from Collection: Records linked to a Collection or Franchise? You're in control. Remove the selected Records from the associated Franchise or Collection.
Move to New Ticket: Got records that need a new home? Select them, pick this action, and watch them settle into a fresh ticket.

ð Standalone Forms
Standalone forms in Task Manager allow users to add records to the standalone ticket table by filling in the mandatory fields specific to selected record categories like Features, Specials, Supplemental Content, and Short Form Content. These forms are preconfigured and pull in information from client managed lists known as Data Sets. While currently the fields are predefined, future integration with Record Builder will enable users to customize their own fields. Additionally, the Record Title feature suggests existing records as users type, helping them avoid duplication. Standalone forms streamline the process of adding records and contribute to data consistency and accuracy in the Fabric entertainment catalog.


ðïļ Standalone Forms - Tasks Manager 2.0
Task Manager 2.0 no longer uses separate forms for creating or editing records. Instead, it introduces an inline-editing table that allows users to edit records directly within the grid, making the process faster and more efficient. The table supports all field types, including Multi-Select, Select, Date, Year, and more.

ð Attachments
You can use this Ticket Section to upload files (Excel, PDF, Word, EML, MSG and CSV are supported!). It helps give more context and information within Task Manager, and can be used to store a copy of the file to use the Bulk Upload functionality.

ðŽ 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.


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

