Log on was allowed when there is no quantity reported on previous routing position. Respondida
Hi,
Wondering if there's any settings that override this, the option is enabled on the configuration but the time receipt pushed through even when there is no quantity reported on the previous route:
Comentarios
7 comentarios
Prev. Routing position is the first Routing Position with active flag "Clock Mandatory"
if this flag is not active, the system ignore this routing position in all rules
The previous routing position has the "Clock Mandatory" checked:
But position 30 is parallel (not Clock mandatory). Correct?
Position 30:
hmm
the system display that the routing posistions parallel or overlapped.
in both variants the system can't check the previous quantity - special if you work with parallel.
Parallel means: You can start with both in parallel.
That's what I thought initially, but users insist it's not behaving like this before. We'll try running this on a test DB. I'll post an update soon. Thank you!
Sorry for the late update, overlap limit on the route is indeed the cause. Tested and validated this on a test database. Thank you!
Iniciar sesión para dejar un comentario.