Difference between revisions of "InRole"
From SmartWiki
| Line 1: | Line 1: | ||
| − | + | This syntax can be used on submit logic, visibility condition, browser script or any other role specific validation. It will always return a value, either true or false. | |
| − | + | <pre>@object.inRole(Rolename)@</pre> | |
There are three things to use caution about this syntax. | There are three things to use caution about this syntax. | ||
Revision as of 14:56, 18 September 2012
This syntax can be used on submit logic, visibility condition, browser script or any other role specific validation. It will always return a value, either true or false.
@object.inRole(Rolename)@
There are three things to use caution about this syntax.
- Case Sensitive – Watch for lower case “i” and upper case “R”
- Do not encapsulate the whole syntax – This syntax always returns a value, either true or false which mostly would not cause any problems for example in sslogic or visibility conditions. However encapsulation of the syntax would basically return a string which is useless if not equalled to another string.
- Do not encapsulate the role name – This I believe is looping the role names in the instance and tries to match what is in the brackets. Use the exact role name without encapsulating.
Correct: @me.inRole(Organization Contact)@
Wrong: “@owner.inRole(Organization Contact)@”
Wrong: @me.inRole(“Organization Contact”)@
Wrong: “@me.inRole(“Organization Contact”)@”
Wrong: @me.InRole(Organization Contact)@ OR @me.inrole(Organization Contact)@
