JD Edwards EnterpriseOne UX One aims to transform user experience, enabling existing users and attracting new ones with enhanced, role-based content based on the “Alert, Analyze and Act” paradigm. Oracle’s Julie O’ Shea and Ania Gutierrez validate customer concerns by speaking to them from the standpoint of fellow users. By doing so, they offered several helpful tips and tricks to enable easier use of the products offered in UX One.

If you’re interested in experiencing the efficient task management of UX One, you’ll need to have a few of the prerequisites installed and ready to go. So how do you get UX One up and running on your system? First you’ll need to make sure you’ve lined up the necessary software.

Prerequisites to run JD Edwards EnterpriseOne UX One include:

• A minimum of JD Edwards EnterpriseOne Application Release 9.2
• JD Edwards EnterpriseOne Tools Release 9.2 Update
• Basic knowledge of which roles you want to use and what additional content you want to create
• All electronic software updates, user defined objects and application development framework components from UX One and all query in Change Assistant

There have been three updates to the software since the UX One launch, namely the mandatory base version that was launched in November of 2016, the JD Edwards EnterpriseOne 2017 Update 1 in February of 2017 and the Update 2 from April of 2017. Some optional data packs include security and roles and demo data.

Julie continues the presentation by outlining a brief demo of best practices users should follow during implementation, including the following:

• Use the cross-reference My Oracle Support (MOS) document for guidance regarding which pages, watchlists, etc. are included in each role
• Install the security and roles datapack from Update 2
• Import the user defined object (UDO) demo
• Share the All Roles demo
• Use your own security layer and share all roles not needed
• If you want to modify any object, you must copy that object. Otherwise, when you take a new object update or a patch, that object will be overwritten.
• You will need an application interface server to operate UX One
• Whatever you do, don’t assign over 30 roles per user. The system will become unstable if all 30 roles are active at the same time.

The presentation continues with brief demos of a few JD Edwards EnterpriseOne UX One capabilities, including Change Assistant and Task Index Builds. The speakers also demonstrated checks and balances within the install process and best practices in staying code current. Throughout the webinar, O’Shea and Gutierrez give clear visual examples of what to expect with each UX One.

Every tool they present encourages customization, and as Gutierrez reminds us, “You’re more than welcome to create your own [model] based on ours. Just know that what we’re delivering works.”

To see these detailed demos in action, jump over to their JD Edwards EnterpriseOne UX One troubleshooting and installation presentation.