Eric F Dunn commented on Dec 4, 2009

Section II - Architectural Overview

final image does not depict use of the Form List Portlet - as text describes.

Eric F Dunn commented on Dec 4, 2009

Section II - Architectural Overview

in the "BPA DesignTime Topology" section** the term BPA should be BPA Framework - we should be very careful about the use of these two terms.

Eric F Dunn commented on Dec 4, 2009

Section II - Architectural Overview

"Furthermore** the Unified Task List includes different task provider implementing data access to different workflow systems. This can be a WebSphere Process Server or Lotus Domino Server** but also any other workflow engine through a standard interface as shown in the following diagram." - diagram missing

Eric F Dunn commented on Dec 4, 2009

Section II - Architectural Overview

"A portlet that shows a list of forms ready to be claimed by the logged-in user (as a member of a group that can ‘claim’ work of that type)". The Form List Portlet does not show forms that can 'claim' - it shows forms that the logged in user can start processes with.

Eric F Dunn commented on Dec 4, 2009

Section II - Architectural Overview

"WebSphere Process Server is not forgiving ... in the persistence layer." - not clear what 'persistance layer' is. But yes, Forms need to be designed correctly such they empty values are communicated properly from Form to Process.

Eric F Dunn commented on Dec 4, 2009

Section II - Architectural Overview

"The BPA framework in its first release currently supports Lotus Quickr and the filesystem as repositories". not exactly correct, The BPA Framework supports any repository that provides a quickr REST API interface. We've tested agaisnt Lotus Quickr itself, and of course the file system based repository that ships with the BPA Framework, but others exist as well like CM and Filenet.