Hello, community, In OFBiz, * definition of portalPortlets, * definition and content of the portalPages (column and which portlet in each one) * portalPortlet attributes for a portalPage * and some other details about the organization of the portal are stored in the ofbiz database.
As Nicolas says, it is not practical/advisable to manage/sharing GUI changes in a development process (and continuous integration) because they are not managed by a VCS (svn or git). So I propose to * create a widget-portal.xsd * a new general property to read (or not) the database for the organization of the portal * some modifications on include-portal to read the portal information on the xml file and if the property is Yes the complementary elements in the database. With these modifications it will be possible to dynamically add portalPage or Portlet and use editParam features when working with ProductOwner/keyUser/endUser but not in a production environment. After the workshop, the consultant will have to formalize what has been validated in the appropriate xml file and commit it in order to have it in production environment if the GUI test are ok (the modifications don't break anything ;-) What do you think about this ? Olivier
