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.

Fields that can be used when creating a time based condition in Onboarding

Summary:

Fields that can be used when creating a time based condition in Onboarding

Content (required):

As per Oracle Doc 1616371.1, there are only four standard fields that can be used when creating a Time Based Condition and user-defined fields cannot be used to trigger date-based conditions.

We implemented the Onboarding process since 2016 and eSignature Dates were being used since then to trigger date-based conditions. Recently, we found some processes that should have been triggered around December 2020 and January 2021 were failed. There is nothing else incorrect after that time.

I'd like to check:

  1. What fields are you using to trigger the date-based conditions.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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