A session at INFOCUS 18 covered tips for how to get the most out of your UX One implementation. Sharon Winter, Senior Principal Product Manager at Oracle, discussed the technical requirements and important information needed to utilize UX One.

What we learned:

Three Buckets

There are three buckets that someone might fall into when thinking about implementing UX One. Whether you are migrating from World, upgrading to Release 9.2 or are already on 9.2, there is an approach designed for you to implement UX One. To learn the steps and how UX One can benefit your organization, check out the full presentation below.

Technical Requirements

In order to implement UX One in your organization, you will need:

• Release 9.2 with the latest updates
• Tools 9.2.1 or higher
• AIS Server for analytic components, Notifications with Orchestrator or Modernized User Interfaces (ADF Apps)
• ADF Server on WebLogic for Orchestrator Studio or Modernized User Interfaces (ADF Apps)

User Defined Objects (UDOs)

UX One is based on UDOs, which help users create personalized content within without creating a large number of customizations. This means it’s important for you to stay in control of UDOs with Security Workbench. Within Security Workbench, you can manage the Feature Security, UDO Action Security, Content Security, View Security, Data Browser Security and Application Security.

What You Need to Know

Here are some key points that the Information Technology team should know when implementing and working with UX One:

• The supported versions of servers and performance information
• UDO Security and UDO Management
• Subject matter expertise of how to build and modify each type of UDO, so you can support the citizen developers

Here is some additional information that will be useful for Business Analysts when using and managing UX One:

• How to build and modify each type of UDO
• How to share UDOs and grant View Security to roles or users
• How to work with the Orchestrator Studio if you want to build Notifications