The database comprises a number of different modules that correspond to different business areas. For example, there are modules for Problem Management, Change Management, Request Management, and so on. Each of these modules contains a number of business objects that you use to capture information and a top-level object that you can create processes for.
You can also add new modules to your database to support additional business needs in your organization, and transfer them to a different database. For example, you could add a new Facilities Management module to handle your organization's facility management processes.
When you create a new module, you specify a top-level object for it that you can create processes for, and the software automatically creates the objects and behaviors required to provide the basic features for a process module.
In addition to the top-level object, creating a new module creates the following objects:
You can now add new objects and attributes to the new module as required, and design windows, processes, queries, and so on as for any other module.
For information about how to create a Reinitialize action in a new module, see Reinitialize: switching between processes within a module.
If you want to use a process from your new module with Service Catalog, you need to add the ConfigurationItemType Relationship behavior to the top-level object.
If you are logged in to Console as a user who has their culture set to the default language, you can export locked modules using Design Transfer so that they can be imported into another database.
When you have locked a module, you can use Design Transfer to export only the entire module. You cannot export individual windows, processes, and so on from a locked module unless you unlock it. The branches that correspond to locked modules under the Service Desk folder in the Export tree in Design Transfer are removed.
When you lock a module, you supply two passwords: a publisher password and a subscriber password. The publisher password locks the module for editing and makes it available for exporting. The subscriber password enables someone who has imported a module into a different database to unlock it and make changes to it. If a subscriber DOES NOT unlock their imported module, then they can accept future versions of the module supplied by the publisher as updates to the module. If a subscriber DOES unlock their imported module, they can no longer import updates to it.
Never provide the publisher password when you provide an exported module. This password is only for the publisher to unlock the module so that it can be modified to generate a new version to give to subscribers.
DO NOT provide the Publisher Password.
When a subscriber has the XML file, they can import the module into their own database.
When you have imported the new module, you can use all of its features as provided.
If you have a locked module, you can still add Web Access queries, and create, update or delete instances of service levels, ordered lists, reference lists, and categories for the module.
If you want to modify the module using Object Designer, Window Manager, Process Designer, Query and Report Designer, or Template Designer, you first need to unlock it using Object Designer.
If you unlock a module you cannot accept future updates from the publisher of the module.
If you have never unlocked a module, you can import updates to it that are provided by the publisher. Changes made to an updated module are merged into the original module. If categories, ordered lists, reference lists, or response levels are different, then you are asked which ones you want to keep.
When you import an updated module, you are told about any objects or attributes that have been removed from the module so that you can fix any Web Access queries, Crystal Reports, and so on that you have created that may have relied on those objects and attributes.
You can delete certain unlocked modules from your database using the Delete Module action in Object Designer. Modules that you cannot delete are:
You cannot delete modules that are referenced from other modules until you have removed those references.
Copyright © 2018, Ivanti. All rights reserved.