CIS-HAM Exam Dumps : Certified Implementation Specialist - Hardware Asset Management

The ServiceNow Agent mobile app allows the user to scan and create assets in ServiceNow in various scenarios123.

One scenario is to create a single asset via barcode scan. The user can scan the barcode or QR code of an asset and fill in the required fields to create an asset record in ServiceNow1.

Another scenario is to receive one or multiple assets from a purchase order. The user can scan the barcode or QR code of a purchase order and view the list of assets to be received. The user can then scan the assets and confirm the receipt in ServiceNow1.

The other scenarios, such as creating multiple assets listed on a contract PDF scan or creating a single asset via Name search, are not supported by the ServiceNow Agent mobile app123. References:

ServiceNow Agent app - Product Documentation: San Diego - Now Support Portal

Hardware Asset Inventory Management - ServiceNow

Automation Simplifies Hardware Asset Management - ServiceNow Blog

To exclude certain types of CIs from the CI lists on the Incident, Problem, and Change forms, you can use the Principal CI class checkbox, which is available on the Class Manager module under Configuration1.

The Principal CI class checkbox allows you to specify which CI classes are considered as principal CIs, meaning they are the most relevant and important CIs for the business services and processes1. By default, only the CI classes that have this checkbox selected are displayed on the CI lists on the Incident, Problem, and Change forms2.

To use this feature, you need to navigate to the Class Manager module, select the CI class that you want to exclude or include, and check or uncheck the Principal CI class checkbox accordingly1. You can also use the Filter option to search for the CI classes by name or label1.

The other options are not recommended or valid ways to exclude certain types of CIs from the CI lists. Adding a Show field to the base cmdb table would require modifying the table schema and creating a reference qualifier, which could affect the performance and integrity of the CMDB3. Creating an Access control to hide the unnecessary CIs from the itil users would require defining the conditions and roles for the access rule, which could be complex and error-prone4. Making a show/hide UI action to show only the desired CIs to the itil users would require creating a custom script and UI element, which could be incompatible with the existing UI and functionality. References: 1: Principal configuration item classes 2: Configuration item lists 3: CMDB table schema 4: Access control rules : [UI actions]