RE: Calling for V3 Feature Requests

From: tedteng (anonymous_at_discussions.microsoft.com)
Date: 02/12/04 

Date: Wed, 11 Feb 2004 21:36:05 -0800

if possible. allow the security permission per DOCUMENT unit.

br

ted
     
     ----- anonymous@discussions.microsoft.com wrote: -----
     
     here here
     
     All good suggestions. And it would be a crime to put out
     the next version without folder and document level
     security.
     
     my 2 cents
>-----Original Message-----
>Bill, I have sent out the emai. But for the discussion.
     I attached my email below:
>>==============
>Hi, Bill. Hope nobody say I am not too greedy for V3
     features. cheers
>>>>1. Powerful Site data usage analysis report
>>2. Enable the different permission setting per dl,
     per list, on an area like wss sites
>>3. more views for events, like a mini calendar view
>>4. Easier customization of portal layout with some
     tools to let user to change elements of the sps.css
>>5. Auto reject the dead links on portal
>>6. The folder view of the DL can display how many
     docs inside the folder
>>7. Now event list can all allow users to add two
     event items with time conflicts, expect another
     alternative option that users are NOT allowed to add two
     items with time conflict, that means only one event item
     one time. That will be easier for users to expand the
     usage of the event list, e.g. the event list can be used
     as a meeting room booking system.
>>8. Contact list now imports from outlook address
     book. Expect it can be imported from user profile
     database and the fields and items imported can be user
     defined and mapped.
>>9. Auto check the not existing domain users why
     synchronizing the user profile database with domain AD.
>>10. now users can only handle DL events but users
     sometimes need to handle the LIST events which is not
     available
>>11. The columns can be defined with a type which
     imports from other list field.
>>12. The task issue listâ?Ts assign-to column could be
     defined by users or pointing to the user profile database
>>13. Provide a page to enable users to change their
     contact details(telephone no. etc ) which can be written
     back to AD/Global Address Book
>>14. A tree structure of all sites(including areas and
     wss sites) for admin to manage and monitor
>>15. Easy storage quota definition by user and by site
     both
>>16. Can backup and restore per area
>>17. Provide RSS web part
>>18. So far the Office Webpart is hard to deploy.
     Expect some copy and paste silly operation like the
     Content Editor Web Part
>>19. Provide some methods to allow SQL actions like
     join between two lists to generate some new list
>>20. Expect the Functions of Document Management
     Systems such as the self-defined approval process
>>21. Multiple parameters can be passed between web
     parts during connection operation
>>22. InfoPath Form Display Webpart
>>23. More exact the permission right, say delete / add
     an item can be seen as two right permissions
>>24. More views of Group Listing or let Group Listing
     act as a normal List which can add some new columns.
>>25. Allow developers to extend the webpart class to
     create a new web part inheriting the exiting web part
>>26. Users do not know the alerts mechanism. Expect to
     let users to create alerts with more complicated filter
     conditions.
>>>>>>>>> ----- Bill English [MVP] wrote: -----
>> I know I've posted this here before, but here goes
     again. I'll be
> presenting to the SPS product team in April on the
     new features that people
> want in Version 3.
>> If you have suggestions, I'm all ears. Please
     email me at
> benglish@networknowledge.com. Also, please use the
     subject line V3 Feature
> Request. If your email even remotely looks like
     spam, I'll delete it.
> Using this subject line will help ensure I don't
     delete your email.
>> Thanks.
>> --
> Bill English, MCSE, MCT, MVP, MCSA, GSEC
> https://www.sharepointsummit.com
> sharepointdiscussions-subscribe@yahoogroups.com
>>>>>>>.
>

Relevant Pages

  • Re: Permission to eat meat
    ... There are mitzvot asei and there are mitzvot lo taaseh. ... We aren't given permission to eat birds on ... >the list -- we don't need permission for that. ... it lists the *forbidden* birds. ...
    (soc.culture.jewish.moderated)
  • RE: Calling for V3 Feature Requests
    ... Bill, I have sent out the emai. ... The columns can be defined with a type which imports from other list field. ... A tree structure of all sites(including areas and wss sites) for admin to manage and monitor ... Provide some methods to allow SQL actions like join between two lists to generate some new list ...
    (microsoft.public.sharepoint.portalserver)
  • Adding Roles With Selected Permission In Custom Add Role ASpx Page
    ... I have made a custom aspx form that lists down all the available permission ... rights for all groups in a Grid, and provides a text field for Site Group ... document libraries, edit Web discussion comments in documents, and customize ...
    (microsoft.public.sharepoint.portalserver.development)
  • RE: limit issues in issue list
    ... you will have to assign the view permission to each ... the "View List Items" permission) you have granted to them. ... every user who can access the WSS list will at least been ... link in the WSS site so that these users can view these lists. ...
    (microsoft.public.sharepoint.windowsservices)
  • RE: Calling for V3 Feature Requests
    ... >agree the security per folder. ... Contact list now imports from outlook ... wss sites) for admin to manage and monitor ... join between two lists to generate some new list ...
    (microsoft.public.sharepoint.portalserver)