The CreatorCon Call for Content is officially open! Get started here.

Impersonation issue

kais_b
Kilo Contributor

Hi everyone,

I've got a an issue with a user that I'm impersonating.

When the user is logged into his account he can approve changes and close them without having to pass through the approval process in the workflow.He shouldn't be able to do that.

When I impersonate this user, the user can't approve and closechanges himself. He has to make an approval request. this is the proper behaviour.

I have no Idea how this can happen. the user doesn't have the role to approve the change himself and the worklfow works fine for everybody else.

Do you guys have an idea about how I could solve this?

Regards

Kais

1 ACCEPTED SOLUTION

oharel
Kilo Sage

Hi Kais,


I have three suggestions:


1. This may sound a bit strange, but are you sure you are impersonating the user? Perhaps the user has two different accounts (but with the same name) and you're using the other account?


2. Carefully check the conditions of the UI actions that allow the user to do whats/he is doing.


3. Ask the user to show you what they are doing to approve and close the change. Maybe they are doing it in some roundabout way that you did not think of. Or might be that they are doing something that triggers a client script or a BR that approves or closes the change for some reason.


Even when you think you created a water tight process, end-users can surprise you...



Harel


View solution in original post

3 REPLIES 3

oharel
Kilo Sage

Hi Kais,


I have three suggestions:


1. This may sound a bit strange, but are you sure you are impersonating the user? Perhaps the user has two different accounts (but with the same name) and you're using the other account?


2. Carefully check the conditions of the UI actions that allow the user to do whats/he is doing.


3. Ask the user to show you what they are doing to approve and close the change. Maybe they are doing it in some roundabout way that you did not think of. Or might be that they are doing something that triggers a client script or a BR that approves or closes the change for some reason.


Even when you think you created a water tight process, end-users can surprise you...



Harel


kais_b
Kilo Contributor

the third one is the correct one for me!


thanks!


Hi Kais,



I am glad it helped.


Please mark my answer as correct, so it can be removed from the unanswered list.


Thanks


Harel