If you want to have 'tasks' surfaced in the portal, then I think that the 'cases' is probably the best example to model your new code. If you want to configure special security for tasks other than always showing tasks that are related to a contact,
then you would want to add a security entity for configuring that security (taskAccess as you mentioned), but if you don't need that additional security, then you won't need that security entity.
Adding tasks to the portal will likely mean adding a task list page as well as a task detail page. The job of the task list page is to list open tasks, and you can use a CrmEntityFormView control and tie it to a CRM view, or you can use a standard
Linq query in the code-behind and then use CrmSavedQueryColumnsGenerator() to build columns for a data table. These techniques are all in the source code of the customer portal under the /Pages/eService folder.
I would highly recommend you use Visual Studio and debug the existing customer portal. Place some breakpoints in some of the pages that interest you and examine the variables and page flows and step through the page one line at a time. Examining
how the portal is running is one of the first steps to learning how to write your own extensions.
Good luck!
Shan McArthur www.shanmcarthur.net Check out the commercial edition of xRM portals @ www.adxstudio.com
