In the simplest, out of the box use of UX One, you simply assign the UX One Role to an end user, for example PLANMGRJDE, the Plant Manager which shows Production Schedules, Incidents, and Maintenance Costs.There is a Datapack which contains these roles, relationships, action security, and the UDO Security for the UX One pages. Oracle strongly suggests this is not downloaded directly into an active production environment. If your security covers production and non-production, you shouldn't put this into non-production. 

Continuing the path of using the delivered roles, after adding the role to the user via Role Relationships, the user will see the new UX One Page the next time security cache is cleared (sometimes it appears just with signing out and signing back in). For some graphics you'll see a hamburger menu to choose a different Query for graphing, like in the one shown here. If you click on one of the graph's headers, it will open the base application where the data originated which is where the additional UX One queries exist as well in case there are queries you need to adjust to fit your company's data. Clicking on Watchlists will open the application with those records for your review. 

If you will not be using the Datapack, all the UX One objects will need security setup for them for your existing Role structure. Part IV in this series will show how to use the UX One Cross Reference to identify all the obects for security setup.

Want to see your question answered in the series, or just want to subscribe for alerts on future issues? Simply fill out the form below!