Skip to main content
Version: 1.3.3

Tasks

Any substantial change to the asset form, such as a new state, location, or other, can only be made through a corresponding task. This enables you to maintain a transparent and flawless workflow during the whole life cycle of an asset in your company. Some tasks can be initiated by the system, for example, disposal tasks for the assets with an expired useful life or when the Not found checkbox remained on the asset form longer than permitted by the system property.

Roles

The ITAM role model contains various roles with access to specific forms and functionality corresponding to employees' job duties. Each article of this section provides information about the roles that users need to manage specific task types. The basic set of roles for the tasks includes:

  • itam_agent – can view all tables and forms, but access is restricted according to the ACL.
  • itam_process_manager and itam_operation_specialist – both roles can create, process, cancel, and complete tasks.
  • itam_responsbile – can approve tasks.

Filters

To facilitate your search for the required documents, available assets, employees, stocks, and other data, most fields and widgets include preconfigured filters. For example, each task has a custom filter applied before adding assets. This ensures that the system prevents adding assets to a task if they do not match its type or lack the required attributes on their forms. In each article, you will find detailed information about the requirements for the assets added to the task. However, there are general conditions that apply to all assets:

  • Asset records must be active; otherwise, you cannot add assets to a task. For example, assets from an empty consignment or assets decommissioned due to expired useful life.
  • Assets cannot be added to more than one task simultaneously. For example, if an asset is already added to a maintenance task, you cannot create another task with the same asset.
  • You cannot add an asset with the Not found checkbox selected to a task, except the decommissioning task.

Task states

The task states are changed using the UI actions available to the assigned users. The UI actions set for the task align with the task state models. Note that some tasks do not require mandatory approval state and can be completed without it.

Approvals

If tasks are rejected, you can resend them for approval as many times as needed. Approval tickets for additional approvers are sent separately. If you reapprove tasks, you need to add them again.

Find detailed information about the ITAM tasks in the articles below:

📄️ Return to Stock

Within the return to stock task, you can return assets from use to the stock for further allocation to another user or decommissioning. Only the assets of one user can be added to the task, they must be in the In operation stage, In use state and refer to the same stock. When you add assets to the task, their stage changes to Transfer and their state changes to Unavailable. When the task is completed, the stage of the assets will change to Storage, the state to Available, and the value of the User field on the asset forms will be cleared.