All JD Edwards organization need to keep their software components updated to avoid obsolescence and most importantly, to keep the system secure against known security vulnerabilities and glitches. Two components that often are not kept updated are the Java JDK (Java Development Kit) and JRE (Java Runtime Environment).

Presented at BLUEPRINT 4D
Session ID: 100920

JP Cycles recently implemented a very successful warehouse robot solution using orchestrator. Being the CNC, my inner geek was super excited - ROBOTS!!! It was short-lived, because then the meetings started. Robots have their own language? And their own data? Volume is going to increase by how much? What if there’s a network glitch? What if there are errors? What do you mean errors aren’t saved? What if the data gets out of sync? How is it re-synced? How is it verified? Join me to hear how robots upended my simple existence and how orchestrator helped us create a semi-autonomous solution for error handling.

The foundation of efficiency is automation. Nearly every advancement in technology can be somehow tied to the quest for higher levels of automation. The JD Edwards Digital Platform, anchored by Orchestrator, has its fair share of automation tools and techniques. Customers and partners have done amazing things using these tools to automate business processes. But now it's time to think about upping the stakes from process automation to enterprise automation. What would it look like if every aspect of your business operations had some level of automation? What would that mean for efficiency? Accuracy? Timeliness? But perhaps more important than the efficiency itself, what kind and what volume of data would be generated? What insights and observations could you glean from such a mountain of data - data that reflects every heartbeat of your operations? Learn more about this future - it's not far off.

Getting Started with the REST API. Learn what your Custom Dev team expects for integrations. Whether it's validating E1 data or you deliver an immaculate Orchestration, knowing how to communicate to a dev that has no experience with E1 can be a challenge. This session is meant to help you bridge the gap, giving you the tools (API Testing Software PostMan) to help test your requests before you give them over to the custom dev team.

Learn how Yamana Gold leveraged the use of Swift's - low code / no code app automation platform and Orchestrator to create their Mobile PO Approval application in a matter of days, helping them achieve:

Join this session to understand how migrating to 64-bit JD Edwards EnterpriseOne 9.2 can future-proof your business. Understand the technical details related to moving to 64-bit JD Edwards, best practices and considerations.

Session ID: 101320With 20+ years of Developer Experience, I'd like to share a few new things I've learned recently. I'll try to amaze with tricks, traps, and wonders that may not have been presented before.

Join City of Plano and ACBM Solutions as we take you on a deep dive through a complete Construction Management integration between JDE and Aurigo Masterworks using Orchestrator. We will start by discussing the business case and why this project was needed.

Then we will explore the Orchestrations that were built to make the integration work across the following areas:

• Vendors
• Purchase Orders
• Project Budgets
• Expenses
• Payments

After attending sessions and taking some training I realized that creating orchestrations is easy but I still kept stumbling with what do I actually do with the orchestration once I create it.

I know that you can use the form extension to create a button on a form to call an orchestration but if you want to pass in data and the data you need is not on the form, then what do you do? I have also had people talk about writing external scripts or web pages and using the orchestrations from there. That is all great, but I am not a full-fledged programmer so how can I use what I have and know in JDE to make my orchestrations work for me? It has been a long road, and I have learned a lot about the next steps to take to actually get an orchestration to work within JDE and I wanted to share my experience.