Get Started with Redwood for Oracle Cloud HCM Begin Now
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.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
HR Helpdesk Request Migration from legacy application
Summary:
Questions & best practice around HR Helpdesk Request Migration from legacy application
Content (required):
Hi Team
We have got a requirement to migrate In progress active HR helpdesk requests from legacy application to HR helpdesk.
We will be continue using same mailbox in HR helpdesk i.e. during cutover window, we will switch the mailbox from legacy application to HR helpdesk. I am looking for inputs and best practice around data migration to avoid duplicate tickets being created.
- How did you approach the data migration during cutover phase?
- Once we switch the mailbox to HR helpdesk application, if employee tries to respond to older ticket from their email, new tickets will be created (as message ID, SR ID reference will not be there). How can we mitigate this?
0