Difference between revisions of "Visibility Condition"
From SmartWiki
(→See Also) |
(→See Also) |
||
| Line 32: | Line 32: | ||
* [[Status Field Permissions]] | * [[Status Field Permissions]] | ||
| − | + | For help constructing logical statements for '''Visibility Condition''': | |
* [[Determining the statusid]] | * [[Determining the statusid]] | ||
* [[Determining the roleid]] | * [[Determining the roleid]] | ||
| − | * [[Advanced Logic]] | + | * [[Advanced Logic]] (for more examples) |
[[Category:Custom Fields]] | [[Category:Custom Fields]] | ||
Revision as of 14:12, 29 May 2009
The Visibility Condition section of Custom Fields and Standard Fields allows you to use logical statements to determine whether a field is visible or not.
Examples
To make the field visible after 06 February 2009.
now()>'2009-02-06'
To make the field visible only if the date in the field named Date Initiated is after 2009-01-31
'@Date initiated@' >'2009-01-31'
To make the field visible for a user with roleid 9999
',@me.rolelist@,' REGEXP ',9999,' =1
To make the field hidden for a user with roleid 9999
',@me.rolelist@,' REGEXP ',9999,' = 0
To make the field visible only when the status is Draft or Open
* '@status@' in ('Draft','Open')
- Note: The above Visibility Condition would only be used Standard Fields. Custom Fields have a separate Status Field Permission section that can be used.
More Examples,
'@Destination City@'='Toronto' '@Type@'!='Contract'
Note: remember to include the @fieldname@ in single quotes.
See Also
Access to Custom Fields can also be controlled using:
For help constructing logical statements for Visibility Condition:
- Determining the statusid
- Determining the roleid
- Advanced Logic (for more examples)
