Let's Reconnect, thank you for making 2022 our best year yet.

Look Back
Areas of Responsibility Behavior — Cloud Customer Connect
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

Areas of Responsibility Behavior



Approval went to an inactive approver.

Content (required):

Can you confirm the behavior is expected?

  • A request for Transfer was sent on 7 Nov with effective date of change is 24 Jul and the request for approval was sent to Approver A.
  • Approver A, at the effective date of change, is already terminated on 06 Sep but AoR is still assigned and valid until 31/12/4712
  • The current approver (Approver B) with the AoR that is effective from 26 Aug onwards

Issue: the Approval was sent to previous approver (Approver A) even is she is already terminated instead of the current approver (Approver B). We expect the request for approval to always go to the active and current approver (Approver B) even if the date of effectivity is in past since the previous approver (Approver A) is no longer active in the system and cannot approve it.

Howdy, Stranger!

Log In

To view full details, sign in.


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