CIS-HAM Certified Implementation Specialist - Hardware Asset Management Questions and Answers

According to the Hardware Asset Management documentation, residual value is the estimated value of an asset at the end of its useful life.

Residual value is calculated by subtracting the depreciation from the cost of the asset, as stated in the Hardware Asset Management documentation: “Residual value = Cost - Depreciation”.

Depreciation is the amount of value that an asset loses over time due to wear and tear, obsolescence, or other factors.

Therefore, the correct answer is option C, subtract the depreciation from the cost of the asset. References:

Hardware Asset Management documentation

What is Hardware Asset Management?

According to the ServiceNow Hardware Asset Management documentation, the ServiceNow Content Service is a cloud-based service that provides content updates for hardware models, such as manufacturer, model category, and lifecycle information. The ServiceNow Content Service also collects unrecognized data from customers, such as new or custom hardware models, to improve the content quality and coverage. Customers can opt out of sending unrecognized data to the ServiceNow Content Service for specific models, but this will also prevent them from receiving content updates for those models.

Operational: The current status, performance, availability, and capacity of the CI, as well as any incidents, problems, or changes that affect it.

Relationship: The dependencies and connections between the CI and other CIs, services, processes, and users.

The information that you would track for an asset includes:

Financial: The cost, depreciation, ownership, and warranty of the asset, as well as any procurement or disposal activities.

Lifecycle: The stages and transitions of the asset from request to retirement, as well as any inventory or stock management.

The information that you would not track for a CI versus an asset are:

Contractual: This information is relevant for both CIs and assets, as it relates to the agreements and obligations between the service provider and the customer or vendor.

Lifecycle: This information is relevant for both CIs and assets, as it relates to the stages and transitions of the component from request to retirement.

According to the Hardware Asset Management documentation, an asset audit is a process of verifying the physical existence and location of assets in an organization.

The asset audit results show the status of each scanned asset, such as “Scanned and expected”, “Scanned and not expected”, “Expected and not scanned”, or “Not expected and not scanned”.

The status of “Scanned and expected” means that the asset was both expected to be in the inventory and scanned during the audit, indicating a match between the physical and the logical inventory.

Therefore, if you receive the result of 10 “Scanned and expected” assets, it means that you expected 10 assets in your inventory and scanned these 10 assets during your audit, as stated in option B. References:

Hardware Asset Management documentation

What is Hardware Asset Management?

According to the ServiceNow IT Asset Management (ITAM) Hardware Asset Management (HAM) learning path, the Hardware Asset dashboard is a feature that shows key metrics on your hardware and consumable models and assets for the entire asset life cycle.

The Hardware Asset dashboard is available with the Hardware Asset Management (HAM) application, which is a licensable application that provides advanced workflow, automation, and mobile capabilities to maintain your assets1.

To access the Hardware Asset dashboard, you need to have the ham_user role, which is the minimum role required to use the HAM application1.

The ham_user role grants you the permission to view and update hardware and consumable assets, transfer orders, disposal orders, and RMA requests1.

Therefore, the correct answer is option C, ham_user, as it is the minimum role required to use the Hardware Asset dashboard. References:

ServiceNow IT Asset Management (ITAM) Hardware Asset Management (HAM) learning path

Hardware Asset Management documentation

What is Hardware Asset Management?

According to the ServiceNow Hardware Asset Management documentation, the Inventory tab of the Hardware Asset Management dashboard provides a comprehensive view of the inventory functions, such as asset audits, disposal orders, stock orders, and shipments. The primary goal of this tab is to show the value from maintaining inventory, such as reducing costs, improving service delivery, and optimizing asset utilization. The Inventory tab also helps users to take inventory-related actions, such as creating or managing stock orders, disposal orders, or shipments, scanning assets with a mobile device, and assigning assets to pallets. References:

ServiceNow Hardware Asset Management: Hardware Asset Management overview

ServiceNow Hardware Asset Management: Inventory view

The reclamation process allows managers to select assets to be reclaimed from the asset service catalog, including hardware, software, and consumables. Only selected items will be processed for return.

Stock rules are the rules that define the minimum and maximum quantities of hardware assets in a stockroom1.

Stock rules help to optimize the inventory levels and avoid overstocking or understocking of hardware assets1.

Stock rules have the following purposes:

To automatically transfer assets when a low quantity threshold is detected in a stockroom: This means that when the quantity of a hardware asset in a stockroom falls below the minimum threshold defined by the stock rule, the system automatically creates a transfer order to replenish the stockroom from another stockroom that has excess quantity of the same asset1.

To send notifications when a low quantity threshold is detected in a stockroom: This means that when the quantity of a hardware asset in a stockroom falls below the minimum threshold defined by the stock rule, the system sends an email notification to the stockroom manager or other stakeholders to alert them of the low inventory level1.

Therefore, the purposes of stock rules that are also options in the question are A. To automatically transfer assets when a low quantity threshold is detected in a stockroom and C. To send notifications when a low quantity threshold is detected in a stockroom.

The other options that are not purposes of stock rules are:

To track stock orders from a vendor: This is not a purpose of stock rules, but a function of purchase orders. Purchase orders are the records that capture the details of the vendor contracts for procuring hardware assets2. Purchase orders help to track the status, quantity, and cost of the stock orders from a vendor2.

To track stock movement between stockrooms: This is not a purpose of stock rules, but a function of transfer orders. Transfer orders are the records that track the movement of hardware assets between stockrooms3. Transfer orders help to track the source, destination, quantity, and status of the stock transfers between stockrooms3.

To send notifications when a stock shipment arrives at a stockroom: This is not a purpose of stock rules, but a function of stock order tasks. Stock order tasks are the tasks that track the fulfillment of asset requests from stockrooms4. Stock order tasks help to send notifications when a stock shipment arrives at a stockroom and when the assets are received and verified4. References:

1: Stock Rules

2: Purchase Orders

3: Transfer Orders

4: Stock Order Tasks

According to the ServiceNow Product Documentation on Stock Rules1, stock rules are records that define the conditions and actions for replenishing the stock of assets in a stockroom when they drop below a specified threshold1.

According to the ServiceNow GlideFast blog post on Stock Rules in ServiceNow2, when creating a stock rule that replenishes from a vendor, the primary requirement for the warehouse stockroom is that it must have an assigned manager and the manager must have a valid email address2.

The reason for this requirement is that the stock rule will generate a purchase order for the procurement of additional assets from the vendor, and the purchase order will be sent to the stockroom manager’s email address for approval2.

The other options are not primary requirements for the warehouse stockroom when creating a stock rule that replenishes from a vendor. The stockroom does not need to have an assignment group, a valid mobile phone, or a valid time zone for the stock rule to work.

Baseline asset states are the predefined states that represent the lifecycle stages of hardware assets in the ServiceNow platform1.

Baseline asset states are used to track the status, location, and ownership of hardware assets, as well as to trigger workflows and tasks for asset management2.

The baseline asset states are: In Stock, In Use, In Repair, In Transit, Retired, Consumed, and Duplicate1.

In Stock means the asset is available in a stockroom and ready for deployment1.

Consumed means the asset is used up or depleted, such as a toner cartridge or a battery1.

Retired means the asset is no longer in use and has been disposed of or recycled1. References:

Baseline asset states

Hardware Asset Management overview

Normalization is the process of aligning hardware asset data with the ServiceNow Content Library, which provides standardized values for manufacturer, product name, and model number. During normalization, the system compares the hardware model data with the content library and assigns a status to indicate the level of match. The status of Match Not Found means that the system could not find any matching record in the content library for the hardware model. The most common cause for this status is missing data, such as an empty manufacturer field or a generic product name. To resolve this issue, the user can manually edit the hardware model record and provide the missing data, or use the lookup feature to search for a matching record in the content library. Alternatively, the user can create a new content library record for the hardware model and link it to the asset record. References:

Hardware model normalization

Normalize hardware models

Create a content library record

According to the ServiceNow documentation, an asset is "any tangible or intangible item that might have value for an organization"1.

The default asset classes in ServiceNow are Hardware, Software License, Consumable, Bundle, Software Entitlement, and Facility1.

These general classes can be used to manage various assets, such as computers, printers, software licenses, office supplies, software subscriptions, and buildings1.

Therefore, facilities, hardware, and software entitlements are considered assets, while contracts and software distributions are not. References:

Asset and configuration item (CI) management - ServiceNow

 According to the ServiceNow Hardware Asset Management documentation, assets can be moved between stockrooms by using transfer orders. A transfer order is a record that tracks the movement of assets from one stockroom to another. A transfer order can be created manually by the stock manager or automatically by the system based on predefined rules or workflows1. A transfer order contains information such as the source and destination stockrooms, the assets to be transferred, the shipment details, and the status of the transfer2.

The other options are not correct because:

Stock orders are records that track the procurement of assets from vendors, not the movement of assets between stockrooms3.

Stock rules are rules that define the minimum and maximum stock levels for each asset model in a stockroom, not the movement of assets between stockrooms.

Transfer rules are rules that define the conditions and actions for creating transfer orders automatically, not the records that track the movement of assets between stockrooms.

Hardware model normalization is a feature that enables users to normalize the details, such as manufacturer, product, model, and device type, of hardware and consumable models1

Hardware model normalization uses the data from the models and compares it against the data in the Hardware Model Normalization Content Service, which is a cloud-based service that provides standardized and enriched information about hardware models1

Hardware model normalization sets the normalized display name for each model record based on three attributes: Name, Manufacturer, and Model number2

The Model Management tab of the Hardware Asset dashboard shows the status of the hardware models in the Product Catalog, such as Matched, Match Not Found, or Not Normalized3

Several of your models are listed as Match Not Found on the Model Management tab of the Hardware Asset dashboard. This means that the normalization process could not find a matching rule in the Content Service for those models3

The potential causes of this are34:

The hardware model content has not yet been downloaded from the Content Service. The Content Service is updated periodically with new and updated rules for hardware models. You need to download the latest content from the Content Service to ensure that your models are normalized with the most accurate and complete information. You can download the content manually or schedule it to run automatically.

Normalization could not match any of the three key fields in the hardware model form with a rule in the Content Service. The three key fields are Name, Manufacturer, and Model number. If any of these fields are missing, incorrect, or inconsistent with the data in the Content Service, the normalization process will fail to find a matching rule. You need to review and correct the data in these fields to ensure that they match the data in the Content Service.

A normalization rule for the hardware model does not exist in the Content Service. The Content Service may not have a rule for some hardware models, especially if they are new, rare, or custom-made. In this case, you can create a custom rule for the hardware model in the Hardware Model Normalization Rules module, or submit a request to the Content Service team to add a rule for the hardware model.

 Operational expenses are the costs incurred by an organization to maintain and use an asset throughout its lifecycle. These costs include the expenses related to the repair, maintenance, upgrade, and disposal of the asset. Some examples of operational expenses are:

Replacement parts: These are the costs of purchasing and installing new parts or components for an asset that is damaged, worn out, or obsolete. For example, replacing a hard drive, a battery, or a keyboard for a laptop.

Maintenance agreements: These are the costs of contracting with a vendor or a service provider to perform regular or preventive maintenance on an asset. For example, paying a monthly fee for a technician to check and service a printer or a scanner.

Other examples of operational expenses are:

Storage costs: These are the costs of renting or owning a space to store an asset that is not in use or awaiting disposal. For example, paying for a warehouse, a locker, or a shelf to keep unused or surplus computers or monitors.

Warranty costs: These are the costs of extending or renewing the warranty coverage for an asset that is still under the manufacturer’s warranty or has expired. For example, paying an extra fee for a one-year or a three-year warranty extension for a tablet or a smartphone.

Hardware asset management, Procurement, and Cost management are the plugins which are not active by default in base Servicenow System

Normalization is the process of restructuring data to maintain consistency, accuracy, and completeness across different sources and systems. Normalization helps to eliminate data duplication, conflicts, and errors, and to ensure that the data conforms to predefined standards and rules. Normalization is especially important for hardware asset management, as it enables users to have a clear and unified view of their hardware models, manufacturers, product names, device types, and other attributes. ServiceNow Hardware Asset Management provides a feature called Hardware Model Normalization, which allows users to normalize the details of their hardware and consumable models using predefined or custom rules, data sources, and schedules. Hardware Model Normalization can be accessed from the Hardware Asset Management application menu in the ServiceNow platform1. References: Hardware Asset Management - ServiceNow, Hardware Asset Management - Product Documentation: Tokyo - ServiceNow, Hardware Asset Management Implement - Customer Success - ServiceNow, Work with hardware normalization - ServiceNow - Now Support, Getting Started with ServiceNow Hardware Asset Management

The ServiceNow Agent mobile app allows the user to conduct asset audits by scanning asset barcodes or QR codes1.

The user can perform audits offline when they are in areas without connectivity1.

The app automatically compares the scanned assets against the expected assets based on the inventory records to identify discrepancies1.

The user can also view the audit results and generate reports from the app2. References:

Audit your inventory - Product Documentation: San Diego - ServiceNow

Hardware Asset Inventory Management - ServiceNow

Hardware Asset Management - ServiceNow

Once a catalog item has been requested, the mechanism that determines the approvals and tasks that are triggered in the application is the flow12.

A flow is a graphical representation of a business process that consists of one or more actions, such as approvals, tasks, notifications, scripts, etc., that are executed based on certain conditions and triggers12.

A flow can be associated with a catalog item to define the fulfillment process for that item, such as who needs to approve it, what tasks need to be performed, and what notifications need to be sent12.

A flow can be created and managed using the Flow Designer, a low-code development tool that allows users to design and test flows without writing any code12.

A flow can be activated or deactivated, versioned, and published to make it available for use12.

A flow can be monitored and debugged using the Flow Execution Details and the Flow Logs12. References:

Flow Designer

Service Catalog Request Fulfillment

Assets are tangible items tracked for lifecycle management and financial purposes. Facilities (e.g., buildings), servers, and network cables are physical assets. Software licenses and distributions are intangible and treated differently in ServiceNow Asset Management.

 According to the ServiceNow Hardware Asset Management documentation, ITAM personas and ITAM roles are different concepts that relate to the types and access of users of the product. The difference between them are as follows:

ITAM personas are user profiles that represent the typical users of the ITAM product and their business needs. They are not tied to any specific role or permission, but rather describe the goals, challenges, and expectations of the users. For example, some of the ITAM personas are IT Asset Manager, IT Asset Analyst, IT Procurement Manager, and IT Finance Manager1.

ITAM roles are access controls that determine what features and functions a user can access in the ITAM product. They are assigned to users or groups based on their responsibilities and tasks. They can also be combined to grant multiple levels of access to a user. For example, some of the ITAM roles are asset, asset_admin, asset_tagging, and procurement2.

Therefore, a user may have multiple roles, but a single persona (A), roles control access to features in the product (B), personas represent types of users of the product ©, and a user may have multiple roles and personas (F) are the correct statements that describe the difference between ITAM personas and ITAM roles. References:

1: ITAM personas 2: ITAM roles

The Asset Operations view consolidates tasks such as RMAs, audits, disposals, and stock orders into a single workspace, enabling managers to streamline operations efficiently.

According to the ServiceNow Hardware Asset Management documentation, a loaner asset is a temporary asset that is provided to a user for a specific period of time, such as when their primary asset is being repaired or replaced1. Users can request loaner assets from the Service Catalog, where they can select the type, quantity, and duration of the loaner asset they need2. If the requested asset is not available in the local stockroom, the request is wait-listed until the asset becomes available3. Users may request loaner assets even when the requested asset is not available in the local stockroom because the wait-listed loaner asset requests provide visibility to the demand for loaner orders. This visibility helps the asset managers to plan and optimize the loaner asset pool, as well as to identify and address any gaps or bottlenecks in the loaner asset fulfillment process.

The other options are not correct because:

The request does not create an automatic transfer order to move assets from a warehouse with in stock assets. Transfer orders are created manually by the stock manager to move assets between stockrooms.

The wait-listed loaner asset requests do not provide visibility to streamline internal transfer order flows. Transfer order flows are managed by the stock manager using the Transfer Order Management module.

The request does not automatically create a purchase order to obtain the assets from a vendor. Purchase orders are created manually by the procurement manager to order assets from vendors.

According to the Hardware Asset Management documentation, the hardware asset management content service is a cloud-based service that provides normalized and enriched hardware model data to the ServiceNow platform, such as manufacturer name, model name, model number, and product lifecycle information.

The hardware asset management content service helps customers identify and manage their hardware assets more effectively, as well as plan for hardware refreshes based on end-of-life (EOL) and end-of-service (EOS) dates1.

The elements that are provided by the hardware asset management content service are as follows1:

Manufacturer lifecycle dates: The dates when the manufacturer stops selling, supporting, or servicing a hardware product.

Manufacturer: The name of the company that produces the hardware product.

Model name: The name of the hardware product, such as Dell Latitude E7450 or HP ProLiant DL380 Gen10.

Therefore, the correct answers are options A, D, and E, as they are the elements that are provided by the hardware asset management content service. References:

Hardware Asset Management documentation

What is Hardware Asset Management?

The Procurement tab of the Hardware Asset dashboard is a graphical representation of the hardware asset procurement across the enterprise1.

The Procurement tab provides the following information1:

Hardware expenditure by vendor: This shows the total amount spent on hardware assets from each vendor in the current fiscal year. This helps to analyze the vendor performance and negotiate better contracts.

Requests that require sourcing: This shows the number and status of asset requests that need to be fulfilled by purchasing new hardware assets from a vendor. This helps to prioritize the procurement activities and optimize the inventory levels.

Therefore, the information that are also options in the question are C. Hardware expenditure by vendor and F. Requests that require sourcing.

The other options that are not information on the Procurement tab are:

Hardware nearing end of warranty: This is an information on the Inventory tab of the Hardware Asset dashboard. This shows the number and percentage of hardware assets that are nearing or have expired their warranty period1.

Hardware model normalization status: This is an information on the Normalization tab of the Hardware Asset dashboard. This shows the number and percentage of hardware models that are normalized or not normalized1.

Hardware models up for end of life: This is also an information on the Inventory tab of the Hardware Asset dashboard. This shows the number and percentage of hardware models that are approaching or have reached their end of life date1.

New hardware assets found by audits: This is also an information on the Inventory tab of the Hardware Asset dashboard. This shows the number and percentage of hardware assets that were discovered by the asset inventory audit process but were not previously recorded in the CMDB1. References:

1: Hardware Asset Dashboard

A blind audit is a type of inventory audit that does not provide any information about the expected assets in a location. The auditor scans all the assets in the location and compares them with the records in ServiceNow1.

To perform a blind audit, you need the Hardware Asset Management (HAM) application, which enables you to manage the lifecycle of your hardware assets, and the ServiceNow Agent mobile app, which allows you to scan asset tags and barcodes using your mobile device12.

The ServiceNow My Assets mobile app is used to view and request assets from the enterprise asset catalog, not to perform audits3.

The Software Asset Management (SAM) application is used to optimize software licenses and compliance, not to perform audits4.

The ITSM Asset Management application is used to track the financial, contractual, and inventory details of hardware and devices, not to perform audits. References:

1: Audit your inventory - Product Documentation: San Diego - ServiceNow

2: Enterprise Asset Inventory Management - ServiceNow

3: My Assets mobile app - Product Documentation: San Diego - ServiceNow

4: Software Asset Management - ServiceNow

: IT Asset Management - ServiceNow

A model category is a classification of models that defines how they are managed in the system1. It determines the behavior and attributes of the models and the assets or configuration items (Cls) that are created from them1.

Model categories can be used to group consumables, assets, or services in the product catalog or the service catalog, but this is not their primary function. Their primary function is to define the relationship between configuration management and asset management1.

Configuration management is the process of identifying, tracking, and verifying the configuration items (Cls) in an IT environment and their relationships2. Asset management is the process of tracking and managing the financial, contractual, and inventory details of IT assets throughout their lifecycle3.

Model categories determine when to create assets from configuration items (Cls) based on the asset tracking strategy1. For example, some model categories, such as Computer, create assets automatically when Cls are discovered or imported1. Other model categories, such as Consumable, require manual creation of assets from the product catalog1.

Model categories also provide the link between configuration management and asset management by allowing asset managers to view the configuration data of the assets and configuration managers to view the asset data of the Cls1. This enables better visibility, control, and alignment of IT assets and services1.

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]

Fixed assets in ServiceNow are classified as long-term assets that are used in operations and have a useful life exceeding one year, such as equipment, buildings, and vehicles. They are distinct from intangible and short-term assets.

According to the ServiceNow Hardware Asset Management documentation, hardware model lifecycle phases are the stages that a hardware model goes through from its introduction to the market to its retirement. The valid hardware model lifecycle phases are:

•Pre-release: The hardware model is not yet available for purchase, but it is planned to be released in the future.

•General Availability: The hardware model is available for purchase and supported by the manufacturer.

•End of Life: The hardware model is no longer available for purchase or supported by the manufacturer.

•Disposal: The hardware model is disposed of or recycled.

According to the ServiceNow Hardware Asset Management documentation, a stockroom is a location where assets are stored and managed. A stockroom must have an assigned manager who is responsible for overseeing the stockroom operations and inventory. The stockroom manager must have a valid email address to receive notifications and alerts related to the stockroom, such as low stock levels, stock transfers, and stock orders. The other options are not primary requirements for the warehouse stockroom. The stockroom does not need to have an assignment group, a valid time zone, or a valid mobile phone.

During an inventory audit, if you accidentally scan the same asset twice, the Hardware Asset Management (HAM) application will automatically remove the duplicate records and only import the unique scans. This is because the HAM application uses the asset tag or the serial number as a coalesce field, which prevents duplicate records from being created or updated in the hardware asset table. Therefore, you do not need to worry about scanning the same asset twice, as the HAM application will handle the duplicates for you. References:

Audit your inventory, which provides a step-by-step guide on how to perform scheduled or blind audits of asset stockrooms and other locations using the Agent mobile app and the Now Platform.

Hardware Asset States, which describes the different states and substates of hardware assets and how they are used to track the asset lifecycle.

Importing Hardware Assets into ServiceNow, which provides a step-by-step guide on how to import hardware assets into ServiceNow using an excel spreadsheet, an import set table, and a transform map.

The Expected Assets list is populated when the asset manager starts the audit by clicking the Scan button on the asset audit form1.

This list shows the assets that are expected to be found in the audit location based on the asset records in the CMDB1.

The asset manager can then use a barcode scanner or a mobile device to scan the actual assets in the location and compare them with the expected assets1.

The asset manager can also manually add or remove assets from the expected assets list if needed1. References:

1: Hardware Asset Inventory Audit

According to the Hardware Asset Management documentation, a transfer order is a record that tracks the movement of assets from one stockroom to another.

A transfer order line is a record that specifies the quantity and type of assets to be transferred, as well as the source and destination stockrooms1.

When using the HAM application, what happens when you create a new transfer order line on a transfer order is that a transfer order line task is automatically created to move the transfer order line from one stage to another1.

A transfer order line task is a record that tracks the progress of the transfer order line through the following stages1:

Requested: The transfer order line is created and waiting for approval.

Approved: The transfer order line is approved and ready for fulfilment.

Fulfilled: The transfer order line is fulfilled and the assets are shipped from the source stockroom.

Received: The transfer order line is received and the assets are checked in at the destination stockroom.

Closed: The transfer order line is closed and the transfer is complete.

Therefore, the correct answer is option C, a transfer order line task is automatically created to move the transfer order line from one stage to another, as it describes what happens when you create a new transfer order line on a transfer order. References:

Hardware Asset Management documentation

What is Hardware Asset Management?

A field service management (FSM) change task is a task that is created from a change request and assigned to a field service agent to perform work on a configuration item (CI) or an asset1.

An asset task is a task that is created from an asset record and linked to an FSM change task to track the work done on the asset2.

When an asset task is completed, the asset record associated to the task is automatically updated with the latest information, such as location, status, assignment group, assigned to, and so on2.

This feature removes the need to manually update the asset record after completing the FSM change task, saving time and ensuring accuracy2.