This page (revision-29) was last changed on 26-Nov-2021 10:22 by jmyers

This page was created on 26-Nov-2021 10:22 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
29 26-Nov-2021 10:22 4 KB jmyers to previous 1ST_DAY_OF_WEEK ==> 1ST_DAY_OF_WEEK(System_Preference)
28 26-Nov-2021 10:22 4 KB JMyers to previous | to last
27 26-Nov-2021 10:22 4 KB JMyers to previous | to last
26 26-Nov-2021 10:22 4 KB Bill Hughes to previous | to last
25 26-Nov-2021 10:22 4 KB Bill Hughes to previous | to last
24 26-Nov-2021 10:22 4 KB Bill Hughes to previous | to last
23 26-Nov-2021 10:22 4 KB Bill Hughes to previous | to last
22 26-Nov-2021 10:22 4 KB JMyers to previous | to last
21 26-Nov-2021 10:22 4 KB JMyers to previous | to last

Page References

Incoming links Outgoing links
DTDP
DTDP

Version management

Difference between version and

At line 5 changed 2 lines
This function gives managers the ability to see who punched IN/OUT (clock entries) and from what clock device [ITCD] - (''Define Clock Devices'') they came from.\\ \\
Most time clock implementations will have more than one clock device (time clock or punch clock); this calendar based screen allows managers to select a clock device and see clock entries by day and by employee. It also provides information a manager might want to see such as costing or shift information.
This function gives managers the ability to see who punched IN/OUT (clock entries) and from what clock device [ITCD] - (''Define Clock Devices'') they came from. \\\Most time clock implementations will have more than one clock device (time clock or punch clock); this calendar based screen allows managers to select a clock device and see clock entries by day and by employee. It also provides information a manager might want to see such as costing or shift information.
At line 8 removed 2 lines
The definition data for the Daily Device Clock Punches screen is stored in the [P2K_TS_CLOCK_DEVICES] and [P2K_TS_CLOCK_ENTRIES] tables.
At line 11 changed one line
Dynamic Calendars are used in the [DTSH] form to allow companies to specify the start of the work week. \\ In the [Preference tab of IMST|IMST#PreferencesTab], clients must add [1ST_DAY_OF_WEEK(System_Preference)] preference with a value of 1 through 7 where 1 represents Sunday and 7 represents Saturday.\\ \\The clock entry information below the calendar is derived based on the date in focus on the calendar.
Dynamic Calendars are used in the [DTSH] form to allow companies to specify the start of the work week. \\ \\In the [Preference tab of IMST|IMST#PreferencesTab], clients must add [1ST_DAY_OF_WEEK] preference with a value of 1 thru 7 where 1 represents Sunday and 7 represents Saturday. \\ \\The clock entry information below the calendar is derived based on the date in focus on the calendar.
At line 10 added one line
!!DTDP Fields
At line 14 removed one line
At line 19 changed one line
The following clock entry details can be seen by day based on the date in focus on the calendar above:
The following clock entry details can be seen by day based on the date in focus on the calendar:
At line 27 changed one line
;[Type|CLOCK_ENTRY_TYPE]:This field identifies the type of clock entry being made. e.g. In, Out, Break, Lunch or Undetermined.
;[Type|CLOCK_ENTRY_TYPE]:This field identifies the type of clock entry being made, e.g. In, Out, Break, Lunch or Undetermined.
At line 37 changed 2 lines
;[Reference Information|REFERENCE_INFORMATION]:This field will allow the user to include any additional information about the time entry. This field may be used to indicate the clock device if the G1 or G2 interface is used. Each time clock would be given a machine name that corresponds to a clock device ([ITCD]) in Personality. This code would be stored in the reference information for each clock entry.
%%information The following areas are view only%%
;[Reference Information|REFERENCE_INFORMATION]:This field will allow the user to include any additional information about the time entry. This field may be used to indicate the clock device if the G1 or G2 interface is used. Each time clock would be given a Machine Name that corresponds to a clock device ([ITCD]) in [{$applicationname}]. This code would be stored in the reference information for each clock entry.
At line 47 added 2 lines
----
;[Clock Entry Status|CLOCK_ENTRY_STATUS]:This field displays the status of the card entry, e.g. Newly Entered or Processed.
At line 51 changed 2 lines
!Clocking Details
;[Clock Entry Status|CLOCK_ENTRY_STATUS]:This field displays the status of the card entry. e.g. Newly Entered or Processed.
;[Time Exception Status|TIME_EXCEPTION_STATUS]:This field displays the status of the time exception, e.g. Newly Entered or Processed.
At line 54 removed 2 lines
;[Time Exception Status|TIME_EXCEPTION_STATUS]:This field displays the status of the time exception. e.g. Newly Entered or Processed.
At line 56 added 2 lines
!!DTDP Tables
The definition data for the Daily Device Clock Punches screen is stored in the [P2K_TS_CLOCK_DEVICES] and [P2K_TS_CLOCK_ENTRIES] tables.
At line 59 added one line
[{If var='loginstatus' contains 'authenticated'
At line 61 added 2 lines
![Discussion|Edit:Internal.DTDP]
[{InsertPage page='Internal.DTDP' default='Click to create a new discussion page'}]
At line 63 changed 2 lines
![Notes|Edit:Internal.DTDP]
[{InsertPage page='Internal.DTDP' default='Click to create a new notes page'}]
}]
This page (revision-29) was last changed on 26-Nov-2021 10:22 by jmyersTop