The functionality contained in the portal is facilitated by modules. i.e. Group Collaboration module contains the group calendar and group surveys islands and the standard module contains the rich text editor island. Note that each module has it’s own data source, which could be data from a 3rd party app. The portal fx provides services to modules, such as the user directory, workgroups and pages, and logging. There is no limit to the number of modules the portal can contain.

Portal Modules Include: (Islands, Action Pages, Search Items, Headquarters Items, Module Properties, Module Administration Items, Events, Event Handlers, Help Items)

-A module may contain several entities that facilitate the presentations of functionality. Can contain none or all of these entities. You can have as many of each entity as you need.
-Most common entities are island and action pages.
I-slands are typically used for data display as opposed to data-entry.
-An island can have several action pages, which are most commonly used as the data entry/manipulation for an island (more on this in the example).
-Headquarter items are similar to islands, but are only available from the headquarters page.
-They are often used for aggregating data or providing a quick link to more detailed information or entering data
-Search items are a non-UI entity that facilitate data searching/retrieval and control how the module’s data is searched, given a search term.
-A module property is another non-UI element that acts as a storage mechanism for settings apply to a module (i.e. connection string, file storage paths).
-Module administration item shows a user interface available to the user/role designated as the module administrator and is typically used to manipulate module objects that an end-user should have direct access to (i.e. adding and removing Help Desks).
-Events facilitate cross-module communication (i.e. Help Desk Request Added).
-An event handler can act upon a raised event (add functionality to your module when a Help Desk Request is added).
-It’s very uncommon to raise and handle an event in the same module.
-A help item is a text page that explains how to use a product/feature.
-Items are added to a configuration file and later merged with portal/module help on runtime


The decision tree is used to determine what type of module entity should be used for a particular feature. To use it you start in the upper-left corner at “Feature” and answer the questions with one of the choices provided along the way. It is important to note that not all features will fit into this decision tree, particularly those features that are a sub-feature of a module entity (we’ll have an example of this at the end of our feature list).

Using the tree, see if you can arrive at the correct Module Entity to satisy the following conditions:

Feature #1: As a user I want to view my contacts as a categorized list. A contact is required to have to following information: Company Name, Contact person, Contact phone, Contact email. A contact has optional information: Address, Fax, Notes, Website. Answer

Feature #2: As a workgroup manager or assistant manager I want to be able to Remove, Add, and Update contacts. Answer2

Feature #3: As a Module Administrator I want to be able to RAGU categories. Answer3

Feature #4: As a Module Administrator I want to be able to set the connection string. Answer4

Feature #5: Contacts can be searched by Contact Name & Company Name (when you play with this at home you can add all the fields you want!!!) Results will be filtered to show only those contacts in my workgroups. Answer5

Code For Download:
-Rolex Module
-RSS Module
-API Documentation

Last edited May 27, 2008 at 3:16 PM by honkywater, version 12


No comments yet.