Restricting Employee-Initiated Absence Entry for Specific Absence Type in Redwood UI

Hi

We are currently using the Redwood UI for Absence Entry in Oracle Fusion HCM Cloud, and we have a specific business requirement for which we are seeking guidance or confirmation of the recommended approach.

Our requirement is to prevent employees from initiating a new absence for one particular Absence Type in Redwood UI, while still allowing employees to self-initiate other Absence Types without restrictions.

At the same time, an integration loopback process creates absences of this restricted type in Saved status. Employees must be able to open, edit, and submit these Saved absences that were created via Loopback integration.