Denovo recently had a UX One implementation (in Release 23), and there was an issue with spinning "Loading" icons. In an attempt to troubleshoot, the CNC added View security to all the "E1PAGE" objects associated with the UX One page having this issue. This introduced a new problem - every E1PAGE object became its own Page. This is a known and documented bit of setup to not do. Yes, you need View security on the Watchlists, Queries, applications that are called by clicking on graphics, etc., but you do not need View security on the dependent E1PAGE objects. 

If you haven’t yet taken advantage of UX One objects or pages, let us give you a personal demo to show you how they work and how they can increase productivity and end user satisfaction.

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!