User Interface Overview

BigFix Runbook AI lets users to act on to unresolved open tickets, keep a log of archived tickets, and view key performance indicators and metrics on the dashboard. The user interface consists of four main menus: Tickets, Ticket Logs, Dashboard, and Knowledge. Users can manage tickets, execute runbooks, view ticket logs, search knowledge repositories, and customize the dashboard.

BigFix Runbook AI allows users to respond to unresolved open tickets, keep a log of the archived tickets closed by BigFix Runbook AI, and automatically update the dashboard to let users view key performance indicators and metrics at a glance.

The user interface comprises of four main menus:

Tickets

This section describes the recommended steps to view or manage a ticket. On occurrence of an incident or if an IT product or service is required, the user submits a ticket that is considered as the incident documentation or the service request.

To manage tickets, go to main menu bar and click Actions->Tickets. A drop-down menu appears with the following options:

Figure 1. Figure 6 - Manage Tickets

Actionable Tickets

This section describes how unresolved open tickets in BigFix Runbook AI are executed in either Auto or Manual mode.

To view or manage actionable tickets,

  1. Click Actions->Tickets on the main menu bar, and then click Actionable Tickets.
  1. The Actionable Tickets screen appears, displaying the summary and status of all tickets. It also lists the in-progress or failed tickets, either auto-executed or manually executed, in the following tabs:
  • All Tickets: Lists the organization’s tickets, both assigned and unassigned.
  • My Tickets: Lists only the tickets assigned to the current user, including in process or failed tickets.
Figure 2. Figure 7 - Actionable Tickets

All Tickets

This section describes the organization-specific tickets available in BigFix Runbook AI and how to manage them.

To view and use the All Tickets tab, perform the following steps:

  1. Select an Organization and then select a Module .
  1. The specific tickets for the selected organization and module appear in a tabular view.
  1. The All Tickets tab is categorized into the following tabs:
Table 1. Table 3 - All Tickets Sub-sections
Tab Description
Tickets

Lists the tickets that are a part of the BigFix Runbook AI queue and must be executed by BigFix Runbook AI

Lists the consolidated tickets from the Assigned and Unassigned tabs

Assigned

A subset of the Tickets tab; lists the tickets allotted for either automated or manual execution

Shows the allocation status of a ticket and the runbook initiated for it

Unassigned

A subset of the Tickets tab; lists the tickets pending for allocation

Enables the current user to self-assign any ticket by selecting the most relevant runbook suggested and then initiating execution

Figure 3. Figure 8 - All Tickets
  1. Each tab includes columns with the following values:
  • Ticket Details: Provides information about a request, including the ticket description, summary, identification number, and creation date
  • Information: Includes Guide and Related Tickets links
  • Runbook: Auto fills details based on the selected tab:
  1. In case of Assigned Ticket, the user and the runbook operating on the ticket are displayed.
  2. In case of Unassigned Ticket, if runbooks with a confidence score above the threshold are available for a ticket, then the Select Runbook button appears in the same column. This enables the user to select the desired runbook and acknowledge the ticket. For runbook execution details, see Runbook_Execution.
Figure 4. Figure 9 - Un-Assigned Tickets
  • Action: It enables the Release button in specific circumstances:
  1. If the execution criteria for a ticket, as detailed in the Runbook_Execution, are not met, a Release button appears next to the ticket so the user can release the ticket from the BigFix Runbook AI queue.
  2. For manual execution, the Release button is always active. Click Release to follow the steps as configured in the environment. See Runbook_Execution for detailed information.

The Action column remains unavailable in the Assigned Tickets tab.

Figure 5. Figure 10 - Ticket Details

Runbook Execution

To execute the runbook for a ticket, perform the following steps:

  1. On the All Tickets tab, click the Un-Assigned tab to filter tickets based on user allocation or identify the ticket to be executed from the Tickets tab.
  1. To initiate ticket execution in the BigFix Runbook AI queue, first, collect the necessary ticket data from the IT Service Management (ITSM) tool.
  2. The following table describes the execution status for each activity.
    Figure 6. Figure 11 - All Tickets
    1. For a condition where multiple runbooks above a defined threshold are available against a ticket, a Select Runbook button appears in the Runbook column. However, if the appropriate runbook is not configured, the Release button is enabled so the ticket can be released from the BigFix Runbook AI queue.
    2. Click Select Runbook.
    Figure 7. Figure 12 - Select Runbook and Release Options
    1. A pop-up window displays the summary and description of the tickets and the list of runbooks in descending order of confidence score.
    Figure 8. Figure 13 - Summary and Description Options
    1. In addition to the confidence score, the SME Approved column displays the result of SME validation against the runbooks. Both parameters help the user to identify the runbook for execution.
    2. After the runbook is identified, click Runbook Name to expand the selected row.
    Figure 9. Figure 14 - Select Runbook
    1. This displays the runbook description and parameters for the selected runbook. These parameter values are retrieved from the ticket. The user may select the runbook with the highest confidence score or the one recommended by the SME.

    If the values are available, then they are referenced from the ticket description, or the default values are provided. The user can either retain these values or change them.

    1. Click Execute to start runbook execution for the selected ticket.
  1. On successful initialization of the execution, a confirmation dialogue box appears.
Figure 10. Figure 15 - Runbook Initiation Confirmation
  1. Simultaneously, the following updates happen in the All Tickets tab:
  • In the Tickets and Assigned tabs, the ticket is marked as Owned By, replacing the Select Runbook button with text specifying the runbook that is being initiated for execution. The username appears next to Owned by under the tab.
  • If the user selects Assigned in the All Tickets tab, then the same ticket is added in the Tickets and In-Process tabs under the My Tickets tab.
Figure 11. Figure 16 - Runbook Execution
  • The Logs grid displays the ticket status as Initiated.
Figure 12. Figure 17 - Runbook Execution
  • The Assigned Ticket remains unavailable for allocation by another user unless the Owned by user releases the ticket from their queue.

This section describes how to retrieve the relevant knowledge for a ticket, from different sources, for a user in a single view. The sources from where this information will be retrieved depend on the configuration in your environment.

To use the Guide , perform the following steps:

  1. Click Guide for the ticket for which you want to view the information.
Figure 13. Figure 18 – Guide
  1. The Knowledge Repositories screen appears with the most relevant information specific to the ticket from across the configured sources.
Figure 14. Figure 19 - Knowledge Repositories
Capture
  1. BigFix Runbook AI can fetch data from the Collections of an organization, and if the data is not available in Collections , then it retrieves results from Google.

Related Tickets

This section describes the bucket in which the ticket resides and lists all tickets in that bucket.

  1. Click Related Tickets for the ticket for which user wants to view the related tickets.

    The Bucket Details window appears.

Figure 15. Figure 20 – Related Tickets
  1. User can view all the tickets available in the selected bucket, including their description and the associated runbook details.
  2. Click EXPORT TO CSV to download the bucket details.

My Ticket

This section describes how to manage the tickets assigned to the current user and available in the BigFix Runbook AI queue.

To view and use the My Ticket tab, perform the following steps:

  1. Select an Organization from the drop-down list and then select a Module .
  1. The organization and module-specific ticket assigned to the current user appears in a tabular view.
Figure 16. Figure 21 - My Tickets

The My Tickets tab is categorized into the following tabs:

Table 2. Table 5 - My Tickets Sub-Sections
Tab Description
Tickets
  • Lists the tickets that are a part of the BigFix Runbook AI queue and assigned to the current user for execution
  • Lists the consolidated tickets from the In-Process and Failed tabs
In-Process
  • A subset of the Tickets tab; lists the tickets assigned to the current user for which execution is in process
  • Displays the allocation status of a ticket and the runbook being initiated for it
Failed
  • A subset of the Tickets tab; lists all the tickets assigned to the current user that have failed execution
  • Enables the current user to release the failed tickets from BigFix Runbook AI.

After successful execution, tickets are automatically moved from the BigFix Runbook AI queue. The tickets are marked either as resolved or assigned to another group in the ITSM tool based on how the runbook workflow execution is configured in your environment.

  1. Each tab includes columns with the following values:
  • Ticket Details: Provides information about a request, including the ticket description, summary, identification number, and the creation date. Selecting a ticket’s Incident ID displays the ticket detail in the Logs tab.
  • Information: Includes a Guide link that retrieves the most relevant knowledge for a ticket from across different sources in a single view, enabling you to resolve the ticket.
  • Runbook: Displays the runbook being selected and executed.
  • If the ticket execution is In-Process, the Runbook button is disabled.
  • For Failed ticket execution, the Runbook button is enabled. Clicking the Release button displays a window and lists all the relevant runbooks by their confidence score. Users can perform any of the following steps:
  • View the last executed runbook with the parameters and run the same runbook again.
  • Select a new runbook to execute.
  • For more details, see Runbook Execution.
  • Action: This column is available in the Tickets and Failed tabs. The Release button is displayed for the tickets with Failed execution, allowing the user to release the tickets from the queue.

The Action column remains unavailable in the Assigned Tickets tab.

  • The colored bar on the left of the Tickets tab displays the current ticket execution status. An orange bar indicates an In-Process execution and a red bar indicates a Failed execution.

Clicking Release either releases the ticket to the All Tickets queue (keeping it in the BigFix Runbook AI queue but removing the allocation of the current user) or to some other group in the ITSM tool based on configured rules. In either case, the allocation of the current user will be removed.

  1. In the Ticket or In-Process tabs, clicking an incident number displays the ticket-specific log in the Logs tab, which provides a runtime update for the selected ticket with the following details:
  • Parameter used for execution
  • Start date of execution
  • End date of execution
  • Execution status
  • Interaction ID provided by the underlying RBA tool
Figure 17. Figure 22 - My Tickets

The logs displayed are ordered by date and time. The most recent update appears on the top of the grid.

Logs

This section describes near real-time status updates of ticket execution initiated by the user.

To view a ticket log, navigate to the Log tab appearing below the All Tickets and My Tickets tabs. This displays the activity log for all tickets being executed with the following details:

Table 3. Table 6 - Log Fields
Name of the log values Description of the log values
Incident Number This is a unique, auto-generated number for the incident ticket. It is preceded with an INC prefix (e.g.INC0000001) of the logged ticket.
Interaction ID Unique ID generated by the underlying RBA tool.
Runbook Name Name of the runbook executed for the logged ticket.
Log Date Time Date and time of the logged ticket.
Runbook Status Status of the runbook selected for the ticket.
Status Reason Displays the ticket specific logs including the field values. Value wrapped to multiple lines within the column. To access the related record, click View More.
Attachment Displays any relevant attachment for the ticket.

The logs displayed are listed by their date and time. The most recent update is available on the top of the grid.

Figure 18. Figure 23 - Logs view

Auto Execution View

This section describes the auto-execution process for unresolved, open tickets in the BigFix Runbook AI queue. It displays the summary and status of all automatically executed tickets including in process or failed tickets.

To view tickets in auto-execution view, perform the following steps:

  1. On the main menu bar, click Actions->Tickets, and then click Auto Execution View.
  1. Select an Organization from the drop-down list and then select the Module for organization and module-specific tickets.
  1. The Auto Execution View screen is displayed listing the selected organization and module-specific tickets under the My Tickets tab.
Figure 19. Figure 24 - Auto Execution View: My Tickets
  1. The My Tickets tab is categorized into the following tabs:
Table 4. Table 7 - My Ticket Subsections
Tab Description
Tickets
  • Lists all tickets available for auto-execution in the BigFix Runbook AI queue
  • Displays a consolidated list of tickets from the In-Process and Failed tabs
In-Process
  • A subset of the Tickets tab
  • Lists the tickets available for auto-execution
  • Shows the allocation status of a ticket in the queue and the runbook being initiated for it
Failed
  • A subset of the Tickets tab
  • Lists all the auto executed tickets with failed execution that can be moved out of the BigFix Runbook AI queue using the Release button

Ticket Log

Users can view the comprehensive log of all the activities for a ticket, including updates and notifications, whether it is by a user or by BigFix Runbook AI.

To view the ticket logs, perform the following steps:

  1. On the main menu bar, click Actions->Tickets and then click Ticket Logs .
  1. The Ticket Logs screen appears.
Figure 20. Figure 25 - Ticket Logs
  1. Select an Organization from the drop-down list and then select the Module .
Figure 21. Figure 26 - Organization and Module

This lists the ticket log for organization and module-specific tickets in the following tabs.

  • Current: Lists the log details of the tickets available for execution in the selected organization, including the ticket number, current state, acted by, queued on, and last modified information.
  • Selecting a Ticket Number displays the detailed log information including logged on and logged by details, action was taken on the ticket, the reason for the action taken, and remarks.
Figure 22. Figure 27 - Ticket Logs
  • Archived: Lists the log details of the ticket that are marked as closed in the selected organization, including the ticket number, current state, acted by, queued on, and last modified information.
  • Selecting a Ticket Number displays the detailed log information including logged on and logged by details, action that was taken on the ticket, the reason for the action taken, and remarks
  1. Users can export the log details using the Export to Excel button above the Log Details view.

All fields marked with an asterisk (*) are mandatory.

Knowledge

This module allows users to search across the organization’s internal repositories such as SNOW and external domains such as Stack Overflow and Ubuntu.org. You can also perform an advanced search by applying conditions followed by the search term and Boolean condition (OR, AND, and so on) for more refined results.

Knowledge Search

This section describes how to use the advanced, organization-specific configuration to retrieve results from the knowledge repository.

To use Knowledge Search, perform the following steps:

  1. On the main menu bar, click Advance Configuration->Knowledge, and then click Knowledge Search.
  1. The Knowledge Search screen appears.
Figure 23. Figure 28 - Knowledge Search
screenshot1
  1. Select the Organization from the drop-down list, then type the search string in the Search box, and then click . The search results are displayed in a grid below.
Figure 24. Figure 29 – Search
C:\Users\saloni.malik\AppData\Local\Microsoft\Windows\INetCache\Content.MSO\67AC1766.tmp
  1. For more advanced search , instead of clicking , click the Advance Search button.

An Advance Search window is displayed for users to fill in the information and retrieve results.

Figure 25. Figure 30 - Advance Search
screenshot3
  1. Advance Search allows users to restrict search results by applying conditional filters or define the order of the search results.

User can add any number of custom conditions to refine their search for more relevant results.

  1. Click to start a search. After the search filter is applied, any results that appear will align with the conditions specified in the Advance Search box.
Figure 26. Figure 31 - Advance Search Results

All fields marked with an asterisk (*) are mandatory.

Dashboard

The dashboard provides a complete view of the system in your environment and helps spot trends in real-time. Each dashboard User Interface (UI) element can instantly provide additional data insights, including a platform to create reports using the preconfigured widgets available on the dashboard.

To manage the dashboard, perform the following steps:

  1. On the main menu bar, click Reports->Dashboard. The Dashboard screen appears.
Figure 27. Figure 32 – Dashboard
  1. Dashboard filters allow users to narrow the range of one or more reports on the active Dashboard tab. This filter lets you select a specific time frame, such as last month, this month, last quarter, or a range of dates.
  2. To configure a specific report, select the Organization from the drop-down list, then select the time frame from the drop-down list of the Period, and then select the date range in the From Date and To Date fields.
Figure 28. Figure 33 – Period
  1. Click Save Widget. These selections will recompile the data that appears in any report that is associated with the date filter. All data beyond the selected range is excluded.
Figure 29. Figure 34 – Widget
  1. You can use predefined widgets under the Dashboard Filters tab to add new widgets and modify or remove existing widgets from the organization.
Figure 30. Figure 35 - Dashboard Filters
Graphical user interface, application Description automatically generated

Configure Widgets

Dashboard customization is available for users with the appropriate privileges, such as Organization Admin. The dashboard customization can be configured for different user roles as required by the administrator. To add more reports or data in a dashboard, you can define multiple widgets for a selected organization.

To add a widget to an organization, perform the following steps:

  1. On the Dashboard screen, select an Organization from the drop-down list.
  1. If there are any configured widgets in the selected organization, it appears below the Dashboard Filters tab.
  1. Click on the Dashboard Filters tab to list the predefined widgets.
Figure 31. Figure 36 - Select Organization
C:\Users\saloni.malik\AppData\Local\Microsoft\Windows\INetCache\Content.MSO\28456598.tmp

Preconfigured widgets list all the KPIs so that users can customize their view.

  1. Select the checkboxes next to the widgets you want to include, then select the time frame from the drop-down list of the Period, and then select the date range in the From Date and To Date fields and then click Save Widget.
Figure 32. Figure 37 - Select Widgets
C:\Users\saloni.malik\AppData\Local\Microsoft\Windows\INetCache\Content.MSO\55987F7A.tmp

To delete a widget from the selected organization, clear the widget checkbox selection, and then click Save Widget to save the changes.

The added widgets are displayed on the dashboard.

Figure 33. Figure 38 - Report

Users can view drill-down details of any report appearing on the widget

To view the drill-down report, perform the following steps:

  1. Click any visualization to view the drill-down report.
Figure 34. Figure 39 - Select Dataset

The detailed drill-down report is displayed.

Figure 35. Figure 40 - Drill Down Report

Each widget can be resized using the following steps:

  1. Point at any corner of the selected tab with the mouse pointer. When the pointer changes into a double-headed arrow, hold down the primary mouse button and drag the corner in or out to resize the window. Release the mouse button to stop resizing the window.
  2. Click Save Changes to save the changes.

Each widget can be moved using the following steps:

  1. Click a blank portion on the navigation bar of the selected tab.
  1. Hold down the primary mouse button and then drag the mouse pointer to the place on the screen where you want the tab. After you move the mouse pointer to the position on your screen where you want the taskbar, release the mouse button.
  2. Click Save Changes to save the changes.

The navigation bar on each widget contains the following menus.

Table 5. Table 8 - Navigation Bar Functions
Tabs Name and Function
/ / / Change the view of widget to bar/grid/pie/doughnut.
Refresh the data in a widget.
Remove a widget from the selected organization’s dashboard.
Export the data in a widget to PDF or CSV format.

Help

This page helps the user to locate the necessary documents for better understanding of the tool as well as get the details of the components being running in BigFix Runbook AI.

  1. On main menu bar, click on Help. The below page appears:
Figure 36. Figure 41 - Help

It has two tabs:

  1. Documents
  1. On Documents tab, it shows all the required documents needed for better understanding of BigFix Runbook AI:
    • Configuration Guide
    • Installation Guide
    • Integration Guide
    • Introduction Guide
    • User Guide
  1. To view any document, click on icon . It will open the document in new tab.
  2. To download any document, click on icon .
    1. Component Details
  1. This tab displays all the components running on BigFix Runbook AI along with the server Host/IP on which component is running, the name of the component, component code, the version of BigFix Runbook AI currently running, the service name with which component is installed, the actual URL along with port on which component is running and the LB URL, if exists, for the component.
Figure 37. Figure 42 – Help (Cont.)