In reply to:2. I think I saw another posting on this just a moment ago... but is there any way to report on *finished* Workroute MP workflows in the UI? No, not in the current UI.
In reply to:4. Anyone have any experience building a tree-view of knowledge space folders in the UI?Perfect Timing. We are working on a custom viewset with this feature. Please talk to Product Management for release schedule.
In reply to:5. The concept of a document life-cycle is a little weak in WorkSite MP... there really needs to be a good "publishing" mechanism for producing "public" content from documents that can go through various states of draft. Is there an existing best-practice around this? Bookmarks are a possible partial solution, but do help when linking back to a single document that was published at version 2 and is now undergoing further revisions. If that makes sense. What I mean is:-Version 1 of a document is created.-A team of reviewers marks it up and makes changes to versions 2-5.-Version 6 is "final" and ready for publishing as a public, company-wide document.-Several months later, the review team realizes the document still needs more work. What is their best course of continuing on? If the security policy was simply changed to make the document public or a bookmark was placed on some other workspace (likely a knowledge space) pointing back to the current version of the document, how does the review team move forward without affecting the "public" version of the document? A copy might solve the issue, but I'm try to reduce data duplication, not increase it. Will the new PDF engine help here at all? I've not played with that yet.I have a couple of comments: Tbe best bet now would be a custom workflow to review and publish the content with custom metadata to link both documents. Providing bookmark links back to the 'published' document in the original place is not good idea. It works only when all the users of the destination container are part of the source container too. Also you need to pay attention to the security policies of the parent containers for the source location.
In reply to:6. I'm trying to figure out how to make use of the "catagory" type of workspace-specific metadata, with an eye towards solving issue #1, above. I can create the things easily enough in xml or the object modeler, but I'll be damned if I know how to populate them or make them visible & useable in the UI. Any experience here?Bijoy: Can you please elaborate a bit more? Are you referring to use workspace metadata in the configuration tools?
In reply to:7. Anyone have a concise list of *exactly* what SQL Server permissions are needed by the WorkSite MP user / database owner? So far I've just given that user admin rights, but there will come a day when a client won't allow that.Let me forward this question to an expert.
In reply to:8. How is Search Relevance computed, and what exactly does it mean?Let me forward this question to an expert.
In reply to:10. It looks like any user can start a workroute workflow. I'd like the ability to prevent certain users from kicking off (or even knowing about) certain workflows.None available now.Anything planned that you know of?[quote]11. Is there a way to limit a user so that they can add content / files, but not make changes to the folder structure? Right now, giving someone "add" privileges allows them to add both files and folders.This privilege is not available for document folders on WorkSpace. A similar feature is available in Knowedge Space for categories.
In reply to:12. It looks like at the moment that the switch that allows users to replace existing document versions or not is at the library level. True? I need it at the trustee or workgroup level if possible, so certain users will be denied that feature while others can make use of it. Anyone ever have and solve this need?Yes, this is a library level configuration option. It is not a trustee level privilege.