Hello, how can we help you?

Recent Searches: Copilot - 2.2.2 - Workspace - 2.2.2 - Workflow - 2.2.2 - Training - 2.2.2

SoftExpert Action plan tasks

 

Introduction

Tasks are pending system activities for which the user is responsible. They are divided into two categories: Execution and Tracking.

Tracking tasks are tasks for which the user is responsible, but that are executed by another user.

Execution tasks are pending tasks that the user must execute within a deadline or defined period.

See further details on SoftExpert Action Plan tasks. They will be listed by their names:

 

Execution tasks

Planning approval

Who receives it: Users who compose the responsibility route for the planning approval of the action plan or isolated action.
When: The planning of the action plan or of the isolated action is finished.
Purpose: Approve the planning of an action plan or an isolated action.
Where: In the My tasks > Execution menu. This task can also be executed through the button available in the notification e-mail related to it.
 
 

Request execution

Who receives it: The party responsible for the execution of the request, defined in the SoftExpert Request component.
When: The issue/approval step (as configured) is finished by the due responsible parties in the SoftExpert Request component.
Purpose: Create action plans to meet the needs of the requesters.
Where: In the My tasks > Execution menu.
 
 

Action rescheduling request execution

Who receives it: User and team members responsible for the action plan to which the action belongs. 
User and team members responsible for the isolated action.
When: The issue/approval step (as configured) is finished by the due responsible parties in the SoftExpert Request component. The issuance of action rescheduling requests can be executed through the Request section from the Details tab of the action data screen, while it is under "Execution".
Purpose: To reschedule the start and end dates and/or the responsible for the execution of the action.
Where: In the My tasks > Execution menu.
 
 

Action execution

Who receives it: SoftExpert Suite user and team members responsible for executing the action of the plan. 
SoftExpert Suite user and team members responsible for executing the action of the plan.
When: The planning step of the action plan or the isolated action that does not have the approval step configured is finished and sent to the next step. 
The action plan or the isolated action planning is finished.
Purpose: Allow the responsible parties to start, enter important information about the execution, and finish the execution of the planned action, either isolated or action plan actions.
Where: In the My tasks > Execution menu. External users responsible for action execution may execute the isolated actions and plan actions through the Customer panel.
 
 

Planning

Who receives it: User and team members responsible for the action plan planning. 
User and team members responsible for the isolated action.
When: The action plan remains in planning, that is, it is not sent to the next step. 
The isolated action remains in planning, that is, it is not sent to the next step.
Purpose: To finish the planning of an action plan or isolated action, enabling to perform the necessary adjustments before sending it to the next configured step.
Where: In the My tasks > Execution menu.
 
 

Action verification

Who receives it: Users who compose the responsibility route for the verification of the action plan action.
When: The execution of a planned action plan action is finished 
The planning of the plan to which an immediate action belongs is finished or approved, according to the settings made in its category.
Purpose: Allow the responsible parties to confirm whether the execution of the action was implemented in accordance with the pre-established objectives.
Where: In the My tasks > Execution menu. This task can also be executed through the button available in the notification e-mail related to it.
 
 

Effectiveness verification

Who receives it: Users that compose the route responsible for the effectiveness verification of the action plan or isolated action.
When: The execution of a planned isolated action is finished. 
The planning of an immediate isolated action is finished or approved according to the configurations set in its category. 
The execution of all the actions that make up a plan is finished or verified according to the configurations set in its category.
Purpose: Allow those responsible to confirm whether the implementation of the isolated action/action plan is in accordance with the pre-established objectives.
Where: In the My tasks > Execution menu. This task can also be executed through the button available in the notification e-mail related to it.
 
 

 

Tracking task

Tracking

Who receives it: User and team members responsible for the action plan. 
User and team members responsible for the isolated action.
When: The planning step of the action plan or isolated action is finished and sent to the next step.
Purpose: Track and perform the necessary adjustments in the action plan/isolated action during its execution.
Where: In the My tasks > Tracking menu.
 
 

 

Conclusion

As tasks are executed and closed, they are no longer displayed in the list of pending records in the Task menu.


Was this article helpful?