Other changes in Service Desk and Asset Manager 2016.2

This section describes the other changes that were made for Service Desk and Asset Manager 2016.2.

Asset Management module in Service Desk removed

As part of the upgrade to 2016.2 for Service Desk, all of the objects in the Asset Management module have been moved to the Configuration Management module. The new Asset Management module is now solely for use with Asset Manager, along with two more new modules: Contract Management, and Audit Management. You cannot design processes for these modules unless you are licensed for Asset Manager. Similarly, you cannot design processes for Incident Management, Problem Management, Call Management, or Knowledge Management unless you are licensed for Service Desk.

For information about the new modules, see the Prebuilt Content section.

You can no longer select Optional Modules as part of the database upgrade in Configuration Center.

As a result of this change, after upgrading to 2016.2 you must rebuild your Service Catalog and knowledge indexes. In Ivanti Console, start the Knowledge Management Administration component, and display the Knowledge Settings. In the Actions list, click Rebuild Knowledge, then click Rebuild Service Catalog.

12-hour or 24-hour time formats for users

2016.2 enables you to specify for each user whether they want times displayed in 12-hour format (for example, 03:45 PM) or 24-hour format (for example, 15:45). The default is 24-hour format.

During the upgrade, a new attribute called Time Format is added to the user object. You can add this as a field on any of your user windows so that in the Administration component of the Console you can select 12 Hour or 24 Hour for each user.

Running related actions on only a subset of the items in a collection

In 2016.1, the ability to run actions on related processes was added (see Running actions on related processes). From 2016.2, if the related action is running on a collection of items on the source process (for example, adding a note to all of the Changes attached to a Problem), you can add a filter to the properties for the automatic action so that the action runs only on a subset of the items in the collection. For example, if your related action adds a note to all of the Changes attached to a Problem, you can add a filter to select only those Changes that are at a specific status and then add the note only to those.

To add a filter to a related action:
  1. Open the required process and select the automatic action for the related action.
  2. Click .
    The Properties grid appears.
  3. In the Related Action Filter property, select the filter you want to use, or click New.

If you create a new filter, the Based On and Filter By values are preselected for you.

  1. Click .
    The process is saved.

Changes to linking objects

Sometimes you want to link together objects that are currently not linked together. For example, you can link the incident note category object with the support group object to associate specific support groups with specific incident note categories. This then enables you to create a filter that displays only those categories on an incident note that are associated with the specific support group.

Previously, the number of objects that you could link in this way was highly restricted: mainly to objects that are available in the Administration component, such as categories. From 2016.2, the objects available when you use the New Linking Business Object action in Object Designer is greatly increased.

Using details from the originating process in a linking action

When you create an automatic linking action in Process Designer, you can now specify the current object for one side of the link. For example, you can set up an automatic linking action on a Change that will link the Change to a CI.

You do this by creating a linking object and adding an action to create the link using the Manage Business Object Actions dialog in Object Designer. When you have created a window for the linking object and added the new action as an automatic action in Process Designer, you can now select . as the runtime value for the control when you set a Value Type for the process end of the link.

For information about creating Linking Business Objects, automatic actions, value types, and about using Process Designer, see the Designer Guide.

Specifying a process when importing data

When you import data into an object that has processes associated with it, such as Change, Customer, or (if you are using Asset Manager) Configuration Item, you can specify the process that you want to use for the items that you are importing.

To specify a process when importing data:
  1. In Ivanti Console, start the Data Import component and open the required mapping from the Import Mappings tree.
  2. On the Target Attributes tree, right-click the business object, then click Set Lifecycle.
    The Lifecycle dialog appears.
  3. In the Lifecycle list, select the process that you want to use with the imported data, then click OK.
    Only activated processes appear in the list.
  4. Save the changes to the import.
    The next time the import runs, the imported data will use the selected process.

If you do not select the process that you want to use for imported data, the process that is set as the Default in Process Designer is used.

You can map an attribute from the source onto the Status for the target to ensure that the imported item is imported to the correct place on its process.

Date and time options for Console queries in Web Access

The Date Only and Time Only options on the Date Time Properties tab for column properties set on a query designed in Console are now supported in Web Access.

Grouped queries on collection tabs in Web Access

Previously, if you had a grouped query as the default query for objects that were used as collections on windows in Web Access, an error was displayed in Web Access. From 2016.2, you can used grouped queries as the default query, but the grouping is removed when you display collections in Web Access.

Query paging in Workspaces

The paging control on queries in Workspaces has been updated.