This documentation supports the 21.3 version of BMC Helix ITSM.

To view an earlier version, select the version from the Product version menu.

Accessing BMC Helix ITSM application console

Accessing and navigating the legacy BMC Helix ITSM application console

To log in and access the BMC Helix ITSM applications:

  1. Type the following URL into your browser:
    • <webServer>: Fully qualified name of the BMC Helix ITSM, specified in the format .
    • <port>: (Optional) Port number (required if the web server is not on the default port)
  2. In the User Name and Password fields of the Welcome page, enter your user name and password.
  3. Click Login.
    The IT Home page opens by default, however, system administrators can use Configuring home page preferences Open link to open.

Application consoles

Use the information provided in this topic to understand the application consoles. BMC Helix ITSM: Asset Management, BMC Helix ITSM: Change Management, and BMC Helix ITSM: Service Desk each provide one or more consoles. The following table provides information about the consoles provided by each of these applications.

  • Incident Management interface Open link
  • Problem Management interface Open link
  • The functional areas of the Asset Management console Open link
  • The Software Asset Management SAM console Open link
  • Data Management consoles and windows

BMC Asset Management

This application console provides the following consoles to perform asset management tasks.

  • Asset Management 
  • Contract Management 
  • Purchasing 
  • Software Asset Management (SAM) 
  • Receiving
BMC Change Management

This application has the following two consoles:

  • Change Management console
  • Release Management Console

The Change Management console has two views: one focused on the support technician, and one on the manager. The Change Management console also provides the ability to change the support console to focus the work on tasks or change requests.

BMC Service DeskBMC Service Desk provides an Incident Management console and a Problem Management console. Each of these consoles provides a single view that is intended for use by service desk analysts and managers.
Data ManagementData Management provides the Data Management Job Console.

Navigating consoles, forms, and modules

As a service desk agent, you can navigate around BMC Helix ITSM consoles, forms, and modules.

In most cases, when you open consoles, forms, and modules from the IT Home page, they open inside the IT Home page view. Similarly, if you open a form from a console, the form replaces the console in the view.


If you are working in a hub and spoke environment and open a spoke server record from the hub server, the spoke server record opens in its own window. Each subsequent spoke server record that you open from a hub server also opens in its own window. You can open as many spoke server windows as necessary.

Be aware that opening a spoke server record on a hub server can take a little longer than it does to open records in environments that are not configured for the hub and spoke capability. This delay is because the hub server must first determine which spoke server to connect to and then open the record in separate browser window.

If you open a related record from a form, the related record opens in the view that was occupied by the form. For example, if you are working with a problem investigation (the "parent" record) and from the parent record you open a related incident request, the incident request replaces the parent record in the view. If you then open a change request from the incident request, the change request replaces the incident request in the view, and so on. To help you keep track of the records you are viewing and to help with navigation, there is a breadcrumb bar across the top of the view field.


Not all of the consoles, forms, and modules open in the view area. For example, the AR System Approval Central module opens in a new window. When a console, module, or form opens in a window, it is not added to the breadcrumb bar.

How do the breadcrumb navigation buttons and bar work?

The breadcrumb bar contains links to the records that you opened from the parent record. When you open a record, the breadcrumb trail expands along the breadcrumb bar. If there are more than six links in the breadcrumb trail, arrows appear at one or both ends of the bar that let you scroll back and forward on the bar to see links not currently in the view.

The first link in the breadcrumb trail indicates the place from which you started. It can be a console or a form. For example, if you open a change request record directly from the IT Home page, the first link in the breadcrumb trail takes you to the change request.

The last link corresponds to the record currently in the view. If you open a link to the left of the record currently in view, the system truncates the breadcrumb trail to that link. The history is retained, however, so you can use the back and forward arrows in the navigation controls to move through the bar one record at a time. There is also a history of your most recently viewed records, which you can use to move directly to a record. Click the down arrow to open the history list.


The Forward button is only visible after you move back along the breadcrumb bar by opening a link to a record that you previously viewed.

If you are viewing a record from the middle of the breadcrumb trail and then branch off to another parent-type record, the system removes the forward breadcrumb trail from the point where you branched off and starts a new history from there, using the new parent-type record as the starting point. For example: You open a problem investigation, and then open a related incident request, and from the incident request you open a related change request. If you go back to the incident request record and then open a second problem investigation, the breadcrumb bar no longer contains a link to the change request. The breadcrumb trail now shows the original problem investigation, the incident request, and the second problem investigation. It then shows any related records that you subsequently open from the second problem investigation.

When you close the parent record, the system removes the breadcrumb history.

What happens to data as I move back and forth on the breadcrumb trail?

If you are entering information into a record and open another record from the breadcrumb trail, the system prompts you to save the work, if you have not done so. If you do not save the information, the system does not preserve it on the record and you must re-enter it later.

If someone updates and saves a record on your breadcrumb trail that is not currently in the view, those changes are visible to you when you open the record again.

How does the breadcrumb trail behave with forms in Search mode?

If you run a search from a form that is in Search mode, the last entry in the breadcrumb trail is the name of the form.

When you open a record from the search results table, that record does not appear in the breadcrumb trail. However, if you drill down through that record to open other related records, those related records will appear in the breadcrumb trail.

To return to the originating record, use the history list.


All of the records that you open from a form in Search mode are added to the history list.

To return to the results table, click the name of the form in the breadcrumb trail.

Can I force a second window to open?

If you press the Shift key and then double-click a record entry in any table, the record opens in a second window. Also, if you hold the Shift key and click a link, button, and so on, the form or dialog box associated with the link or button opens in another window.


If there is a record in the history list that you want to open in a second window, press the Shift key and then double-click that record.

If you are working in a new record that has not yet been saved and you open a new child type record (task, activity, CI, and so on), the system will open a new window automatically to accommodate the new child record. This safeguard prevents the information in the new, unsaved parent record from being lost.

Which consoles, forms, and modules open in a new window?

Not all of the consoles, forms, and modules open in the IT Home page's view. The consoles, forms, and modules in the following list open in a new window. If you open one of these from the IT Home page, any unsaved changes to the IT Home page are lost.


Before you open any of the following consoles, forms, or modules, save the changes to the IT Home page that you want to keep.

  • AR System Administration 
  • Administration Console
  • Service Level Management 
  • Analytics 
  • Service Management Process Model

User interface standards for field labels

On BMC Helix ITSM forms, field labels provide data entry hints. The following table lists the significance of field-label formats and special characters.

Field-label format or special characters

Significance for data entry

Bold label

Field is required to submit and update the form.

Important: If you leave the field blank, when you attempt to submit the form, the field is highlighted with a red border.

Field label not bold

Field is optional.

Label followed by an asterisk (*)Field is Section 508 compliant. For more information about Section 508 requirements, see

Italicized label

System-generated value for this field. Typically this field is read-only for the user.

Label followed by a plus sign +

Additional functionality is associated with this field. Typically, you access this functionality by pressing Enter. For example, you might press Enter in a field to access a search dialog box or to perform a search based on the value typed into the field.
If a field label followed by a plus sign is also bold, the field is required. Otherwise, the field is optional.

For examples of field-label formatting in Incident Management, see the following figure:

Requester Console

For organizations that do not install BMC Service Request Management, the Requester Console is an interface for users to create and view their requests. From the Requester Console, users can create a request that is submitted to BMC Helix ITSM: Change Management or BMC Helix ITSM: Service Desk. Depending on how the application is configured, the console might display incident requests and change requests entered on the user's behalf by support staff, in addition to the requests that the user created. Users can also view requests and respond to a survey after the request has been resolved. 

Requester Console users are typically employees who need assistance from the IT support staff to implement a change or resolve an incident. However, the user might not be an employee. Non-employees can also be users because non-registered users can also submit service requests.

Traditionally, after a user made a telephone call to a central help desk, a support staff member logged the request. BMC Incident Management and BMC Change Management provide user self-provisioning. Using the Requester Console, users can submit, track, and (in some cases) resolve their own requests. BMC Helix ITSM: Change Management and BMC Helix ITSM: Service Desk are preconfigured to work with the Requester Console. However, an organization can decide to make the Requester Console unavailable.


BMC Service Request Management, when it is installed, replaces the Requester Console. For more information, see BMC Service Request Management Open link .

The following figure illustrates the key areas on the Requester Console.

Was this page helpful? Yes No Submitting... Thank you