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.

Performance Issue for Autocomplete DoR

Summary:

We have an approved usecase #80 for Document Records BO.

Once a DFF has been updated from Null/Empty to a value, it cannot be changed any longer. For e.g. If updated from value but not equaling empty or null, to any other value but also not equaling empty or null, then show error.

Currently it is only being applied to one Document Type. The question is if we can apply this to all DoR? Will there be an issue in terms of its performance or should we include always a filter for the specific Document type?

Customer Name: Deutsche Bahn AG

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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