SoftExpert Request tasks
Prerequisite
- Access to the My tasks menu.
Introduction
To-do tasks are assignments for which a user is responsible. They are divided into two categories: execution and tracking.
The tracking section gathers the tasks for which the user is responsible, but which are executed by another user.
The execution section gathers all to-do tasks that the user needs to execute within a defined deadline or period.
Check further details about the tasks generated in SoftExpert Request:
Execution tasks
Request approval
Who receives it | Members of the route responsible for the approval. |
When | The request issuance is finished. |
Purpose | To approve or reject the issuance of a request. |
Request issuance
Who receives it | User who started the request issuance. |
When | The request was created, but was not sent to the next step. |
Purpose | To alert the user of the existence of a request that needs to be issued. |
Request closure
In order for this task to be generated, the closure step must have been configured in the request type.
Who receives it | User who issued the request. |
When | The request execution is closed. |
Purpose | To allow the issuer to evaluate the execution of the requested service. |
- The tasks can also be executed through the button available in the e-mail notification.
- Refer to the How does approval work? article to learn how to use this resource.
Tracking task
Request tracking
Who receives it | User who issued the request. |
When | The request issuance is finished. |
Purpose |
To allow the user to track the execution of the request they have issued. If the logged user has full or specific control over the records of a department, position, or user, as configured in SoftExpert Administration, from the File > Organizational unit > User (AD004) menu, the system will also display the requests issued by that department, position, or defined user. |
Conclusion
As tasks are executed and closed, they are no longer displayed on the list of pending records in the task menu.