User Security Hierarchy Suggestions

[JefferyD]

Currently we have a user security structure like:

Code: Select all

(User Authorization) ==> (Role) ==> (Object List) ==> (Object)

Each level has a dedicated UI page, limiting the view to only a single parent and it's children. This means that in order to know what objects a role has access to, each object list would have to be checked one by one.

Suggestion #1
When viewing the children of a parent, add a feature that will allow expanding any child that is a collection increasing the view from a 1 generation to 2.

For example, when viewing the roles of an authorization type, let the roles be expanded to show what object lists each role has access to. This would make it much easier to follow the overall access a user may have without having several different tabs or windows open.

• User Authorization
  • Role
    • Object List
    • Object List
    • Object List
  • Role
    • Object List
    • Object List
    • Object List

Suggestion #2
Separate from the previous suggestion, I'd also like to suggest a hierarchy tree generation feature. Given an entity, I'd like some way to generate a read-only report of everything under that entity.

An example of a user authorization hierarchy is below, but I could also see it working with webpages, widgets, methods, submethods, loop methods, batch jobs, and APIs (maybe excluding controls and services as they can get complicated with sibling relationships on top of parent/child ones).

• User Authorization
  • Role
    • Object List
      • Object
      • Object
      • Object
    • Object List
      • Object
      • Object
      • Object
    • Object List
      • Object
      • Object
      • Object
  • Role
    • Object List
      • Object
      • Object
      • Object
    • Object List
      • Object
      • Object
      • Object
    • Object List
      • Object
      • Object
      • Object

[SumanPrasad]

Jeff,
Task 10727 is created to enhance UI for roles and objects.
Thanks,
Suman

[JustinVanRegenmorter]

This feature has been implemented as of the current version of EASYProcess.