If you've been following Oracle's OBE's, attending conferences, and using Oracle's LearnJDE content to follow Logic Extensions, you have seen some use cases. If you've followed Ask Denovo's Logic Extension Series over the last few weeks, you have one more building block of knowledge for building and using Logic Extensions!
One key takeaway unique to this use case was not using a JDE Data Structure, whether out of the box or a custom one, but instead simply adding variables. Part III also pointed out the ability to trigger Logic Extensions via a field, action (Find, OK, Cancel, etc.) or grid column action, not necessarily always attaching to a Form Extension Button. Release 25 now allows Logic Extensions to be triggered from a Row or Form exit!
As promised, here are a couple real Logic Extensions being used:
- Government agency didn't like having to make duplicate entries into both Employee Auto Deposit and the Supplier Bank Account apps. Logic Extension was created to update the Supplier Bank Account with Employee Auto Deposit information.
- Distribution company had frustrated users who were entering the same information in the same fields in Standard Voucher Entry and Job Master creation. Logic Extensions and Orchestrations both used to default hard-coded values into Company, default some date fields, and enter values into the Job based on user data.
If you continue to have interest in Logic Extensions, now is the time to contact Denovo! We can help you find those opportunities to build Logic Extensions, train you on how to create and support them, and be well on your way to optimum process improvements!