Skip to Content
author's profile photo Former Member
Former Member

Namespace filter: Only show files that were created by user

Hi,

we want to implement the approval workflow to a repository folder. All users should be able to upload files, work on them and start the approval process. If the process completes succesfully, the file should be visible to all users. Unfortunately all users with write permission can see all files, while it is still "in progress" status, whether they are the owner or not. This makes the approval workflow useless to us, since all users need write access to demand their work for approval.

To solve the problem we wanted to create a new namespace filter for this repository. We use the KM Navigation iView to display files. With this filter, any iView shouldn't display files anymore if following filter conditions comply with at read request time:

if the resource's status is still in progress:

- the user who requests needs be the owner (creator) of the resource

or

- the user who requests needs to be a valid approver for the repository folder

How to develop a namespace filter is already documented, but i cannot find the following objects for comparison with String IResource.getCreatedBy() at read request time within the filter:

- the requesting user

- the valid approvers of a repository folder

Thanks in advance and best regards

Philipp Eisenmann

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Nov 09, 2004 at 02:02 PM

    Hi!

    Do you resolved this problem? I also have this problem...

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hello,

      some general remarks about the usage of Namespace filters. Since these filters are used for every access to the registered repository the implementation need to be done careful concerning performance issues. Moreover, the administrator, e.g. content manager, need still to have full access to that repository. This is also true for system principals like the service users.

      Another approach could be to use ACLs. Whenever a document is created, an ACL is set to that document like Everyone Read. In this case the other authors only have access to the document as soon as it is released. In this case you need to develop an event receiver which might be easier.

      If there are only a limited number of editors, e.g. 5 groups of editors, the usage of separate folders with ACLs could be used without any further development.

      Kind regards,

      Roland

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.