Difference between revisions of "InRole"

From SmartWiki
Jump to: navigation, search
Line 11: Line 11:
 
{|
 
{|
 
|'''Correct''':
 
|'''Correct''':
|'''@me.inRole(Organization Contact)@'''
+
|'''''@me.inRole(Organization Contact)@'''''
 
|-
 
|-
 
|<font color="red">'''Wrong''':</font>
 
|<font color="red">'''Wrong''':</font>
|"@owner.inRole(Organization Contact)@" - don't put quotes around the variable. It's a true/false value, not a string.
+
|''"@owner.inRole(Organization Contact)@"'' - don't put quotes around the variable. It's a true/false value, not a string.
 
|-
 
|-
 
|<font color="red">'''Wrong''':</font>
 
|<font color="red">'''Wrong''':</font>
|@me.inRole("Organization Contact")@ - don't put quotes around the role name. The role name is ''Organization Contact'', not ''quote Organization Contact unquote''.  
+
|''@me.inRole("Organization Contact")@'' - don't put quotes around the role name. The role name is ''Organization Contact'', not ''quote Organization Contact unquote''.  
 
|-
 
|-
 
|<font color="red">'''Wrong''':</font>
 
|<font color="red">'''Wrong''':</font>
|"@me.inRole("Organization Contact")@" - don't put quotes around both things...
+
|''"@me.inRole("Organization Contact")@"'' - don't put quotes around both things...
 
|-
 
|-
 
|<font color="red">'''Wrong''':</font>
 
|<font color="red">'''Wrong''':</font>
|@me.InRole(Organization Contact)@ OR @me.inrole(Organization Contact)@ - use the correct capitalization, ''inRole''
+
|''@me.InRole(Organization Contact)@'' OR ''@me.inrole(Organization Contact)@'' - use the correct capitalization, ''inRole''
 
|-
 
|-
 
|<font color="red">'''Wrong''':</font>
 
|<font color="red">'''Wrong''':</font>
|@me.inRole(''rolename1'' OR ''rolename2'')@ - instead of this, use @me.inRole(''rolename1'')@ OR @me.inRole(''rolename2'')@
+
|''@me.inRole(''rolename1'' OR ''rolename2'')@'' - instead of this, use ''@me.inRole(''rolename1'')@ OR @me.inRole(''rolename2'')@''
 
|}
 
|}
  

Revision as of 14:24, 16 July 2013

This syntax can be used on Submit Logic, Advanced Logic, visibility conditions, browser scripts 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 will return a string which is useless if not equaled to another string.
  • Do not encapsulate the role name – This 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)@" - don't put quotes around the variable. It's a true/false value, not a string.
Wrong: @me.inRole("Organization Contact")@ - don't put quotes around the role name. The role name is Organization Contact, not quote Organization Contact unquote.
Wrong: "@me.inRole("Organization Contact")@" - don't put quotes around both things...
Wrong: @me.InRole(Organization Contact)@ OR @me.inrole(Organization Contact)@ - use the correct capitalization, inRole
Wrong: @me.inRole(rolename1 OR rolename2)@ - instead of this, use @me.inRole(rolename1)@ OR @me.inRole(rolename2)@

See Also