Adding validation conditions
You can add conditions to each validation which define additional characteristics, such as whether the server skips the validation if a supervisor performed the clock punch.
Since clock validations are an important aspect of the WBCS
configuration, most validations have default configurations. The defaults are
automatically applied to the appropriate clock punches, and the
skipwhensupervisor
parameter is set to
True
to allow supervisors to override the validation.
When you specify conditions in the settings.conf file, you override the default conditions, which have been configured so that the WBCS functions properly. Although you can specify conditions for any validation, Infor recommends that you only override the default conditions when necessary.
Validation conditions are in the form com.infor.wfm.clock.server.validation.ValidationType.condition = value
,
where ValidationType
is the specific validation name
and condition is one of these:
Setting | Description |
---|---|
update.employee
|
This condition activates the clock server framework to update the employee's last status and last swipe. Set to True to update the employee's last status and last swipe. Set to False to leave the employee's last swipe and last status unchanged. Example:
This tells the clock server framework to leave the employee's last swipe
and last status unchanged if the swipe is validated by the
|
skipwhensupervisor
|
When set to True, the validation is skipped if the punch was performed by a supervisor. This setting allows supervisors to override validations when they perform punches on behalf of their employees. By default, validations are configured with this condition set to True. Set this condition to False to prevent supervisors from overriding the validation. |
tcode
|
Defines which time codes trigger the validation. For
example, with the
BreakLengthValidation , this condition defines
the time codes that are considered breaks. The condition can take a comma
separated list of time codes.
|
type
|
Defines which swipe types trigger the validation. The condition can take a comma separated list of swipe types. |
needsupervisor
|
When set to True, the clock prompts the user for a supervisor badge if the validation fails. This condition only works with clocks that can drive the supervisor prompt, such as Synel clocks. |
onlyonline = true
|
When set to True, the validation is skipped when an offline swipe (a clock punch performed when the clock is not connected to the WBCS) is received. By default, validations are configured with this condition set to False so that both online and offline swipes are validated. |
-
Open the
settings.conf
file with a text editor. The file is located in the \conf subdirectory of the WBCS installation file. -
Locate the section of the file with the existing validation
conditions, if any. Validation conditions are supplied in the form:
com.infor.wfm.clock.server.validation.ValidationType.condition = value
. -
Specify the new validation condition on a new line. For example, to
define the minimum break length as 30 minutes, type
com.infor.wfm.clock.server.validation.BreakLengthValidation.length = 30
. - Save the file and exit the text editor.