|
In this tab, it is possible to parameterize if the resources will be allowed to enter the time that was spent in the meetings of this type. To do that, check the Enable timesheet option and fill in the fields of the following sections:
The configurations made on this tab will only work correctly if the SE Time Control component is part of the solutions acquired by your organization. These configurations will impact the Timesheet screen. Refer to this section for more details on the timesheet.
|
Inhibit time entry
Option
|
Checked
|
Unchecked
|
Approved
|
The timesheet will be blocked after the approval of the timesheet for the meetings.
|
The timesheet for the meetings of this type will not be blocked after its approval.
|
Before
|
The timesheet for the meetings 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 meetings of this type will not be blocked before a specific date.
|
Mandatory to fill out the [Description] field
|
When entering time in the meetings 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 meetings of this type.
|
|
In this section, it is possible to define that the time entered in the meetings 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 meetings of this type, as well as editing its members. ▪Fixed: Allows the route to be selected/edited during the timesheet of meetings 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 meetings 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 (SE Time Control) that will be used for approval. Use the buttons next to the field to add a new responsibility route and clear it. It is important to note that filling in this field is mandatory if the route type selected previously is "Fixed & unique". If another Route type option is selected and this field is filled out, in the meeting timesheet, 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" email 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's 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. ▪The responsible parties entered in this section will enter the timesheet approval through Timesheet approval. |
|
In this section, it is possible to parameterize for it only to be possible to enter overtime hours in the meetings 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 feature 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. |
|
|
