You control the classic timecard UI using the settings in the Timecard configuration group.
You can control the enhanced timecard UI from the Timecard configuration group or the timecard custom settings. The fields in custom settings "Timecard Settings" and "Timecard Entry UI Personal Settings" have the same names as those in the Timecard configuration group.
If you opt to use the PSA Timecard configuration group to control the enhanced timecard user interface, all settings are org-wide; personal (individual user) settings are not available unless you use the timecard custom settings.
Contact FinancialForce Customer Support for more details.
Use these settings to manage the enhanced timecard user interface in custom settings in FinancialForce PSA
Use these global UI settings to manage the Timecard user interface when the Timecard Entry UI Switch is selected.
Use these settings to control user-specific behavior for the Timecard Entry pages. Each user experiences the results of these settings separately.
This section lists the timecard settings that you can only change in the Timecard configuration group. For other timecard configuration settings in the Timecard configuration group, see "Timecard Settings" and "Timecard Entry UI Personal Settings".
| Field | Description |
|---|---|
|
|
Indicates whether the Closed for Time Entry checkboxes on parent records such as projects, assignments and milestones only stops time entry on new or unsubmitted timecards. When the option is enabled, users cannot enter new timecards or submit a timecard that was not previously submitted. |
|
|
Indicates whether audit notes are automatically created when the assignment or project in a timecard is changed. Four tokens are used:
For instance, the default value is: User <user> changed the Project from <oldproject> to <newproject> on <date>. |
|
|
Indicates whether the timecard end date must not be later than the Assignment End Date. When this option is set, timecard hours for days after the Assignment End Date must be zero. |
|
|
Indicates whether the timecard start date must not be earlier than the Assignment Start Date. When this option is set, timecard hours for days prior to the Assignment Start Date must be zero. |
|
|
Timecards that have a status which is included in the values for this field appear in the estimates versus actuals calculations. When a user changes the status of a timecard to a status that is not included in the list, the actuals for that timecard are removed from the estimates versus actuals calculation. For example, if you change the status from Submitted to Rejected, that timecard is no longer included in the calculation. |
|
|
Timecards with a status other than the ones listed in the values are included when PSA calculates missing timecards. Add a value to the missing-timecard-status field for each status that you do not want to generate a missing timecard for. You can add :Saved, Submitted and Approved. |
|
|
Indicates whether users can save timecards with zero hours. |
|
|
Indicates whether a recall link is displayed on submitted timecards. |
|
|
Set the value to true if you want users to be able to submit timecards with zero hours, otherwise set the value to false. |
|
|
If you want the Assignment roll-up fields to update when users submit timecards, set the value to true, otherwise set the value to false. |
|
|
If you want the Milestone roll-up fields to update when users submit timecards, set the value to true, otherwise set the value to false. |
|
|
Indicates whether the Approver field on a timecard is updated when a user edits it. This configuration option is dependent on the AssignProjectManagerToTimecardApprover configuration option in the ASM Triggers configuration group. |
| update-tch-from-tc-sync | Indicates whether changes made on timecard splits are carried out on the related timecard at the time the change is made on the timecard split. |