My Oracle Support Banner

Oracle Fusion Absence Management - Release 22A: Deploy seeded Absence Case approval rules using SOA composer Skip to end of metadata (Doc ID 2848862.1)

Last updated on APRIL 05, 2024

Applies to:

Oracle Fusion Absence Management Cloud Service - Version 11.13.22.01.0 and later
Information in this document applies to any platform.

Symptoms

Rule customizations performed by customer for Absence Case approval flows in 21D or prior releases could cause those flows to fail post 22A update.


Symptoms:

  1. The POD has moved from 21D to either 22A or 22B.
  2. Notifications are not sent to approvers when Absence Case is submitted. This should be replicable for all users with administrator access. However, auto approval may be enabled too.
  3. The transaction console should display the following error message for the corresponding transactions.


Changes

 NOTE: The steps provided below will revert all the rule customizations done by customer for Absence Case approval flows. So customer needs to take screenshots of rule configurations for Absence Case approval from BPM worklist, so that the same changes can be done later.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.