Managing Security for User Defined Objects

What are UDOs?

UDOs are personalized web-based objects that can be created by users to improve their JDE experience and reduce the requirement for the developer involvement.  Below are a couple of examples of a custom UDOs.  Whether you need something simple or you need to put several sets of information at your fingertips, E1 UDO functionality can empower you.

Managing Security in UDOs

Managing Security in UDOs

There are various schools of thoughts around who is empowered to do the development of these tools.  In reality, the best practice varies by company and the tool. Some, such as queries, may make sense to make available for more users while other, such as the pages above, may make more sense to centralize development on.  Either way, once you have your UDO created, now you are ready to share it.

UDO Lifecycle (Citizen Developer)

Assuming that the correct authorities exist, a user(s) can develop their own User Defined Objects via the relevant JDE interface – EnterpriseOne contains a design panel (located on the top-right corner of the screen) that provides a coherent way to create and request to publish UDOs.  Below is a graphical representation of the steps involved in the User Defined Object lifecycle:

Managing Security in UDOs

 

UDO Security

Once the UDO is approved for sharing, security still needs to be put into place to enable it for users.  JDE provides security functionality to allow User Defined Objects to be controlled – this security layer (F00950W) sits on top of the standard application security layer (F00950).  The full process including the security functionality involved includes:

Managing Security in UDOs

  • Enabling those UDO features that are available in EnterpriseOne.
  • Determining who can create UDOs for their own personal use and who can modify shared UDOs created by other users.
  • Defining who can request to publish (share) UDOs with other users and who is responsible for approving these UDOs.
  • Identifying who can view/use shared UDOs created by other users.
  • Identifying who can use UDO content in CafeOne UDOs.

It is important to develop a strategy around who is responsible for all levels of UDOs security.  This can be a complicated process, especially with the multiple layers of security and publishing involved.

F00950 Faster Maintenance in a Grid Using ALLOut

As with so many of our tools, ALLOut has identified opportunity to make this process simpler with better visibility to the involved information regarding what is available to the various users and roles.  The enhanced  ‘Security Maintenance’ SuperGrid (PAOS0950) provides easy-to-use functionality to maintain the F00950W table.  The program allows maintenance of all security types (including UDO security) within E1 but with features to speed up your maintenance.

  • Manage UDO Security (Feature/Content/Action/View) from one screen; alongside existing security.
  • Included in the same screen is the ability to Approve UDOs for Publishing – thus giving full visibility over all UDOs, their statuses and originators.
    • Manage UDOs and their access on either fat client or web.
    • A Defaulting Method can be defined to speed up the entry of security records by automatically inheriting predefined values.
    • “1-Click” row exits allow you to create security records in a single click using predefined defaults.
    • Manage multiple records (including copy & paste from spreadsheets) at one time.

To access the SuperGrid from the ‘Security’ tab of the ‘Maintenance’ screen (PAOS0001), click Maintain Security in ‘SuperGrid’’ or FastPath to PAOS0950.

Managing Security in UDOs

The above screenshot shows all available UDO ‘Features’ that have been enabled – select the form exit Feature Security to change the available mode.

For more information on UDOs and how to secure them, email hazel.jackson@alloutsecurity.com for a Tutorial and Product Brief or to find out how to view one of our recorded webinars.