The Remote Time Sheet Applet has been obsoleted by TimeAnywhere.
This registry entry is required for the Remote Timesheet applet. It controls the format of the time and expense display sections of the remote time screen, the number of previous and future periods that may be accessed, the first day (and number of days) of the period, retry and timeout constants, etc. Note that the data entry fields in the top portion of the Time & Expense Screen are managed by the screens.txt file. Contact Data-Basics support for details.
Consult the Remote Time Sheet Setup for additional information on setting up the Remote Time and Expense software.
Testing Your Registry Entries
The system does not verify the validity of registry entries. Be sure to test your registry entries after completing them to verify that they are functioning correctly.
Setting Values are Uppercase-Lowercase Sensitive:
The Setting Value is case-sensitive: be sure that you enter the value exactly as specified in the documentation. If the documentation specifies a value of true, do NOT enter True or TRUE.
Id
The Id of the Registry Entry must conform to one of the following format:
sys-remotetime
sys-remotetime-securityid
sys-remotetime-employeetype
sys-remotetime-style
sys-remotetime-userid
sys-remotetime registry entries are continuously cumulative and allow overrides to be set. When specifying an addition or override, you need only set the options that you wish to add or change. This makes it easier to implement different time entry setups can be specified for different employees by Security Id, Employee Type, style or even User Id.
Example:
Suppose that you want most of your employees to be limited to entering time to this week, last week, and next week. However, you want your project managers to be able to enter time for the last 6 weeks through the following two weeks. In this situation, you would set up a base level sys-remotetime entry with the periodspast and periodsfuture options set to allow time entry to last week, this week and next week. In addition, you would also create a sys-remotetime-style entry (say, sys-remotetime-pm) for project managers. In sys-remotetime-pm, you would only specify the overrides to periodspast and periodsfuture options (to allow project manages to enter their time to a broader time range). When Project Managers entered their time, the Remote TIme Entry screen would be identical to the other employees except for the allowable periods in the past and future. Note that in this case, the Remote Time Sheet Style field in the Employee record would have to be set to pm for all project managers.
Description: This field is optional but recommended for clarity (Remote Timesheet Configuration).
Setting Key: reports Setting Value: UDReportId1,UDReportId2,...
where UDReportId1 is replaced by the Id of the user-defined report (or reports) that Remote Time users should have access to. Note that these reports must exist in your database.
Setting Key: hours Setting Value: BegValue _EndValue@increment,Value1,Value2...
controls the time increments that appear in the drop-down hours box. BegValue should be replaced by the first value to be selected from the list; it must be followed by an underscore. EndValue should be replaced by the last value, and @increment by the incremental value. The Value1, Value2... option may be used to specify additional selections, such as 40 or 80 hours.
Example:
The following entry would result in values of .25, .50, .75 through 8.0 (in quarter hour increments) and the values of 40 and 80 appearing on the drop-down list:
Setting Key: hours Setting Value: .25_8@.25,40,80
Setting Key: periodspast Setting Value: number
this entry defines the number of previous periods that a user is allowed to enter time to. A period is defined by the days option (defined below) and is typically one week.
Example:
periodspast=2 (or Setting Key: periodspast Setting Value: 2) would mean that a user could time for the two previous weeks as well as the current period. If this option is not specified, time cannot be entered remotely to previous periods.
Setting Key: periodsfuture Setting Value: number
this entry defines the number of periods in the future that a user is allowed to enter time to. A period is defined by the days option (defined below) and is typically one week.
Example:
periodsfuture=1 (or Setting Key: periodsfuture Setting Value: 1) would mean that a user could enter time for the current period and the next period. Typically, periodsfuture would be set to enable an employee to enter vacation time ahead of time.
Setting Key: firstday Setting Value: day
where day is replaced by the day of the week that begins the period. Valid entries are Fri, Sat, Sun, Mon, Tue, Wed, Thu.
Setting Key: days Setting Value: numberofdays
where numberofdays is replaced by length of the period, typically 7. This entry sets the number of days in the time entry grid at the top of Remote Time screen.
Note: 8 Day Period
Under certain highly specific circumstances, the period may be set to eight days. For example, suppose that certain employees work uneven work weeks (one Monday-Thursday four-day week of 36 hours followed by a five day week of 44 hours). However, for management and tax reporting, each week may not exceed 40 hours. In this case, an 8 day period could be specified in conjunction with the AM/PM option (discussed below), and the starting day set to Friday. On every other week (where an employee worked on Friday), the AM hours would be allocated to the previous period, and the PM hours would be allocated to the current period.
Setting Key: AMPM Setting Value: true
this option should only be entered if the first day if AM hours on the first day of the period should be set to one period, and PM hours to the next (as discussed in the example above.
Setting Key: LaborGridColumns Setting Value: field1,field2,....
where field1,field2,... are replaced by the fields that you wish to appear on the labor entry grid, in the order that you wish them to appear. Note that commas are used to separate the field names. Valid values for the fields include the following:
date hours job costcategory
paytype description status posted
costcode trxdate index workorder
Setting Key: LaborGridLabels Setting Value: field1label,field2label,....
where field1label,field2label,... are replaced by the labels that you wish to appear on the labor entry grid, in the order that you wish them to appear. Note that commas are used to separate the field labels.
Setting Key: LaborGridWidth Setting Value: width1,width2,....
where width1,width2,... are replaced by the width of the columns (defined in the LaborGridColumns) in pixels. Note that commas are used to separate the column widths.
Setting Key: ExpenseGridColumns Setting Value: field1,field2,....
where field1,field2,... are replaced by the fields that you wish to appear on the expense entry grid, in the order that you wish them to appear. Note that commas are used to separate the field names. Valid values for the fields include the following:
date job costcategory otherrate units
unitcost amount description status posted
costcode trxdate index workorder
Setting Key: ExpenseGridLabels=field1label,field2label,....
where field1label,field2label,... are replaced by the labels that you wish to appear on the expense entry grid, in the order that you wish them to appear. Note that commas are used to separate the field labels.
Setting Key: ExpenseGridWidth Setting Value: width1,width2,....
where width1,width2,... are replaced by the width of the columns (defined in the ExpenseGridColumns) in pixels. Note that commas are used to separate the column widths.
Setting Key: TimeSumStartPercent Setting Value:percent1
Setting Key: TimeSumEndPercent Setting Value: percent2
Setting Key: TimeSheetStartPercent Setting Value: percent3
Setting Key: TimeSheetEndPercent Setting Value: percent4
These fields are used to control the position and amount of screen space allocated for the various sections of the Remote Time Entry screen (when it is maximized).
Example:
Suppose you enter these fields as follows:
Setting Key: TimeSumStartPercent Setting Value: 35
Setting Key: TimeSumEndPercent Setting Value: 64
Setting Key: TimeSheetStartPercent Setting Value: 65
Setting Key: TimeSheetEndPercent Setting Value: 98
In this case, the actual time entry grid will appear on the top 34% of the screen. The Time or Expense summary will appear in the next section (from 35-64%), and the timesheet entries will comprise the bottom third of the screen (from 65% to 98%).
Setting Key: StandardTrys Setting Value: number
Setting Key: StandardDelays Setting Value: time
These optional fields are used to adjust the timeout settings for this applet. Contact Data-Basics support for details.
Setting Key: InactivityTimeout Setting Value: timems
This optional field is used to specify how long the Remote Timesheet applet will remain open if it is not being used (entered in milleseconds). Setting this field to InactivityTimeOut-36000, for example, would enable the applet to remain open for six hours. Typically, this option is entered to enable users to conveniently enter their hours throughout the day.
Setting Key: WOStatusList Setting Value: status1,status2,....
This option is only applicable it you are using Remote Entry in a non-standard mode, and applying time to Work Orders instead of jobs. This mode also enables the user to reset the appropriate Technician line of the Work Order by selecting from a dropdown list of statuses. This registry option would be implemented to limit the statuses that appear in the drop down list.
Example:
WOStatusList=Cancelled,Completed,Invoice Ready,OnSite,Waiting Service
Setting Key: userlog Setting Value: false or true
This entry tells the applet whether or not to create a log file for each user in the root directory. The true setting is used by support for troubleshooting. If this entry is not included, an error message will display with the user starts the applet.