Difference between revisions of "Visibility Condition"

Revision as of 14:12, 22 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 1. To make the field visible after 06 February 2009.

  now()>'2009-02-06' 

2. To make the field visible for a role # 9999

  ',@me.rolelist@,' REGEXP ',9999,' =1

3. To make the field hidden for a role # 9999

  ',@me.rolelist@,' REGEXP ',9999,' = 0

4. More Examples,

  '@Destination City@'='Toronto' 
  '@Type@'!='Contract'

Note: remember to include the @fieldname@ in single quotes.

For example, if you used the following Visibility Condition:

• now()>'2009-02-06'

The field will only be visible after 06 February 2009.

These conditional statements can also refer to other fields:

• '@Date initiated@' >'2009-01-31'

The field will only be visible if the date in the field named Date Initiated is after 2009-01-31

• '@Destination City@'='Toronto'

The field will only be visible if the entry in the Destination City field is Toronto

• '@status@' in ('Draft','Open')

The field will only be visible when the status is Draft or Open

Note: remember to include the @fieldname@ in single quotes.

Access to Custom Fields can also be controlled using Role Field Permissions and Status Field Permissions