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
Learn about the new Oracle AI Agent Studio for Fusion Applications: Watch Now

Progress with Redwood: Redwood Resources for Oracle Cloud HCM -  Go Here
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.

Unable get original hire date in alert composer template in case if employee is 'Global transfer'?

edited May 22, 2024 5:25AM in Human Capital Management 4 comments

Summary:

Hi,

We have created a custom resource alert to send notification to line manager for upcoming work anniversarries of the employees.
The alert is working fine, but we are facing a issue that- When a person is Global Transferred, the hire date expected to get fetched is alert template should be the original hire date as per earliest inactive assignment. But we are getting hire date as per current active assignment, which is incorrect.

Is it possible to get original hire date in resource alerts? We are using 'Resource' as 'emps'.

In the filter expression, we are using seniority date as per 'Most recent hire rehire date', the employees are getting filtered based on this criteria but in the template the "emps.HireDate" function is fetching the date as per current active assignment, which in providing incorrect hire date in case of Global transfer employees.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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