Data Validation and Error Handling in Orchestrator
-
Posted by Quest Customer Learning Team
- Last updated 11/18/21
- Share
Presented at INFOCUS Dive Deep 2021
Have you already built amazing Orchestrations that work perfectly with great data, but blow up when the data is not entered as expected? We are not talking about invalid UDC codes or something that is already validated by JDE. Instead, we want to explore how to proactively identify and remediate issues according to business rules such as verifying that the input vendor is equal to the primary vendor associated with that particular Item Branch record.
In this session we are not only going to look at how to add custom Error Handling to send notifications and undo previous parts of an Orchestration, but also how to proactively validate data before anything is processed in JDE.
Watch the full-length video
You’ve reached the ultimate Oracle customer network—exclusively for Quest Corporate and Professional members.
Join Quest to unlock access to strategic content centers, event replays, exclusive programming, and expert insights—all designed to help Oracle users like you go further, faster.
Whether you're on JD Edwards, PeopleSoft, or Oracle Cloud, Quest connects you with a powerful peer network and Oracle experts so you can make smarter decisions, drive innovation, and get more from your investment.
Quest is where Oracle customers connect, learn, and lead with confidence. Ready to join them?
