Difference between revisions of "Visibility Condition"
From SmartWiki
Line 14: | Line 14: | ||
To make the field hidden for a role # 9999 | To make the field hidden for a role # 9999 | ||
',@me.rolelist@,' REGEXP ',9999,' = 0 | ',@me.rolelist@,' REGEXP ',9999,' = 0 | ||
+ | |||
+ | To make the field 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 Permissions|Status Field Permission]] section that can be used.'' | ||
+ | |||
More Examples, | More Examples, |
Revision as of 14:05, 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 role # 9999
',@me.rolelist@,' REGEXP ',9999,' =1
To make the field hidden for a role # 9999
',@me.rolelist@,' REGEXP ',9999,' = 0
To make the field 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 Role Field Permissions and Status Field Permissions