Project and Portfolio Management Practitioners Forum
cancel

For multi users the secuirty at WF step not working

Highlighted
Phanishwar
Honored Contributor.

For multi users the secuirty at WF step not working

Hi ,

There is a business requirement to provide access to risk/issue etc on workflow steps These users are manually entered on Projects .

What I am doing is that I have created a hidden field with PPM - User -all Validation , ACL Type . this field is populated with rule and to syn with project users always ( a job would be scheduled to sync users on project and on risk/issue form(hidden field).

The issue is that when this hidden field has single value then that user see the Action button(can take access) . however for more than one user the security at workflow step defined is not working??...is that for custom field with multi users the securuty doen not work?


Access defined at workflow step as :

User Dedfined token(hidden field token)--[REQ.P.KNTA_PROJECT_MANAGER]
secuirty type : user id

PPM 7.1 , SP7 version
8 REPLIES
Vinod Jadhav
Super Contributor.

Re: For multi users the secuirty at WF step not working

What is the separator used for multiple values in the token?

Regards
Vinod
Phanishwar
Honored Contributor.

Re: For multi users the secuirty at WF step not working

ok..thanks!!..ya that was the issue..By using #@# it is working...thanks!!
Semenov Alexand
Acclaimed Contributor.

Re: For multi users the secuirty at WF step not working

Phanishwar am interesting.
let me see you working token
Thanks
Phanishwar
Honored Contributor.

Re: For multi users the secuirty at WF step not working

THis is the Token : [REQ.P.KNTA_PROJECT_MANAGER]...my rule populates the this hidden field with #@# seperator for multiple users ..so it works..earlier it was separeted by ";" ..so it was not working..


Now if you are interesed in that once rule is fired based on project field and if new users are entered in the project ..then new users value will not sync in risk/issue hidden value so it will not work...is that the case ..The solution is as below :

Write a rule on filed change(field which user is required) on project and call a autonomous function in the rule such that you update the hidden field value in risk/issue form as autonoums fucnction allows you to use DML(update) statement..this will sync project field and risk/issue hidden filed...Let me know if for any question.

Thanks!!
Phanishwar
Honored Contributor.

Re: For multi users the secuirty at WF step not working

see the rule screenshot
Phanishwar
Honored Contributor.

Re: For multi users the secuirty at WF step not working

sorry guys..there is a typo mistake...:)

how come knta_project_manager..it's OOTB standard token..it can't be custom one..:)

mine is PROJECT_MANAGER...:)

Phanishwar
Honored Contributor.

Re: For multi users the secuirty at WF step not working

Alexander,

I am using Autonomous function to sync to forms..pls put your inputs on this!
Semenov Alexand
Acclaimed Contributor.

Re: For multi users the secuirty at WF step not working

Many Thanks