In this tab, it is possible to parameterize if the resources will be allowed to enter the hours that were spent to execute the tasks of the type. To do that, check the Allow enter time option and fill out the fields of the following sections:
Inhibit time entry
Option
|
Checked
|
Unchecked
|
Approved
|
The timesheet will be blocked after the approval of the timesheet for the tasks.
|
The timesheet for the tasks of this type will not be blocked after its approval.
|
After finishing the task
|
When tasks are closed, the timesheet will be blocked.
|
The timesheet for the tasks of this type will not be blocked after its closure.
|
If the hours entered exceed the planned hours by ___ percent
|
The timesheet will be blocked when exceeding a percentage of the total hours allocated for the resources in the task. In the field that will be enabled, enter the percentage of exceeding time the timesheet will be blocked from.
|
The total percentage of allocated hours will not impact the blocking of the timesheet in the tasks of this type.
|
Before
|
The timesheet for the tasks of this type will be blocked before a certain date. In the field that will be enabled, enter the date before which the timesheet will be blocked.
|
The timesheet for the tasks of this type will not be blocked before a specific date.
|
|
Mandatory to fill out the [Description] field]
|
When entering time in the tasks of this type, it will be mandatory to fill out the Description field.
|
Filling out the "Description" field will not be mandatory when entering time in the tasks of this type.
|
Add automatically to timesheet
|
When starting the execution of the tasks, they will be automatically added to timesheet screen listing. By default, this option will be displayed as checked by the system.
|
Tasks must be manually added to the screen for their timesheet to be performed.
|
Allow the resource to start a task through timesheet*
|
If the logged user is a resource allocated to the task and is not responsible for it, the task will be available for a timesheet. Thus, when the resource performs the timesheet, the task execution will be started.
|
The task will not be available for timesheet for the resource allocated to it while its execution is not started by the responsible party.
|
This option will only be applied to the task if the "Allow the allocated resources to perform tasks" option is unchecked in its data screen.
|
|
In this section, it is possible to define that the time entered in the tasks of this type must be approved. To do this, check the Timesheet approval option and fill in the following fields:
Type: Select one of the following options to define the party responsible for the approval:
The system makes available the following fields:
Route type: Define whether the approval route will be:
▪Variable: Allows the route to be selected/edited during the timesheet of tasks of this type, as well as editing its members. ▪Fixed: Allows the route to be selected/edited during the timesheet of tasks of this type, however, it will not be possible to edit its members. ▪Fixed & unique: A default approval route will be set for all timesheets of tasks of this type. The route selected in the respective field cannot be changed (nor its members) when filling out the timesheet. Responsibility route: Select the responsibility route that will be used for approval. Use the other buttons next to the field to add a new responsibility route, edit the data of the selected route or clear the field. The filling in of this field is mandatory if the type of route is "Fixed & unique". If another route type option is selected and this field is filled in, when entering the time of the task, the system will use the informed route; however, it will be possible to edit it.
|
Fill in the following fields:
User: Select the user who will approve the timesheet. Use the other buttons next to the field to add a new user who will be responsible for the timesheet, fill it with the logged-on user data, and clear the field.
Deadline: Enter the number of days the user will have to perform the approval.
|
Use the following options to parameterize when the parties responsible for the timesheet approval will be notified about the Timesheet approval task through the "My Tasks" e-mail notification:
Option
|
Checked
|
Unchecked
|
Notify before due date
|
The responsible party will be notified before the day on which the deadline to approve the timesheet expires. Use the Notify before field to enter how many days in advance the notification will be sent.
|
The responsible party will not be notified before the deadline to approve the timesheet expires.
|
Notify on due date
|
The responsible party will be notified on the day on which the deadline to approve the timesheet expires.
|
The responsible party will not be notified on the day the deadline to approve the timesheet expires.
|
Notify after due date
|
The responsible party will be notified after the deadline to approve the timesheet expires. Use the Notify after field to enter the number of days after the approval deadline expiration in which the notification will be sent. In the Frequency field, enter the frequency, in days, in which this notification will be sent.
|
The responsible party will not be notified after the deadline to approve the timesheet expires.
|
Check the Subordinates' tasks option to define who will be notified about the timesheet approval through the "Subordinates' tasks" e-mail notification (SE Configuration). In that case, the following options are available:
Option
|
Checked
|
Unchecked
|
Notify leader of responsible user
|
The leader of the user responsible for the approval will receive the timesheet approval task status notification.
|
The leader of the user responsible for timesheet approval will not be notified.
|
Specific user
|
A user of the system will receive the timesheet approval task status notification. In that case, fill in the following fields:
▪User: Select the desired user. ▪Go up to __ level(s): Enter how many levels above the responsible user leader level will be notified about the timesheet approval task. ▪Frequency: Enter the number of days past due that the system will go up the hierarchy until it reaches the configured level. |
There will be no notifications for a specific system user about the timesheet approval task.
|
If the Subordinates' tasks option is not checked, the timesheet approval notification will not be sent via e-mail.
The configurations above overwrite the parameterizations referring to the system notifications in the SE Configuration component, but only those referring to the SE Time Control component.
|
|
In this section, it is possible to parameterize for it only to be possible to enter overtime hours in the tasks of this type through the issuance of a request. To do that, select the Overtime request is required option and, in the Request type field, select the type that will classify the requests related to the overtime. Use the other buttons next to the field to add a new request type, edit the data of the selected request type and clear the field.
▪In order for this resource to function properly, it is necessary for the SE Request component to be part of the solutions acquired by your organizations. ▪The request types displayed on the selection screen may vary according to the permissions granted in their security list in the SE Request component. Refer to the component-specific documentation for more details on configuring request types. |
|
|