How does mandatory task expiry field affect Archive and Purge Journey Data ESS?
With 23B - task expiry field is now mandatory
ESS used to disregard the expiry fields on tasks
With 23B update, the task expiry field will be mandatory. How will this affect the Archive and Purge Journey Data ESS that Oracle has scheduled to run through the system?
Previous understanding of the Archive and Purge Journey Data ESS asserted that the process only considered completed allocated journeys and did not consider anything at the task-level. In other words, you can have a completed journey that will be archived/purged, but individual tasks could still be open on that journey.