Enabling the NEW Config Item Pages (aka Views)
The NEW Config Item pages or Config Item Views are hidden by default. To view them, you must set the pages’ visibility true through the Navigation Settings Page.
When you are on the Navigation Setting, search for the NEW Config Items on the navigation list, and check the Visible checkbox.
Â
Once set to visible, you will be able to see a new navigation node named NEW Config Items and the out of the box sub-nodes match what is in Service Manager Console’s Configuration Item view.
Â
Config Item Views
The new navigation node named NEW Config Items is the parent to the new configuration item pages/views. Unlike the current config item view where all configuration items are listed out on a single grid, we have now listed the new pages/views by the config items by class. Â
These pages/views are built using the oData grid widget with Dynamic Data. So users can do all oData grid features on these pages.
Config Item Form (Default)
The default config item form is patterned that of a default config item form in Service Manager Console. The General tab will have the following section:
Object – the first section which only holds the Display Name property
Configuration Item – the second which holds the properties of the Configuration Item base class
Derived Class Properties – the third section which holds the properties of the specific CI class
Â
Custom Config Item Form
Customizing a CI form on the portal is like that of customizing WI forms, which you can read more here.
The only difference is that you will have to name the file with the FULL ClassName and should be placed under the CustomSpace/ConfigItem folder.
For instance, if you would like to customize the Domain User form, the template file should be named as “System.Domain.User.js”
Custom Config Item Task
Adding a custom task to a CI form on the portal is like that of adding WI custom tasks, which you can read more here.
A couple of items to take note, there will be two (2) ways of defining custom tasks for config items as detailed below:
Generic Task
To create a task which will be available to all config items class, use ConfigItem as the task name.
app.custom.formTasks.add('ConfigItem', "Hello World", function (formObj, viewModel) { kendo.ui.ExtAlertDialog.show({ title: "Alert", message: "Hello World" }); return; });
Class Specific Task
Like customizing forms, you will need to use the FULL Class Name as the target type.
app.custom.formTasks.add('System.Domain.User', "Hello World", function (formObj, viewModel) { kendo.ui.ExtAlertDialog.show({ title: "Alert", message: "Hello World" }); return; });
The above code will add a "Hello World" task to the User Form's Task Panel, when clicked the user will see a stylized alert window with the message "Hello World"
Custom Config Item Page
The config item pages are built using both Dynamic Data and  table widget.
If you wish to create a page for your custom CI classes, you need to add them first to Dynamic Data. You can easily do this by adding your class’ table name on the Table Filter Name of the Dynamic Data Settings page. See this article for more detailed steps on how to add table names.
Once your class is available in platform cache, you can create your CI list page by using the OData widget, which you can read more here.
Â