The following consoles provide access to all or a part of
Some content is unavailable due to permissions.
:
The following illustration shows how these consoles integrate with
Some content is unavailable due to permissions.
and other applications.

From the Requester console, IT users can submit incident requests directly to
Some content is unavailable due to permissions.
. The integration with the Requester console:
- Uses the Requester console to define incident requests.
- Updates incident request information using the Work Info record.
- Includes an interface from the incident request to the request that is stored in the Requester console.
- Updates the status of the request to the appropriate status, and makes Work Info entries visible.
Using the Overview console, service desk workers who fulfill many different roles can view incident requests that are assigned to them through
Some content is unavailable due to permissions.
, and additional work assignments that come to them through other applications with which
Some content is unavailable due to permissions.
integrates:
The
Some content is unavailable due to permissions.
console is the main console for
Some content is unavailable due to permissions.
. It provides service desk workers with a single point from which they can generate incident requests, monitor the progress of incident requests as they move through their lifecycle, and record work that was performed while solving the incident request.
Some content is unavailable due to permissions.
integrates with
(see Home) . (For information about this integration,
see Creating requests from fulfillment applications .) When is installed, the Request Entry console replaces the Requester Console. See
Configuring incident rules for information about configuring
Some content is unavailable due to permissions.
to generate a service request every time that an incident request is created.
Users can view service request details from the Request Entry console in . You can also view service request details from the Incident Management Console by choosing Functions > View REQ<number>. For more information, see Viewing details of a service request associated with a work order .
Some content is unavailable due to permissions.
uses the Cost module to track costs associated with incidents. The integration uses the common cost creation dialog box that the Cost module provides. Fields on the Incident Request form integrate with Cost module forms to show cost data related to an incident.
| |
---|
Some content is unavailable due to permissions. console header |
---|
| |
| Opens the Search feature. |
| |
Breadcrumb navigation controls | - Back—Takes you back one link in the breadcrumb trail.
- Forward—Takes you forward one link in the breadcrumb trail. Forward is visible only if you have returned to a record on the breadcrumb trail that you previously viewed.
- Drop-down menu—Contains links to all the records that you have viewed from the current incident request, including records that might not currently be visible in breadcrumb trail.
- Home icon—Takes you to the IT Home page.
|
| Updates the data in the tables. |
| |
- Show
- Filter By
- Magnifying glass icon
- By Role
- More Filters
| The Show, Filter By, and By Role fields combine to control which incident request records appear in the Incidents table. |
|
---|
View Broadcast or New Broadcast | Opens the broadcast dialog box where you can view, create, modify, and delete broadcasts. When there are unread broadcast messages, this area displays the message New Broadcast, along with new messages. When there are new broadcast messages, the area also turns red. If you open the console with no new broadcast messages, but the View Broadcast link is red, open the Application Preferences dialog box and make sure that a Console View preference has been selected. For information about how to view and select the Console View preference, see Selecting your application preferences. |
| Contains incident request metrics. The numbers relate to the selection in the Show field. For example, if the Show field contains Submitted by me, the metrics that appear in this area show the open, unassigned, unacknowledged, and breached incidents that were submitted by you. The count categories are: - Open—The requests with a status of Assigned, Pending, or In Progress.
- Unassigned —The requests that are not assigned to an individual.
- Unacknowledged —The requests with a status of Assigned or Pending. A request is no longer considered unacknowledged after you change its status to In Progress.
- Breached —The requests that have exceeded one or more service level agreements (SLAs). For example, if the SLA requires all password reset requests to be acknowledged within 60 minutes and there is a password reset request that still has a status of Assigned after 61 minutes, that request would appear in the Breached count.
Important: - If you set up a specific Company from your application preferences, the incident metrics that appear in the Counts area are restricted to the specific Company that you selected.
The total number of Unassigned, Unacknowledged, and Breached requests might or might not equal the count for Open. For example, consider a situation where you have the following counts: - Open—19
- Unassigned—0
- Unacknowledged—17
- Breached—6
In this case, the number of Unassigned and Unacknowledged records plus the number of breached records totals more than the number of open records. That's because, 6 of the 19 open requests are in breach of the SLA.
|
| Use the following links in this area to perform the actions described: |
| Contains links to other BMC applications, consoles, and modules. The contents of this area depend on what other applications and so on are installed. Click the double-greater-than (>>) sign to open or close this panel. |
| Lists the incident request records according to the company selected in the Show field and the Filter By field. To view the incident record in detail, double-click the incident request in the Incidents table. Fields on the form display the incident status and other information related to the incident. System administrators can set permission in the Applications Permission Model to view the incident request. For more information, see Applying system settings. |
| Generates a new incident request record. |
Create for Company (for Hub and Spoke installations) | Generates a new incident request record after asking you to identify the company you are creating the record for. |
| Shows the incident request record that is selected in the Incidents table. |
| Prints the selected record in the Watch List and the Incidents table. |
| Opens a high-level diagram of the Incident Management process. |
| Opens the Service Context Summary view for the record selected in the console table. The Service Context button is available only when a business service CI is associated with the incident record. If a business service CI is associated with the incident record, the CI name appears in the Service column of the Incident table. For more information about Service Context, see Enabling and configuring Service Context for BMC Helix ITSM applications. |
| Select an action from the menu. You can perform the following quick actions: - Assign to group member—Reassigns the incident request to another member of your group
- Assign to me—Reassigns the incident request to yourself
- Incident Closure—Moves incident requests with a status of Resolved to the Closed status
|
| Click Preferences to open a menu from which you can add or remove columns from the table, set the rate at which the application refreshes the table contents, or restore the default table preferences. |
| Details — When selected, contains detailed information about the record selected in the Incidents table. To see Incident Details when the Tasks table is showing, click Show Details. The Create, View, and Report icons relate to the work information notes that appear in the table. You can sort the table by clicking any column heading, except Notes. Tasks — When selected, lets you view tasks associated with the incident request record selected in the Incidents table. To see Tasks when Details is showing, click Show Tasks. |
The following consoles provide access to all or a part of
Some content is unavailable due to permissions.
:
The
Some content is unavailable due to permissions.
console is the main console for the application. It provides problem coordinators and specialists with a single point from which they can create known error entries. It also provides a place from which they can monitor the progress of problem investigations as the investigation moves through its lifecycle, and record work that was performed during the investigation.
Using the Overview console, specialists can view problem investigations that were assigned to them through the
Some content is unavailable due to permissions.
application. The specialist role is fulfilled by all IT employees and long-term contractors, except Service Desk Analysts and IT Operators. Specialists can also view work that was assigned to them through the other applications with which
Some content is unavailable due to permissions.
integrates:
The following table describes the functional areas of the
Some content is unavailable due to permissions.
console.
Some content is unavailable due to permissions.
console functional areas
| |
---|
Some content is unavailable due to permissions. console header |
---|
| |
| Opens the Search feature. |
| A navigation aid that contains links to related records that you opened from the current problem investigation. For more information about the Breadcrumb bar, see Managing your work by using Ticket Console in the documentation. |
Breadcrumb navigation controls | - Back button takes you back one link in the breadcrumb trail.
- Forward button takes you forward one link in the breadcrumb trail. The Forward button is visible only if you have returned to a record on the breadcrumb trail that you previously viewed.
- Drop-down menu contains links to all the records that you viewed from the current problem investigation, including records that are not currently visible in breadcrumb trail.
- Home icon takes you to the IT Home page.
|
| Updates the data in the tables. |
| |
Show Filter By By Role More filters | The Show, Filter By, and By Role fields combine to control which problem investigation records appear in the Problem table. |
|
---|
View Broadcast, or New Broadcast | Click this link to open the broadcast dialog box, from where you can view, create, modify, and delete broadcasts. When there are unread broadcast messages, this area displays a New Broadcast message along with the number of new messages. When there are new broadcast messages, the area also turns red. For more information about broadcasting messages, see Broadcasting-messages-to-users. If you open the Some content is unavailable due to permissions. console with no new broadcast messages, but the View Broadcast link is red, open the Application Preferences dialog box and make sure that a Console View preference has been selected. For information about how to view and select Console View preferences, see Selecting your application preferences. |
| This area shows the number of open, unassigned, and unacknowledged problem investigations and the number of open known errors according to the selection in the Show field. The count categories are: - Open Problems —Refers to problem investigations that have a status of Under Review, Request for Authorization, Assigned, and Under Investigation.
- Unassigned Problems —Refers to problem investigations that are not assigned to an individual.
- Unacknowledged Problems —Refers to problem requests that have a status of Assigned or Pending. An investigation is no longer considered unacknowledged after you change its status to In Progress.
- Open Known Errors —Refers to known errors that have a status of Assigned, Scheduled for Correction, and Assigned to Vendor.
|
| Use the links in this area to do the following actions: |
| Contains links to other BMC applications, consoles, and modules. The contents of this area depend on what other applications are installed. Click the double greater-than sign (>>) to open or close this panel. |
| Displays high-level details about the records that match the criteria specified in the Company and Assigned To fields, or that were found by the most recently completed search. |
| Opens a dialog box from which you can create a problem investigation and known error record. |
Create for Company (Hub and Spoke environments only) | Opens a selection list from which you select the company you are creating the record for. You then select to create a problem investigation and known error record. |
| Opens the problem investigation and known error record selected in the Problems table. |
| Prints the details of the problem investigation and known error record selected in the Problems table. |
| Opens a high-level diagram of the problem management process. |
| Opens the Service Context Summary view for the record selected in the console table. The Service Context button is available only when a business service CI is associated with the problem investigation. (The CI name appears in the Service column of the Problems table.) For more information about Service Context, see Viewing CI and service relationships in the Service Context. |
| Opens a menu from which you can add or remove columns from the table, set the rate at which the application refreshes the table contents, and restore the default table preferences. |
| Details—When selected, contains detailed information about the record selected in the Problems table. To see Details when the Tasks table is showing, click Show Details. The Create, View, and Report icons relate to work information notes. You can sort the table by clicking any of the column headings, except Notes. The table does not sort on the Notes column. Tasks—When selected, displays tasks associated with the record that is selected in the Problems table. To see Tasks when Details is showing, click Show Tasks. |
By using work information entries, you can keep notes about the work that you perform on the related record or pass information to colleagues also working on the record. For example, you might want to add a note that a particular CI was deployed, and include the date. You can add work information records directly from the console table, or by opening the record form.
You can view multiple Work Info entries at the same time by clicking the History icon. When you click this icon, the system displays a pop-up window with the Notes field entries arranged with the most recent entry at the top (a date and timestamp is also visible with each entry).
If you have Incident Viewer or Problem Viewer permissions, you can add and modify Work Info entries; however, you cannot create or modify incident requests, problem investigations, or known errors.
- From the console table, open the incident request, problem investigation, or known error.
- To add new work information, under the Add Work Info details section on the Work Detail tab, enter the following information:
- Notes—Enter the details of your work information record.
- Attachment—Click
to add attachments related to the work information. You can add up to three files.
- Click More Details to select the work information type and add more attachments as needed.
From the Work Info Type list, select the type of work information to add.
Click here to see a description of the Work Info types ...
The table below lists the work info types available for asset, incident, problem, task, and known error records.
| Available for the application | |
---|
| | This can be any type of communication from the customer to the incident support staff (for example, email or phone). |
| | The customer acted on the suggestion from the support staff and is reporting on the outcome of those actions (for example, testing a hotfix). |
| | The customer acted on the suggestion from the support staff and is updating the progress of the actions or is reporting that there was a delay. |
| | The support engineer contacted the customer to verify that the problem is solved and the incident can be closed. |
| | Detailed information provided on the closure of the problem. |
| | Information about a change. |
| | Information about decommissioning. |
| | Information about the deletion of a task. |
| | The support engineer asked the customer for more information to clarify what the problem is, or the support staff needed clarification of information that the customer supplied. |
| | Information about the extension of a task. |
| | The support engineer asked the customer for general information such as platforms, versions and patch levels, or a contact telephone number. |
| | The support engineer created a task for another person who is helping with the known error. |
| | Information on provisioning. |
Resolution Communications | | The support engineer sent a resolution email to the customer or called the customer with the resolution. |
RMA - Return to Distributor | | Info about an item that must be returned to a distributor because it is damaged or unwanted. |
| | Info about an item that must be returned to a vendor because it is damaged or unwanted. |
| | A satisfaction survey was sent to the customer. |
| | The support engineer updated the customer with investigation or testing status. |
| | The support engineer created a task for another person who is helping with the incident. |
| | The support engineer created a task for another person who is helping with the problem. |
| | The support engineer included information about the investigation findings. |
| | A predefined set of questions was used to help solve problems. |
| | A log file was attached to the ticket for debugging purposes. |
| | The email system automatically updated the work info. |
| | A paging system automatically updated the work info. |
BMC Impact Manager Update | | BMC Impact Manager automatically updated the work info. |
| | The Chat feature in automatically updated the work info. |
| | Communication between a support engineer and a vendor. |
| Some content is unavailable due to permissions. Some content is unavailable due to permissions. Some content is unavailable due to permissions. Some content is unavailable due to permissions. - Problem Investigation
- Known Error
| When you select a value for the Assignee or the Assigned Group field and save the information, the system automatically adds a new entry under the Work Detail tab. |
| Some content is unavailable due to permissions. Some content is unavailable due to permissions. Some content is unavailable due to permissions. Some content is unavailable due to permissions. - Problem Investigation
- Known Error
| When you select a value for the Impact or Urgency fields and it results in a change in the value of the Priority field, when you save the information, the system automatically adds a new entry under the Work Detail tab. |
| Some content is unavailable due to permissions. Some content is unavailable due to permissions. Some content is unavailable due to permissions. Some content is unavailable due to permissions. - Problem Investigation
- Known Error
| When you change the value of the Status field and save the information, the system automatically adds a new entry under the Work Detail tab. |
- In the Attachment fields, add any additional attachments required for the work information. You can add up to three files.
Select whether to lock the work log.
If you select Yes, you cannot modify the work log after you save it.
- From the View Access list, specify the level of access to the work entry:
- Click Add.
The Save operation adds your entry to the work history.
- Open the
Some content is unavailable due to permissions.
console. - Select an incident.
- From the Details and Task pane, select the work information record that you want to modify and click View.
- In the Incident Work Info window:
- Update the required fields.
- To remove an attachment, click the delete icon (
) for that attachment. - Click Save.
- To view a report of selected activities that you performed against this record, select the records from the work info table and click report
.
- Adding or modifying the work information of a ticket or a work order does not update the last modified date of a ticket or a work order for the following applications:
- When you select a value for the Impact or Urgency fields and it results in a change in the value of the Priority field, the system automatically adds a new entry under the Work Detail tab when you save the information.
- From the console, select the record to which you need to add a work information entry.
- At the bottom of the console, open the Detail area by clicking Show Detail.
- Click Create.
- Enter the work information details in the Work Info dialog box.
- To add an attachment to the record, right-click in the attachment table and select Add from the menu that appears.
Select whether to lock the work log.
If you select Yes, you cannot modify the work log after you save it.
- Choose the type of view access:
- Internal—Select this access if you do not want the customer to see the work information entry on the Requester console or the console.
- Public—Select this access if you want the customer to see the work information entry.
When a work note is created in a request that originated from the console and is marked as Public, the work note also appears in the request's activity log in the Request Entry console of . If the work note is updated, the original work note remains in the request's activity log, but the updated information is placed in a new entry in the request's activity log. If the work note is updated and the Assignee marks it as Internal, the original work note remains in the request's activity log, but the updated information is not displayed.
- Click Save.
- To see a report of selected work information entries, select one or more entries, and click Report.
If the work information entry is not locked, you can modify any field on it.
- From the Incident or Problem console, select the incident request or problem investigation record.
- At the bottom of the console, click Show Detail to open the Detail area.
- From the list of work information entries, select the work information record that you want to update.
- Click View.
Make the required modification as described in the following table:
| |
---|
| Click inside the Notes field and type the changes. |
| Right-click in the attachment table and select Add from the menu that appears, and then follow the onscreen instructions. Attachments to work information entries created in are not transferred with information sent to a backend application, such as an incident, a change request, or a work order. You can access the attachments only from the service request. |
| From the Locked list, select Yes. If you select Yes, the work information entry cannot be modified after you save it. |
To change the view access level | From the View Access list, select Internal or Public. Select Internal if you want only users with application permissions for Some content is unavailable due to permissions. or Some content is unavailable due to permissions. to see the entry. Select Public if you want everyone with access to the system to see the entry, including requesters. In environments that also run , when a work note with the Public access level is created in an incident that originated with the console, the work note also appears in the request's activity log in the Request Entry console of . If the work note is updated, the original work note remains in the request's activity log, but the updated information is placed in a new entry in the request's activity log. The View Access setting is a shared component in . You can change the view access level for Problem Investigation and Known Error records to Public. However, this does not have any effect. If the work note is updated and the Assignee marks it as Internal, the original work note remains in the request's activity log, but the updated information is not displayed. |
- Click Save.
If you save the incident or problem investigation record without making any changes to the work information record, the values in the Modified Date and Last Modified by fields of the work information record are updated.
- Open the incident request or problem investigation record.
- On the Work Details tab, double-click the work information entry that you want to update.
The Notes field updates to contain the work info text and the More Details area expands to reveal the hidden fields. - Make the required changes.
If you need to remove an attachment, click the Eraser icon beside the associated Attachment field. - Click Save.
If you save the incident or problem investigation record without making any changes to the work information record, the values in Modified Date and Last Modified by fields of the work information record are updated.