Validation bypass configuration
This configuration is not based on security groups. Current clock validations are not tied to user identity, so the same bypass setting applies to all swipes processed by that clock configuration.
- Server configuration (
settings.conf) - Reader configuration (RESTful configuration)
Server configuration (settings.conf)
At the server level, each supported validation can be configured with a bypass setting using the following property:
com.infor.wfm.clock.server.validation.[validation name].bypass=false
Replace [validation name] with the validation identifier, for example:
com.infor.wfm.clock.server.validation.BreakLengthValidation.bypass=false
com.infor.wfm.clock.server.validation.SameMinuteValidation.bypass=false
Set the value to true to allow employees to bypass that validation at the clock. Set the value to false to disable bypass so that the validation behaves as before (the swipe is rejected if the validation fails, unless skipped in supervisor mode).
Reader configuration (RESTful)
For RESTful reader configuration, each supported validation can also be configured to allow or disallow bypass using the following property:
validation.[validation name].bypass=N
Replace [validation name] with the specific validation name, for example:
validation.BreakLengthValidation.bypass=N
validation.SwipeOrderValidation.bypass=N
Set the value to Y to allow bypass for that validation. Set the value to N to prevent employees from bypassing that validation.
Validation bypass interacts with other validation settings:
- If bypass is disabled (
bypass=falseorbypass=N), the validation rejects the swipe when the validation fails, and the employee is not presented with a bypass option. - If bypass is enabled and the validation fails, the employee sees the validation bypass confirmation screen and can choose whether to bypass the validation.
- Supervisor‑mode controls, such as “skip in supervisor mode” continue to apply independently of the bypass settings.