@userroles does not work in view?

HCL Domino Domino Forum
1

I have a column with formula:@userroles

but the formula returns nothing (null). However in the doc computed formula it works.

Does @userroles work in view column formula?

2

Subject: Directly from the Designer Help Database

@UserRoles

For a database on a server or a local replicated database, returns a list of roles that the current user has. Roles are defined in a database’s access control list.

Syntax

@UserRoles

Return value

roles

Text list. Each item in the list is the name of a role that the current user has in the current database. The role names are enclosed in brackets. Returns an empty string (“”) if the current database is local and not a replication.

Usage

This function does not work in column, selection, mail agent, or scheduled agent formulas.

Only roles explicitly assigned to the current user are returned. Roles assigned to a group which includes the current user are not returned.

@UserRoles appends $$WebClient to the list of roles when a Web user opens a database.

@UserRoles returns a subset of the information returned by @UserNamesList.

3

Subject: @userroles does not work in view?

From Domino Designer Help:

…

Usage

This function does not work in column, selection, mail agent, or scheduled agent formulas.

4

Subject: RE: @userroles does not work in view?

Yeah, I didn’t realized column = view column.

5

Subject: @userroles does not work in view?

No… when you think about it, this mean mean that each view would have to be indexed for each user. Not all @formulas are available in the view column

6

Subject: RE: @userroles does not work in view?

I am trying to make a “My Tasks” view.

Basically the view is the same but the information differs depending on the role of the user. e.g. approvers only see approval type of tasks.

Is there any way to realise this (other than creating multiple views)?

7

Subject: RE: @userroles does not work in view?

Jon,

To customize a view to display only the docs relevant to each user, you would consider:

  1. Reader Names, but note that there are performance and maintenance issues here, so not a trivial solution

  2. Shared, private on first use views. Lots of maintenance issues here.

  3. Embedded view, show single category. If you can make this work for your needs, it’s the best solution.

  4. Categorized view, where users click on the appropriate category. This is the easiest, but people often don’t like seeing the other categories.

hth,

raphael