Last post Aug 13, 2005 01:19 PM by ttawin
Jul 28, 2005 04:53 AM|realitysleeps|LINK
Aug 01, 2005 01:41 PM|pschaef|LINK
Here is one approach:
- All items are in a single list.
- Each department has its own web part page. On that page, put a Data View Web Part with the filter set to that department.
- A second DVWP could exist with filter set to [me].
Aug 13, 2005 01:19 PM|ttawin|LINK
My manager has made similar requests like this on security and after much thought about WSS (not SPS) I have come to these conclusions:
WSS is a portal framework and an out-of-the-box web application with a document-centric and team-centric architecture to allow the sharing and collabration of documents among the team members. If we use WSS for this purpose then its features and security implementations
make sense. Within WSS, if a user has "Edit/Update" privilege then he will also has "Read" privilege to the document library/list. And when applying security, the document library/list is the lowest component level that can be set. You cannot apply security
settings to the invidual document or list item within a document library/list. Therefore, in your case, I do not believe you can acheive this security settings with the basic features of WSS.
For me, it is difficult to convince my manager that we CANNOT simply utilize WSS out-of-the-box features to set up a traditional business OLTP applications. As I stated earlier, WSS is a team's document sharing/collaboration environment with specific focuses
to managing documents and to managing teams. We cannot treat OLTP data simply as document and users as team members then allow WSS to manage the OLTP data and the users. It is not appropriate.
However, WSS, as a portal framework, can be a central host (via webparts) to various business applications. But, these business applications must still be developed independently of WSS and its data still stored within a dedicate database (and not within the WSS content
database) so that data can still be analyzed and protected through custom logic just like a traditional ASP.NET web application. We cannot force fit the OLTP data/logic into the document/team-centric architecture of WSS.