Difference between revisions of "Visibility Condition"

Revision as of 14:26, 2 June 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 on or after 2009-01-31

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

IMPORTANT: for a visibility condition based the startdate or enddate standard fields you should use '@fullstartdate@' rather than '@startdate@' and '@fullenddate@' rather than '@enddate@'.

This will format the stored date as yyyy-mm-dd so it can be compared using < and >.

• 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

Visibility of Custom Fields can also be controlled using:

• Role Field Permissions
• Status Field Permissions
• Show/Hide Field Control

For help constructing logical statements for Visibility Condition:

• Determining the statusid
• Determining the roleid
• Determining the typeid
• Advanced Logic (for more examples)