FPC Architecture
FPC Architecture
The following figure describes how the FPC fits into the FabriKam environment and is used by FabriKam solutions. The components are detailed in the next section, FPC Components.
.gif)
Figure 1. The technological hierarchy of the SPMLLV FPC SPMLLV uses the Windows SharePoint Services Object Model to implement its functionality.
Using either defaults or specific user settings for library type and document template, the FPC builds a collection of matching libraries within the current SharePoint site. The collection is filtered by the current user's access privileges on the SharePoint site—only libraries that the user has access to are displayed. The whole collection is then presented in a custom configuration tool part, allowing the user to select specific libraries to show in the Web Part display.
From the list of library items selected by the user, a set of fields (or library properties) common to all selected libraries is presented on the tool part. The user selects fields for display from the tool part, along with the display order and aggregation options for each selected field.
Finally, the user configured properties from the tool part are transmitted to the Web Part. With its properties initialized, the Web Part extracts actual data values from selected libraries and renders a HTML view to its UI. If any of the aggregated properties of the document libraries are deleted after the tool part submits its changes to the Web Part, subsequent use of the tool part could send invalid data to be rendered in the Web Part. To avoid this situation, the Web Part refreshes the list of library properties displayed in the tool part whenever it is opened or modified.