When and Why: Exceptions and Adaptations
Exceptions
This table lists the rules that can't be currently implemented for the When and Why object:
Serial Number |
Rule |
Rule Type |
Actions Impacted |
Sections Impacted |
Fields Impacted |
Comments |
---|---|---|---|---|---|---|
1 |
Object Defaulting, Field Validation, and Field Modification rule types not supported. |
Object Defaulting, Field Validation, and Field Modification. |
All |
When and Why |
All |
You may not for example, default the action reason as soon as the When and Why regions are presented. |
2 |
Warnings on termination on exit section only. |
Field Modification |
Termination |
When and Why |
Action Reason |
Warnings related to termination when you exit the When and Why section are being fixed. |
3 |
Not in Request Position Change, Request New Position, Job and Grade Management flows. |
Object Validation |
Position Change, Request New Position |
When and Why |
All |
The use of this object as part of certain actions aren't yet supported due to either of these reasons:
See the impacted responsive flows to see which actions are supported. |
4 |
Cannot validate proposed hire date in offer |
Object Validation |
Create Offer |
When and Why |
Offer Date |
Action date isn't equal to offer date; support for this is coming in an upcoming release through an entirely different object. |
5 |
Cannot differentiate between launch from Transfer quick action and transfer option of Local and Global Transfer quick action. |
Object Validation |
All |
When and Why |
All |
The action type code fetched either from the action type code of the Action Occurrences object or from hcmParams will indicate transfer. This happens if either the action is launched from the Transfer quick action or from the Local and Global Transfer quick action and there is no change in legislation code. Oracle is reviewing this for a possible fix. |
6 |
Cannot differentiate between Me, My Team, and My Client Groups (or any other Home screen tabs) when same action is launched from different tabs. |
Object Validation |
All |
When and Why |
All |
You can use the logged in user role as proxy, but there will be no way of differentiating between say, an HR specialist performing a given action on another person or themselves. Oracle is reviewing this for a possible solution. |
Adaptations
There are no adaptations currently available for the When and Why business object.