portal
Many developers start to build the application by building portlets or JSPs first. This makes sense as the UI design prototypes can be utilize to kickstart development. However in my opinion Workshop and the automatic generation features work best if you start to build your application from the lowest layers first. Even though from the developer's perspective many complex portal applications look like rich clients, with complex PageFlows, and portlet interactions, users view the resulting portals as just another web page.
They will try to bookmark Step no. 5 of a "checkout order" wizard, and when they return, they will expect their half-done order process to be resumed, and they will still use the Back button, even if they've been navigating through many of your portlets, and expect that the result will still make sense. These lists show only the categories and perspectives relevant to the page groups chosen in the Page Group list. If a single page group is selected, categories and perspectives of that page group and the Shared Objects page group are displayed. If multiple page groups are selected, only categories and perspectives in the Shared Objects page group are displayed.
If you are an authorized user and are logged in to OracleAS Portal, you can save a search so that you can perform it again at a later time without having to remember all the criteria you specified. Simply click Save Search on the search results page, enter a name for the search, and click Save.Your saved searches are displayed in the Saved Searches portlet.
If you can not see the Saved Searches portlet, add the portlet to a page. If you do not have the privileges to add the portlet to a page, ask your portal administrator to add it for you. You can only see saved searches when you are logged in to OracleAS Portal.