The Common Master is a unique feature in the application that allows the Administrators to set most commonly used label names and drop-down values across all the modules. If there is a change or addition required in the label names or drop-down values, this feature saves the efforts of the Administrator to make the same changes on all the pages separately. In other words, it simplifies the customization process required to be done by the Administrators for most commonly used labels names and drop-down values.
On the Common Master Types page, the Administrators can add a new label or edit an existing label. For example, a label name called Designation needs to be displayed in the Project Management, Service Management, and Asset module. Instead of modifying the label name in those modules separately, the Administrators can modify the same on the Common Master Types page and map it accordingly on the Common Master page. It makes the change available across all the said modules.
Common Masters Types List By Module
Common Master Type - Platform
Common Master Type | Purpose | Common Master |
Customer | All the Customer values are saved. This can be manually created or is imported using Active directory import, which is used throughout the Application to select a Customer. | |
Department | It is used to save the department in an organization. | Example: IT |
Designation | It is used to save all the designations in the organization. All the users' designation is imported and created from Active Directory import or created manually, which is used across the Application. | Example: Associate Developer, Associate QA Engineer, Associate Engineer |
DisplayDateTimeFormat | It is used to save all the display format of time and date, which is used to display date/time format across the Application. | Example: d MMMM yyyy HH:mm, dd/MM/yyyy HH:mm, MM/dd/yyyy HH:mm |
DisplayTimeFormat | It is used to save all the display format of time, which is used to display time format across the Application. | Example: HH:mm, hh:mm tt |
Document Type | It is used on the Upload Document page to categorize all the uploaded documents. | Example: Official, Common, etc. |
Location | It is used to save all the required Locations, which is used across the Application. | Example: Bengaluru, Chennai, etc. |
MIBType | It is used to save all the MIBs while fetching Discovery data. | Example: CPU, Memory, Temperature |
NetworkOSType | It is used to save all the Network's operating system type retrieved during Discovery job run. | Example: ciscoSystems 15.2, ciscoSystems 16.9.3 |
OSType | It is used to save all the operating system type while retrieving the Discovery jobs data and is used across the Application related to Discovery. | Example: Linux, Microsoft, UNIX |
ServerType | It is used to save all the Server Types fetched during Discovery jobs processing. | |
SMTPAPITypes | It is used to save all SMTP API types if any other API type is used for SMTP. | |
User Level | It is used to save all the required User levels. It is used on User Management pages. | Example VIP, VVIP, etc. |
Vendor | It is used to save all the Vendors retrieved during Discovery of various IPs in Discovery. | Example: Cisco Systems, HP |
Common Master Type - Asset Management
Common Master Type | Purpose | Common Master |
Agreement Status | It is used in the Asset Management module in Contract Agreement Status. Users can Add New status. | Active |
Allocate To | It is used in the Asset Management module for Fixed Asset Allocation Type. These are fixed values and cannot be edited. | Customer, Department, Location, Multiple Users, Single User |
Approval Levels | It is used in the Asset Deactivation Approval Levels. These are fixed values and cannot be edited. | Deactive |
ApprovalMatrix | It is used in Asset Approval Matrix types. These are fixed values and cannot be edited. | Deactivate |
Asset PV Status | It is used in Asset Physical Verification Status list. These values can be edited. | Found, Not Found |
AssetCategory | It is used in Fixed Asset Category Group Name. These values can be edited. | Hardware, Electronic Equipment |
It is used to define the Fixed Asset Condition. These are fixed values and cannot be edited. | Good, Faulty, Scrap | |
AssetMovementApprover | It is used in the Asset Movement Approver Roles. These are fixed values and cannot be edited. | Floor Manager, Head of Location, Reporting Manager, Security Manager |
AssetMovementType | It is used in the Asset Movement Types. These are fixed values and cannot be edited. | Floor, From Repair, Store, To Repair |
ContractAttachmentType | It is used in the Contract Management module and can be edited. | User-defined values |
ContractCategory | It is used in the Contract Management module and can be edited. | User-defined values |
ContractEnrollmentOwner | It is used in the Contract Management module and can be edited. | User-defined values |
ContractFrameAgreement | It is used in the Contract Management module and can be edited. | User-defined values |
ContractFrameAgreementOwner | It is used in the Contract Management module and can be edited. | User-defined values |
ContractLicenseType | It is used in the Contract Management module and can be edited. | User-defined values |
ContractRole | It is used in the Contract Management module and can be edited. | User-defined values |
ContractSubCategory | It is used in the Contract Management module and can be edited. | User-defined values |
DeActive | It is used in Asset Deactivation Reason. These values can be edited. | CPU Problem, Mother Board Issue, Damaged |
Endpoint Script Category | It is used in Endpoint Automation Script Category. These values can be edited. | Network, Registry |
LicenseModel | It is used while adding Procured Software Inventory to define the License Model. | Core Based, Device Based, Processor Based, PVU Based, User Based |
LicenseType | It is used while adding Procured Software Inventory to define the License Type. | Evaluation Version |
Publisher | It is used while adding Procured Software Inventory to define the License Publisher. | Example: |
ReturnableType | It is used in the Asset Movement process to define the type of Asset Movement. | Example: |
Software License | It is used while adding Procured Software Inventory to define the License Software Name. | |
Software ServicePack | It is used while adding Procured Software Inventory to define the License Software Service Pack. | |
Software Version | It is used while adding Procured Software Inventory to define the License Software Version. |
Common Master Type - IT Operations Management
Common Master Type | Purpose | Common Master |
Service Entitlement | A Service Entitlement is assigned to Servers, Network Devices, Network Links, Network Interfaces, Printers, and URLS. Each Service Entitlement contains a group of Monitoring Parameters. | Any name |
Default Configuration | Default configurations can be created for Servers, Network Devices, and Printers. The default configuration can be used to create Servers, Network Device, and Printers from Discovery, import data, manual entry, etc. | Any name |
Action Template | Action Template is the template for specific actions while sending Alerts or while creating Incidents for violated entity parameters. | Any name |
Incident Template | Incident Template is the template of predefined configurations for raising an Incident. | Any name |
AutomatedScriptType | It is used to specify the environment type to run the various platforms scripts. It is used in Script-Based Monitoring. | Example: DOS Command, Batch File, VB Script, PowerShell Script, Remote Execution, SSH, TELNET, and Query, etc. |
AVMMonitoringParameter | Lists all the Monitoring Parameters in ITOM for all the device types, such as Server, Network Device, Network Link, Network Interface, Printers, URL, etc. Some of the parameters concatenate with their Criticality and their Threshold values can be set. | Example: Status, CPU Utilization High, CPU Utilization Medium, CPU Utilization Low, Zombie Process, Buffer Memory Utilization High |
AVMMonitorParameter | Lists all the Monitoring Parameters along with their parent type in ITOM for all the device types, such as Server, Network Device, Network Link, Network Interface, Printers, URL, etc. | Example: Status, Server Health, Hard Disk Utilization, Port Monitor, Exchange, SQL Server, etc. |
AVMTabs | Lists various tabs used in ITOM. Also, you can create new tabs while creating new parameters using Script-Based Monitoring and SNMP -Based Monitoring. | Example: Utilization, HardDisk, BufferSwap, Services, Port, MsSQLServerm, and Oracle, etc. |
Customer | Lists all the Customers in the ITOM module used for Server, Network Device, Printer, etc. | Example: Application |
DevCriticality | Specifies the Network Device's and Server's criticality. | High, Medium and Low |
DeviceCategory | Specifies the Network Device's Category. | Non Production and Production |
ElementType | Specifies the Network Device Types. | Example: Access Point, Access Switch, Cloud, Computer, Firewall, etc. |
Entity Description | Specifies the Entities descriptions. The Entities are Servers, Network Devices, etc. | Example: HP, Stepping, Windows, etc. |
Entity Type | Lists the Entity types in ITOM. | Network Device, Network Interface, Network Link, Printer, Server, and URL. |
Event Management | Specifies the Monitoring Parameters names of all Entity types, such as Servers, Network Devices, Network Links, Network Interface, Printers, and URLs for Event Management. | Status, RAM Utilization, CPU Utilization, Server Health, etc. |
EventImpact | Specifies Event's Impact | High, Low, and Medium |
EventPriority | Specifies Event's Priority. | High, Low, and Medium |
LinkCriticality | Specifies the Network Link's capacity. | High, Medium, and Low |
LinkThresholds | Designed to configure Network Link's threshold value, but not in use. | |
Location | Lists the Locations. | Example: Bangalore, Hyderabad, etc. |
ManagingVendor | Lists the Vendors, which are managing the environment for Network Devices, Links, and Servers. | Example: TATA, RELIANCE, etc. |
MIBType | List of Parameters used to provide MIB OIDs to monitor through SNMP. These entries can only be added from the backend into the database. No option to add from user interface. | Example: CPU, Memory, Temperature, Temperature Status, Fan Status, Voltage Status, etc. |
MonitoringProtocol | The List of protocols used to monitor various types of Servers. | Example: IPMI, SNMP, WMI, SSH, Telnet, Agent, Cloud, proxy server, WMI, VCenter |
MonitorSource | Lists the Monitoring Sources in Application. There are 2 options: Proxy Agent and Summit Server. | Proxy Agent and Summit Server |
NetworkOSType | Specifies the Network Device's IOS type and its version. | Example: CiscoSystems 15.2, CiscoSystems 16.4.2, CiscoSystems 16.9.1 etc., |
NWDeviceType | Lists all the Network Device types, which exist in the Networking module. | Example: Access Point, Access Switch, Computer, Firewall, Hub, etc. |
OSType | Lists all types of the operating systems. | Example: Microsoft Windows, Linux, AIX, Solaris, etc. |
OutputType | Specifies the output value type for the Parameters, which are configured using Script-Based Monitoring and SNMP-Based Monitoring. | Availability, Utilization Percentage, Utilization Value |
ParameterType | Specifies whether the Parameter exists or new while creating/updating a Parameter in Script-Based Monitoring or SNMP-Based Monitoring. | Existing, New |
PingProtocol | Lists the Ping Protocols. | ICMP, TCP, and UDP |
Platform | Used to create the Scripts/Commands to monitor parameters of the respective platforms. Used in Script-Based Monitoring. | Wintel, Non-Wintel, and Network |
Port | Lists the port numbers for Telnet and SSH. | 22, 23 |
Protocol | Lists the protocols. | Example: SSH, Telnet |
ProviderVendor | Lists the Vendors, which are providing service for Network Devices, Links, and Servers. | Example: TATA, Reliance, etc. |
Reason | Lists the reasons for Server/Network Device/Link/Interface downtime. | Example: Scheduled Down Time, Power Off, Network Traffic, etc. |
ServerType | Lists the Server Types. | Example: Apps, DC, |
Service | Lists the Services. | DNS, FTP, HTTP, HTTPS, etc. |
Vendor | Lists the Vendor, which are used to specify Servers, Network, or Device's Vendor. | Example: Cisco Systems, HP, DELL, etc. |
Common Master Type - Service Management
Common Master Type | Module | Purpose | Common Master |
Business Days | Incident Management and Service Request Management | It is used to select Skip Days For Response and Resolution SLA in Incident Management and Service Request Management Priority configuration. | Default value is 2. |
CALL_RECORD_MGMT | Call Management | It is used in the Call Type for capturing the action to be performed. | Enquiry, Incident, Request |
CatalogType | Service Request Management | It is used on the Log Service Request page in the filters to select the Service Catalog type. | No Values |
Change Management-Defect Status | Change Management | It is used for capturing Defect Status in Change Records Defects. | Open, Assigned, In-Progress |
ChecklistTaskStatus | NA | Not Used | No Values |
CMDB Tab Names | CMDB | It is used in CMDB Tenant configuration for configuring the editable tabs by the CI Owner. | Additional Information, CI Relations, Desktop, Documents |
CRRescheduleReason | Change Management | It is used for capturing Reschedule Reason. | Customer Approval, Pending |
Currency | Service Management | The Currency list to be used in across multiple modules. | |
Defect Sub Type | Change Management | It is used to select the Defect Sub Type in Change Record Defects. | No Default Values |
Defect Type | Change Management | It is used to select the Defect Type in Change Record Defects. | No Default Values |
MailToTicket | NA | Not Used | OutofOffice |
MapLocationFrequency | Incident Management and Service Request Management | It is used to select the Location Frequency in Analyst location pop-up. | 15, 30, 45, 60, 75, 90, 105, 120 |
Medium | Incident Management | It is used on the Incident details page for capturing the Medium in which the Incident is logged. | Application, ChatBot |
RBAExecutionOn | Orchestration | It is used to select the Execution On field in Orchestration configuration. | Incident CI, Service Request CI |
RBAExecutionType | Orchestration | It is used to select Execution Type field in Orchestration configuration. | By Action, By Asset, By CI |
RBARemoteToolParameter | Orchestration | It is used to select the Remote Execution By field in Orchestration Script. | System Account, User Account |
Release Requirements Type | Release Management | It is used to capture Requirements Type in Release Record. | No Default Values |
ScheduleType | Release Management | It is used to capture the Schedule Type in Release Record. | Build Schedule, Test Schedule, |
Service Catalog Group Name | Service Request Management | It is used to select the Service Catalog Group Name in Package configuration. | No Default Values |
SmartActionScriptType | Orchestration | It is used to select the Script Type in Orchestration action. | Batch File, DOS Command, |
Source | Incident Management | It is used to select the Source on the Incident details page. | AI, AI-Driven Digital Agent, Event Trigger, Group, Mobile App, |
SRApproveListStatus | Service Request Management | It is used on the Filters pop-up page on the Approve Service Requests page to select the Status. | Pending for Approval, Approved |
SRApproveStatus | Service Request Management | It is used to select the Approval Status on the Approve Service Request page. | Approved, Rejected, Refer Back |
TaskSequence | Incident Management and Service Request Management | It is used to select the Sequence on Auto Work Order Configuration page (Incident Management) and Work Order-Catalog Mapping page (Service Request Management). | Finish-to-Start |
TaskStatus | Change Management | It is used to select the Task Status in Change Record Tasks. | Draft, New, Assigned, In-Progress, Canceled, Implemented, |
TaskType | Change Management | It is used to select the Task Type in Change Record Tasks. | Implementation, Post Implementation, |
AnalystAvailabilityStatus | Service Management | It is used to select the Analyst Availability Status on the My Profile page. | Online, Away, Offline |
To Add Common Master Types:
Select Admin > Infrastructure > Common Masters > Common Master Type. The Common Master Type page is displayed.
On the right action panel, click Add New.
Figure: Common Master Type page
Provide the required details and click Submit.
Field Description
The following table describes the fields on the Common Master Type page:
Field | Description |
Master Value | Type in a name for the new Common Master Type. |
Parent | Select the required parent form the drop-down list. |
Specific to Domain? | If selected, the master value becomes Domain-specific. |
Active | If selected, the configuration becomes active. |
Actions
This section explains all the icons displayed on the right action panel of the Common Master Type page.
Show List
Click Show List to display the List table showing all the Common Master Types in the application.
Figure: Common Master Type page
To edit a Common Master Type, click the configured Common Master Type. Make appropriate changes and click Submit.
Note:
When the Common Master Types are displayed under the List table, the Add New action is displayed on the right action panel. Click Add New to add a new Common Master Type.Your content goes here.
Filters
Click the Filters icon to specify a particular filter criterion to display Common Master Types. On clicking the Filters icon, the Filters pop-up page is displayed. Select the Master Type and click Submit.
Figure: Filters pop-up page