JDE Security – E1 Pages, Composed Pages and the JDE User Interface
Kyle Gray, Solution Consultant – Security and Fraud
Working with an ERP system can be a very cumbersome experience, especially in the beginning. You are learning a new, robust software that controls the company’s day to day functions and/or lines of business. Emphasis on accurate and efficient work is needed and often demanded. Traditionally, the menu path or FastPath were used to navigate and access objects. Depending on the menu setup, users may be required to click multiple times (I’ve seen up to 9) to access just one object. Depending on system performance, navigating to the object could take several minutes. System admins began looking for ways to ease the end users’ experiences and make navigation/access a smoother process.
Users first chance for quicker access points were created by utilizing Favorites. Favorites grant access to a program/report, in JDE, that the user has security access to and are created from the menu path. This simply allows the user to have a one-click option, in the left Favorites panel, instead of navigating through the menu path each time to access an object. Favorites are also tied to the user ID, not the role. Meaning, roles and access can change for a user. However, the issue JDE Security Administrators were finding with Favorites is a user can access the program/report tied to that Favorite, even if the security access has been changed for that user. Meaning, they could be accessing an object (or version of an object) they shouldn’t.
UDOs and the User Interface:
With the creation and now advancement of User Defined Objects (UDOs) in JDE, navigating and accessing the objects has become much easier for the end user. Users are now able to create their own UDOs in the system. Grid Formats being the most popular and universally used. This UDO type allows users to create personal (or shared) grid formats in JDE. Meaning, they can narrow down the data displayed in a grid to only show what is pertinent to the user. These UDOs can be kept for personal use or shared with the rest of your JDE user base. The new, popularity growing, UDOs that are changing the way access is granted and navigated are Classic EnterpriseOne Pages (E1 Pages) and Composed EnterpriseOne Pages. These UDO types are the first screen that appears when logging into JDE. E1 or Composed Pages are setup for specific access needs, usually related to a role or business process (i.e. Payroll Processing, Voucher Entry, etc.)
Planning is key:
Having a plan around creating, securing and assigning UDOs, especially E1 and Composed Pages, is crucial in the success of managing them. Regardless of the nature of the request/need, a plan should be put into place or an existing one adhered to. Creation and lifecycle of UDOs are best (should be) treated as mini projects to ensure the company has a firm grip on the management of UDOs.
Classic E1 Pages:
Classic E1 Pages enable users to work on multiple EnterpriseOne application. E1 Pages are HTML files and can contact HTML-enabled functionality, such as interactive process flows, URL links and web pages, company logos. As you can see in the screenshot, E1 Pages are displayed on the initial log in screen, in a tabular format, with little to no navigating necessary. Classic pages are created outside of JDE, using a Page Composer, then the zipped dat.file is uploaded to JDE and the page is created.
Composed E1 Pages:
EnterpriseOne page with user defined layouts that enables users to access Designer Panes, Watchlist Panes, Classic Pages, EnterpriseOne applications, One View Reports, web pages, OBIEE objects, and ADF applications. Composed pages are created using the JDE Manage Content feature. Composed pages can be tied to a Task ID or the object ID.
Securing and Assigning E1 and Composed Pages:
E1 and Composed have changed the way users navigate and access objects in the system. Pages can be created for a specific user, role or *PUBLIC (all users). Typically, pages tie back to a user, role or business process flow. Once you have decided on how you would like to create your pages and to whom you would like to distribute these pages to for use, you must secure and assign them. Securing your UDO is done through the Security Workbench (P00950). By clicking the Form exit, you have the option to assign Content, Action and/or View security.
- Content Security – Enabling the content for a specific UDO type.
- Action Security – Which user(s) in the system can work with (Create, Modify, Publish) each UDO type.
- View Security – Which user(s) in the system can view a particular UDO
If UDOs are on your future (or current) radar and you would like some assistance in planning, creating, securing and assigning and maintaining your UDOs, please do not hesitate to reach out to the GSI Security Team. We will be more than happy to assist in pre-planning discussions, the enabling/securing/assigning of UDOs or even take over the creation and structure of UDOs in your system.
Meet the Author