Brief overview of the Service Manager Console

Here is a brief overview of the Service Manager Console and some small tips you can use when authoring your own management pack to leverage some of the functionality of the console.

Before going into specific areas, let’s begin with the layout of the console. The console is composed of different areas, and each have a name to it. Below is an image of the console highlighting the different areas:

Main Menu

There are some menu options available that are quite self-explanatory.

Tools has Connect that you can use to connect to another server. You can use my recipient information which opens up your user form provided your user account does exist in the Service Manager database. My notifications lets you view/create/edit and delete notifications where only you’re the recipient.

Wunderbar

This is the area where each item represents a workspace. Out of the box we have Administration wunderbar which has the views and folders that are needed to administer the Service Manager, then we have Library for solution configuration, and then the solution wunderbars follow like Work Items, Configuration Items, etc.

To be able to add your own wunderbar, all you need to do is to add a Folder mp element that is a child of the Console Root folder. The Console root folder exists in the Microsoft.EnterpriseManagement.ServiceManager.UI.Console management pack

<FolderID=“ServiceManager.Console.RootFolder“Accessibility=“Public“ /> à this is the definition of the console root folder, your folder would look like:

Once you have the wunderbar in place, now you will need the top level tree node for your navigation pane. Navigation pane is the area on the left most side in the console. Essentially now any folders that are children of the newly created Folder Microsoft.EnterpriseManagement.ServiceManager.UI.MyWunderBar will appear in this pane. To have a similar look and feel with the out-of-box spaces in the console, its best to have one folder be the child of Microsoft.EnterpriseManagement.ServiceManager.UI.MyWunderBar and then everything else be children of Microsoft.EnterpriseManagement.ServiceManager.UI.MyWunderBar.Tree and you can go as many level deep as you wish to arrange your space

This shows the location of where you are in the console. This displays an explorer structure of the selected item in the navigation pane. So if you’re in administration space, selected Status under workflow—it will show the path as \Administration\Administration\Workflows\Status

View Pane

Now once you have a certain hierarchy of elements in place in terms of what folders and views you would like to have in your navigation pane, the next step would be what gets displayed for them in the view pane.

Each node (tree view/navigation pane item) has a default task, something that gets executed when the node is clicked. Out of thebox currently we support opening 3 types of views when a node is clicked namely:

Overview view: if you click the top level node in the administration space, the view that gets opened up in the view pane is the overview view. In this you can host your own control (page/view) using the schema provided by the OverviewType. This will be discussed more in depth later. More details can be found here:

Summary view: This is something you get for free. If you have folders in your navigation pane that don’t have a corresponding view of type OverviewType then the summary view gets displayed in the view pane that essentially lists the number of folders and views that are contained by that particular folder.

Grid view: This view essentially lists the data in a grid view based on items fetched from a class with a certain criteria if desired. This will be discussed in depth later as well. More details can be found here:

The next area would be the Details pane. This pane gets displayed when the selected view in the view pane is of a grid view type. This area essentially uses the generic forms infrastructure to show the contents of the selected item in the view pane. All classes that derive from System.Entity show the details pane. You can use a category if you don’t want to see the details pane for a class like below:

<CategoryID=“[UniqueCategoryID]“Target=“[TargetClass]“Value=“Administration!Microsoft.EnterpriseManagement.ServiceManager.UI.Administration.Enumeration.HideDetailsPane“ /> where Target is the class and Value is the enumeration that is defined in the Microsoft.EnterpriseManagement.ServiceManager.UI.Administration mp.

The tasks pane items appear based on items selected. So if you’re in the work items space and select the ‘Problem Management’ folder, you will see all tasks that are applicable to the selected folder, then any tasks applicable to the problem management’s parent folder, and then its’ parent in order. They are grouped by the selections in order. So the current selected items’ tasks will appear first, followed by its parents tasks, followed by the parent’s parent task and so on.

Nodes is the list of selected item(s) –so it could be a folder, view or list of selected item(s) in the grid view

Parameters is the additional arguments that can be passed to the task. This is useful when you want the same task handler to do different things based on parameters passed

}

}

The target of the task can be based on needs, so if you want the task to show up when the selected item in grid view is of a particular class, then you should target it to the class. If you want the task to show up if a folder or view is selected then you should target it to that folder/view.

Folders can also contain tasks. So if you want a task to show up for a selected class and also when a folder is selected, then you can target the task to the class and add a FolderItem mp element that has the ElementID of the task and the folder is the one you want you want the task to show for.

The search menu consists of a text box and a drop down that lets you pick types you want to search on. You can choose to search all objects which will show the result in a new window with the search of DisplayName in all work items and configurations that contain that string.

Out-of-box you can search for displayname strings for Incident, Change, Problem, Configuration Items and Windows Computer individually as well.

To be able to add more classes to the list that you want to search on, you can add it to the list by adding a category to your class