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.
Are the purge/archive fields in journey configuration no longer mandatory?
Summary:
My client is on 23A, and we have advised them on timelines to archive and purge their journeys across all workstreams as best practice. Yesterday they reached out asking why these fields are no longer required. I have not seen documentation to support this, but when I log into the client demo pod I can see that when editing an existing journey both the purge and archive configuration fields are no longer required. They ARE mandatory fields if I am creating a new journey. I understand that the fields were not required for journeys created prior to 22A, however I
Tagged:
0