Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

Webclock Punch in and Punch out unable to be captured correctly for Midnight Scenarios

Summary:

Hi Experts,

We are facing an issue to get ideal Punch in and punch out for Midnight spanning cases.

For ex: Employee works in Shift like 10pm to 6am; Login at 10pm > Punch in at 10pm > Clock keeps running > Need to punch out at next day morning 6am.

We are facing issue for this scenario of 6am. When employee comes back to punch out in the morning at 6am, there are both Punch in and Punch out available. The previous Punch-in of 10pm is not visible anymore.

Has anyone faced this? How do we manage this situation which is very common for all the organizations?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!