Details

    • Type: Task
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 2.6.CR2
    • Fix Version/s: 2.6 CR3
    • Component/s: Portal Core
    • Labels:
      None

      Description

      Management Portlet

      The page that houses the management portlet called "Home" has the Pages portlet on it as well. This portlet is redundant since it just repeats what is in the navigation tabs. It should be removed.
      Consider using icon images (with alt attributes set to the name of the function) for actions in the lists in this portlet.

      Portal Objects

      Portal List Screen

      Label "Creating a portal" is above the field it is associated with. This label should be to the left of the field.

      Page List Screen

      The "Create a nested page:" label should be changed to "Create a Page:"
      The text box to create a page, and the drop-down list below it should be left aligned in the same column.

      Portlet Window List Screen

      The text box for creating a nested page, and the drop-down list for the default page should be left aligned in the same column.

      Portlet Window Details Screen

      When clicking on the Window Name of a portlet window, the user is taken to a screen showing a list of portlet Instances, but the current portlet instance is not shown. The current portlet instance should be the default selected item in the list.
      The Portlet Instance list should have a field label describing what it is. Perhaps "Portlet Instance used by this window:".
      Clicking the "Select" button shows the same result as clicking the "Info" button, but no feed back is given to the user that they have updated the portlet instance that the portlet window is using. Clicking the "Select" button should change the screen back to the Portlet Window List screen.

      Wizard Mode

      On the final screen of the wizard, the "confirm" and "cancel" buttons should be on the same horizontal line as the "previous" button, but separated by more space than between the "previous" and "next" buttons on the previous pages. The buttons should have as much spacing between them as all the other steps int the wizard.
      The "Step" panels at the top of each of the wizard pages should be clickable so that the user can get back to any point in the wizard.
      In Step 5 "Confirm", the field labels should be bolded, there should be a colon after each field label, and the field data should be left aligned in a single column (this alignment may already be there, but I couldn't be sure)
      In Step 3 "Select Page" of the wizard, the table that contains the portal regions should be extended to fill the width of the portlet, as with all the other tables in the portlet.
      The "Sub-Pages" function should be left aligned in the cell.
      In Step 1 "Select Portlet" of the wizard, the "Next" button should be disabled until a portlet has been selected.
      In Step 2 "Select Portal", the "Previous" button should have the same padding as the "Next" button.

      Security

      • The security screen on any portal object should have the table of permissions replaced with a table of checkboxes, but the permission label at the top of each column, and the roles at the leftmost column should have the word "Role" removed and placed at the top of the column. The table should be styled similarly to the other tables in the management portlet.
        The "Update" and "Cancel" buttons should be moved to the left side of the portlet, sized, padded, and spaced similar to the rest of the buttons in the portlet.
        After applying security settings, there is a message displayed at the top of the resulting view in the portlet. This message should be bolded, and it's size increased.
        When clicking on the security action for an item not in the current context, subsequently clicking cancel should return the user to the parent context. For example, if a user selects the default portal, then clicks the security link from the default page from within the default portal details page, they are presented with a security screen for the default page. But when the user clicks cancel, they are sent to the default page detailed view, instead of being sent back to the page they came from, as would be expected.

      Properties

      In the "Properties" screen for a portal instance, the style on the predefined property drop-down list doesn't match the style of any of the other drop-down lists in the portlet.
      The "Properties" screen for portal objects should have a "Cancel" button.
      The "Properties" screen should align the "Add Property" button to the left side of the portlet.
      If there are no remaining predefined properties to add to a portal object in the "Properties" screen, the predefined property field and its label should be hidden.
      The label for the custom property field should be changed to read "Custom Property Name:"
      The border around the predefined and custom property fields should be removed.

      Theme

      In the "Theme" screen for a portal object, the border and "Theme Properties" label should be removed.
      The "Update" and "Cancel" buttons in the "Theme" screen should be left aligned.
      The "Please set the display options for the portal: " label at the top of the screen should be replaced with the title "Theme Properties".

      Destroy

      The "Destroy" screen should show the tabs similar to the other screens in the management portlet.
      The "Breadcrumbs" under the WARNING message should be placed at the top of the screen, similar to other screens in the portlet.
      The WARNING message should be increased in size, and bolded to show its importance.
      The "Yes" and "No" links should be made into buttons to be consistent with the rest of the screens in the portlet.

      Portlet Instances

      In the Portlet Instance Details that show up at the bottom of the portlet when a portlet instance ID is clicked, the field data should be left aligned in a column next to the labels.
      The "Show the associated portlet" link should be removed, and the name in the "Portlet Name" should be a link to the associated portlet definition instead.
      If the portlet instance has no Preferences, do not show the Preferences link for it.
      The "Security" and "Preferences" actions show their screens below the portlet instance list, which is inconsistent with the action screens in the Portlet Objects section. The action screens should be shown and the list hidden, or the action screens in the Portlet Objects portion of the portlet should operate like these screens.
      The destroy action has no confirmation screen for it. It should have a similar confirmation screen to the destroy function in the "Portal Objects" section of the portlet, with the aforementioned changes applied.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  theute Thomas Heute
                  Reporter:
                  julien1 julien1 (Inactive)
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: