Action roles not being evaluated

I'm migrating a procedure from v7.6 to v9, there is an action which is set to be available to the ToDoList but it is not. I am not using re-open folder and I can clearly see the folder appearing on the todo list, so I know it's not a problem creating the alert. Used SQL profiler on it and it looks like the role isn't even being queried in the database. But when I change the role to the metastorm administrator, Originator, or everyone it works.

I guess I can work around the problem by changing the roles for the actions so that they never evaluate the ToDo list, but it would be better to fix it. It is a fresh install, so I can't rule out some config setting that I haven't set properly...

Has anybody else had this problem?

p.s. Where are the action roles saved in v9? The field they used to be stored in for v7.6 is blank now... Are they in the dll's?

Find more posts tagged with

BPM

Comments

achopra

Are you by chance using SSO?

I've seen something very similar to your problem, but only when using SSO. It turned out to be an issue with case sensitivity, where the domain name was coming through the SSO script in all lowercase, but I had (manually) entered users into the database with a capitalized domain name (DOMAIN\username). I modified the users in the database to all lowercase and the problem went away.

Carolyn Anderson

You're right, it does seem to have something to do with this. I'm not using SSO on this server, but I have all the users in the eUser table in capital letters (imported from our v7.6 database, which does use SSO), and the alerts are writing the username in small letters for some reason. When I went in and manually changed the username in the alerts table to capitals the option appeared ok. Thanks.

But this is a test system, and the live one will have SSO and the usernames will be in capitals, so I'm guessing if I don't find out why it's writing small letters to the alerts, I'm going to have the same problem when I do the live system? Somehow I need to fix how it's writing the alerts...

Carolyn Anderson

Ok, I got it, the eAssignment table didn't have the user capitalised. I deleted the user out of the database and re-added in capitals, and it's added ok, so it must have been down to creating the test user with small letters. Fixed.

achopra

The workaround that I implemented was to modify the eSSO_Web.sap to get the username from the eUser table, rather than just passing through the username as it was passed into the script. That way, the session will be established using the same case (upper, lower) as is in the eUser table.