SoftExpert Asset tasks
Prerequisite
- Access to the My tasks menu.
Introduction
Tasks are records generated for certain users to take an action. They are divided into two categories: Execution and Tracking.
The tracking category contains the tasks for which the user is responsible, but whose execution is performed by another user. SoftExpert Asset does not generate tracking tasks.
The execution category gathers all pending actions the user needs to take within a defined deadline.
See further details about the system-generated tasks:
Execution tasks
Inventory approval
| Who receives it | Members of the approval routed defined in the Approval tab of the inventory data screen. |
| When | The asset inventory execution is closed, provided that the inventory activity has been planned with the execution approval step. |
| Purpose | To approve the inventory execution of the assets from a specific location. |
Purchase request execution
| Who receives it | The party responsible for executing the request; said party is defined in the SoftExpert Request component. |
| When | The issue/approval step is finished by the due responsible parties in the SoftExpert Request component. |
| Purpose | To allow the responsible parties to execute asset purchase requests. |
Inventory execution
| Who receives it | Members of the team responsible for executing the inventory. |
| When | An inventory activity that is in the planning step is sent to the execution step. The inventory execution has been rejected, if this step was configured during the creation/planning of the inventory. |
| Purpose | To execute the inventory of the assets from a location. |
Asset reservation
| Who receives it | Members of the team responsible for the asset. |
| When | The reservation request is issued. |
| Purpose | To allow the responsible parties to reserve the asset. For example, if the asset has been reserved for maintenance, it must be checked out for maintenance. |
Check-in from calibration
| Who receives it | Members of the team responsible for the asset calibration event. |
| When | An asset returns from the reservation for calibration. |
| Purpose | To define information of the asset that has returned from calibration. |
Check-in from maintenance
| Who receives it | Members of the team responsible for the asset maintenance event. |
| When | An asset returns from the reservation for maintenance. |
| Purpose | To define information of the asset that has returned from maintenance. |
Check-in from usage
| Who receives it | Members of the team responsible for the asset usage event. |
| When | A check-out for usage protocol is issued. |
| Purpose | To define information of the asset that has returned from maintenance. |
Asset revision
| Who receives it |
ISO9000 based: - Draft/Review/Approval/Release: User defined as participant in the asset revision. - Closure: User who created the revision, if the "Manual" option has been selected in the Revision publication field of the revision data screen. Workflow: Users defined as executors of the workflow activity. |
| When |
ISO9000 based: Draft: A new revision starts or a participant rejects a revision step. Review/Approval/Release: The drafter executes the draft task. These steps are optional and the responsible parties receive them in this exact order. Closure: The execution of the last revision step is completed. Workflow: A new revision starts and a process flow activity needs to be executed. |
| Purpose | To control the changes and versions of the assets saved in the system. |
- Tasks can also be executed through the button available in the notification e-mail related to them.
- Read the What is a revision? article for further details on revisions.
- For more details on the to-do tasks menu, click here.
Conclusion
As tasks are executed and finished, they are no longer displayed on the list of pending records in the task menu.