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.

Redwood Timecard - Default date for adding timecard

Summary:

When adding a Redwood timecard, can we default the date to the next period for which a timecard does not exist for the employee?

Content (please ensure you mask any confidential information):

With the responsive timecards, when adding a timecard, the date defaulted to the next period for which a timecard would need to be added (based on timecards that have already been added for the employee). With Redwood, it is always defaulting to the current date, even if a timecard already exists for that period. Is there a way to change the default date to the next period for which a timecard does not exist for the employee (the way responsive timecards worked)?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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