Configuring the Consecutive Types validation
With the Consecutive Types validation you can prevent similar swipes to be performed
within a certain period and based on one or more conditions.
The validation can use these conditions:
Setting | Description |
---|---|
length |
The amount of time (in minutes) for which two swipes of the same
type is not allowed one after the other (0 - to not allow swipes of the same type at
all). For example, you could set this value to 5 minutes for the minimum length. With this configuration, if you clock in you cannot clock in again within 5 minutes. The clock in punch is rejected. For example:
|
type
|
Defines which swipe types trigger the validation. The condition
can take a comma separated list of swipe types. For example: com.infor.wfm.clock.server.validation.ConsecutiveTypesValidation.type =
01,02,06 For more information on the various swipe types, see Supported Swipe Types. |
swipeCompare
|
Defines which attribute of the clock punches are compared to
determine if the punches are duplicates. This condition accepts the these values:
For example, you can specify these comma-separated values:
|
An example implementation of this validation in the settings.conf configuration file is as follows. This example prevents the
employee from a duplicate clock in punch, clock out punch, or time code punch within 5
minutes:
com.infor.wfm.clock.server.validation.ConsecutiveTypesValidation.length = 5
# .swipeCompare specifies swipe properties to compare
com.infor.wfm.clock.server.validation.ConsecutiveTypesValidation.swipeCompare = TYPE, TCode
com.infor.wfm.clock.server.validation.ConsecutiveTypesValidation.type = 01,02,06