JDE is one of the most loved ERP system in the market place with an incredibly passionate user base. First, you'll learn the two most common form types, the Find Browse and the Fix Inspect forms. Next, you'll discover the programming language of E1 called Event Rules. Then, you'll explore runtime structures and event processing. Finally, you'll discover probably the most important part of being an E1 developer... debugging and logging. By the end of this course, you'll understand the basics of developing E1 interactive applications.
Course Overview Hi everyone. My name is Shaun Meyer, and welcome to my course on Interactive Applications for Oracle's JD Edwards EnterpriseOne ERP System. I'm a solutions architect and I've been developing on and extending JD Edwards for almost 18 years now. JDE is one of the most-loved ERP systems in the marketplace, with an incredibly passionate user base. In this course, we're going to explore development of interactive applications and no prior E1 development experience is required. Some of the major topics that we'll cover include the two most common form types, the Find/Browse and the Fix/Inspect reports, the programming language of E1, called Event Rules, runtime structures and event processing, and probably the most important part of being an E1 developer, debugging and logging. By the end of this course, you will understand the basics of developing E1 interactive applications, and you'll be ready to develop applications of your very own. Before beginning this course, you should have some fundamental knowledge of JD Edwards EnterpriseOne, and some very basic programming skills. I hope that you join me on this journey to learn how to develop interactive applications with the JD Edwards EnterpriseOne Interactive Applications course at Pluralsight.
The Forms Design Aid Welcome back to this course, on JD Edwards EnterpriseOne interactive applications. My name is Shaun Meyer, and in this module, we'll be focusing on the case tool, used to create and maintain interactive applications. It's rather unimaginatively called Forms Design Aid, or just FDA. In this module, we will create, the custom, acme Address Book Master Application, P550001 object, in the Object Management Workbench. Then we'll open the application in design mode, using the FDA. Then we'll explore the various menu items, toolbars, windows, and all the features that the Forms Design Aid application provides. So let's jump right in and create that Application object in OMW.
The Find/Browse Form Welcome back to this course on interactive applications for the JD Edwards ERP System. In this module, we will focus on the workhorse of interactive applications, which is the Find Browse Form. This is probably the most common form type. But what is a Find/Browse and why would we want to use it? A Find/Browse is the entry point of the vast majority of E1 applications. It's used to search for records in the database and then we'll do something with it possibly in another form, like a Fix/Spec. It allows users to add, change and delete records, and it contains a read-only grid. This isn't the place where we actually enter the address book information. This is just an entry point and the place that we search for existing address book records. That's exactly what we want for the ACME address book application, right? When the application starts, we can present the Find/Browse form to the user. Then they can either add a new address book record, which will be done in the Fix/Spec form, or they can search for an existing record and then update it, copy it, or delete it. In this module, we will create and build out the Find/Browse form. We will attach a business view to the form. We will add columns to the grid and to the form. The form controls will be made into filter fields, which will help us search for records. And we'll attach the processing option to the application. So next step will be creating and building out the Find/Browse form.
Adding Logic Welcome back to this course on interactive applications for the JD Edwards EnterpriseOne ERP system. In this module, we will talk about the programming language of E1, which is called event rules, or just ER. And I'm doing little air quotes here. I guess it's not really a programming language, but it is how you add the business logic. As I mentioned in the course introduction, I'm going to assume that you already have some basic programming experience. I'm not going to explain to you what a variable or what a while loop is. But what I am going to do is explain how to implement those features using the E1 case tool set. In this module, we will talk about events and event rules. Then we will talk about runtime structures. These are some of the nicest features of programming in E1. Then we will talk about how events are processed by the middleware, and I'll show you a sneaky way to figure out the sequence that events are called in. And that can be very handy while you're a beginner. Then we'll actually add some event rules. We call a few system and business functions. Then we'll very quickly look at BrowsER, which I don't find very useful. There's some freeware tools which are way more interesting, and we'll cover those in the module on debugging. So let's get started. Next up, we'll talk about what an event and what an event rule actually are.
Creating the Fix/Inspect Form Welcome back. In this module, we will continue to build up the custom address book master application, P550001, for our fictitious enterprise, Acme Corporation. We've already created the find/browse form, which means we have an entry point to our application, and we can search for existing records. But what we can't yet do is create new records or edit existing ones, and it's this functionality we will be adding to our application by creating a fix/inspect form. In this module, we will create a fix/inspect form, we will attach our business view, we will add business view form controls, we'll add logic to ensure that the audit information is correct, and then we will call the fix/inspect form from our find/browse form, and add change, copy and delete mode. So, without any further ado, let's create that fix/inspect form.
Debugging Welcome back to this course on interactive applications for the JD Edwards EnterpriseOne ERP system. This is a super important module probably the most important module of this entire course. We're going to talk about debugging. And, as a developer, well this is where you're going to be spending most of your time. E One has some great baked-in tools for logging and debugging. And there also some excellent, free, third party tools which I will also introduce. In this module we will talk about the Debugger, the go-to application for all of your debugging needs. It's not an overly complicated application, but it has everything that you need to squash those stubborn, hard to remove bugs. Another very important topic is logging. Because sometimes you won't be able to use the debugger to track down a bug. Sometimes the only help you're going to get is a log file. But luckily, there are some great free tools to help sift through those sometimes enormous log files. And then the object browser, which is another free third party tool, that makes development in E One that much easier. One thing that we won't be covering in this module is debugging business functions in C. We'll have to save that for another in-depth course. So let's open up the debugger and see what it can do.