Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-2654

Improve vocabularies and users management screens

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 5.2 M2, 5.2 RC1
    • Fix Version/s: 5.3 RC
    • Component/s: None
    • Tags:
    • Impact type:
      API change, API added
    • Upgrade notes:
      Hide

      For 5.2.0:

      Added API:

      • on directory Session and DirectoryManager: hasEntry(String) and createEntry(DocumentModel)
      • on Layout: getWidget(String) and getWidgetMap() to ease cross validation (cf password verification with double check)
      • on UserManager: a bunch of create/update/delete/search methods for users and groups using DocumentModel instead of NuxeoPrincipal and NuxeoGroup

      Changed API:

      • document model retrieved from NuxeoPrincipal as now type "user" instead of "User"
      • UserManagerActions and GroupManagerActions and SecurityAction have been refactored

      users and groups screen now entirely rely on the "user" and "group" layouts.
      rights management screen uses the "add_rights" layout.

      For 5.2.1:

      Vocabulary management pages also use only layouts, directories using the "vocabulary" and "xvocabulary" schemas need to be explicitely declared on a new extension point (target: "org.nuxeo.ecm.directory.ui.DirectoryUIManager", point "directories") to be displayed.

      Show
      For 5.2.0: Added API: on directory Session and DirectoryManager: hasEntry(String) and createEntry(DocumentModel) on Layout: getWidget(String) and getWidgetMap() to ease cross validation (cf password verification with double check) on UserManager: a bunch of create/update/delete/search methods for users and groups using DocumentModel instead of NuxeoPrincipal and NuxeoGroup Changed API: document model retrieved from NuxeoPrincipal as now type "user" instead of "User" UserManagerActions and GroupManagerActions and SecurityAction have been refactored users and groups screen now entirely rely on the "user" and "group" layouts. rights management screen uses the "add_rights" layout. For 5.2.1: Vocabulary management pages also use only layouts, directories using the "vocabulary" and "xvocabulary" schemas need to be explicitely declared on a new extension point (target: "org.nuxeo.ecm.directory.ui.DirectoryUIManager", point "directories") to be displayed.

      Description

      The vocabularies and users management screens cannot be easily customized and have a few restrictions.

      A vocabulary manager component has been developed for a client project and could be used in the default application. It can handle any kind of directory (not only directories with the vocabulaty or xvocabulary schema) and takes configuration to define the layout used to display entries in a table, in view mode and in edit mode.

      Sample configuration is:

      <extension target="org.nuxeo.ecm.platform.VocabularyUIManager"
      point="vocabularies">

      <vocabulary name="subject" layout="subject_vocabulary" sortField="label" />

      </extension>

      The referenced layout is defined as usual, no specifics are needed.

      Some additional configuration could be added to handle dependencies between vocabularies (for hierarchy management for instance), so that a parent entry cannot be removed if it's referenced in a child directory.

      <vocabulary name="subject" layout="subject_vocabulary" sortField="label">
      <deleteCheck directoryName="subject_parent" idField="id" parentIdField="parentId" />
      </vocabulary>

      The table listing directory entries could be customized too so that deletion is done using checkboxes, and edition uses a single link on the vocabulary entry id.

      The user management screen could use this component too, and provide better widgets for users/groups search (suggestion).

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 2 days, 6 hours
                2d 6h
                Remaining:
                Time Spent - 2 days, 2 hours Remaining Estimate - 4 hours
                4h
                Logged:
                Time Spent - 2 days, 2 hours Remaining Estimate - 4 hours
                2d 2h