Current object not available in View Rule Script

Manish Vinayak1 · ‎05-09-2016

Hi Everyone,

I am trying to create a view rule using the Advanced Option.

The requirement is to set the rule if the person is member of the assignment group, or is having some particular role.

But, the 'current' object is not available in the view rule scope. There is no proper documentation / example available for view rule script.

Any suggestions, how it can be configured / any other object that can be used within view rule scope.

Thanks,

Manish

PerV · ‎06-02-2017

Manish, late answer, but since the tread has been alive this year, I would like to share my five cents on this.

I had the same challenge, realized that current.xx is not available for use in advanced mode (even though the fields can be chosen from the field chooser to the right of the script field ).

To get around this I used the condition builder to use a Dynamic Filter (built a new one), from that dynamic filter I called a script include that checks for groups that the user belongs to (or not, in my case), thereby directing to two different views, depending on whether the user should see certain fields or not. In my case I wanted to hide the Activity history completely, but give the user write rights to the work notes field.

//Per

View solution in original post

Peter Tran2 · ‎02-07-2017

Hi,

Probably you should check your name field description again

tkrishna29 · ‎03-02-2017

Hello Manish,

Were you able to find the solution to your problem? I'm stuck in the same kind of problem too. Thank you.

felladin · ‎03-02-2017

There is no way to add code under "Advanced" that uses the current tag.

I ended up creating separate simple rules as I need to get this done before next release and it was not a big issue.

I will return though, and test calling a Script Include, as I have done in a few other places where the script field is limited. Script Includes is a good way to get more fulfilling answers regarding f.ex. conditionals for reference fields and notifications.

PerV · ‎06-02-2017

Manish, late answer, but since the tread has been alive this year, I would like to share my five cents on this.

I had the same challenge, realized that current.xx is not available for use in advanced mode (even though the fields can be chosen from the field chooser to the right of the script field ).

To get around this I used the condition builder to use a Dynamic Filter (built a new one), from that dynamic filter I called a script include that checks for groups that the user belongs to (or not, in my case), thereby directing to two different views, depending on whether the user should see certain fields or not. In my case I wanted to hide the Activity history completely, but give the user write rights to the work notes field.

//Per

Sruthi M · ‎02-05-2019

Can you share the script that checks current user is not member of current assignment group