Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

1.1 The Dashboard should be the OFBiz backoffice "home" page
1.2 Multiple Pages should be allowed and the user should be able to select the desired page using a drop-down (DONE)
1.3 User should be able to create as many new "private" pages as needed (if they have the related b. permission) (DONE) (TO DO: permission b. check)
1.4 The pages that the user can select are all his own pages (the ones he has created) plus the "system" pages
1.5 The "system" pages can be created only by users with a specific permission (a. permission)

...

2.1 User should be able to delete his "private" pages (if he has the b. permission) (DONE) (TO DO: permission b. check)
2.2 User should be able to edit his pages. This means: (if he has the b. permission) (DONE) (TO DO: permission b. check)
2.2.1 Add/Remove columns (DONE)
2.2.2 Set column sizes
2.2.3 Add/remove portlets (DONE)
2.2.4 Configure portlets (attributes change) (DONE)
2.2.5 Move a portlet to another page (DONE)
2.2.6 Move a portlet to a different column or row on the same page (DONE)
2.3 User should be able to create a new page starting from another already existing page (page copying). This will let users to copy a "system" page into a private page and to change it.
2.4 When adding a new portlet to a page the user should be offered all the portlets available in the system (DONE)
 

3. Portlets

3.1 Every application should define the portlets that are needed to the user adding related entity in the database (DONE)
3.2 A path to a screen that renders the portlet should be specified in the Portlet entity (DONE)
3.2 An optional path to a screenshot image of the portlet could be added in the Portlet entity. The image will be visible to the user when he is asked to select a portlet to add to a page (DONE)
3.3 An optional configuration form for the portlet could be added in the Portlet entity. This should be a simple form extending from a predefined form and will be used to edit some portlet specific attributes.
    For example a portlet that shows a list of items could have an attribute defining the max number of elements to show. Every single portlet occurrence will have its own attributes. (DONE)
3.4 The portlet should not check if the user has enough permission to view the portlet. This will be checked in the Application inside the screen (and optionally the editing form) definition. (DONE)
 

- Dashboard system specific Permissions needed -

...