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.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Customizing effective date of transaction to be "read-only" for specific user roles
Summary:
Experience with defaulting the job start date to read-only in page composer for the effective start date on a transaction.
Content (required):
Hi community, curious if anyone has made the effective start date on a transaction default to current date AND read-only?
The intention of the ask would be to limit the ability to modify the job start date (i.e., the need to back date this date or future date) to specific users, and for others have the value appear as read-only to prevent the need for clarification and avoid confusion for the initiator of the transaction.
Interested in cases where similar use cases had this requirement, as well as any lessons learned.
Tagged:
0