Hiding automated components

When you create most automated components, you can hide them under varying conditions. Use the Hide When tab located on many Properties boxes to specify when to hide it.

  • Hide from Notes® R4.6 or later

    Hides a component when it is viewed from a Notes workstation. This is useful for hiding components such as action bar buttons that you provide to Web users as substitutes for Notes menu choices.

  • Hide from Web browsers

    Hides a component when it is viewed from a Web browser. This is useful for hiding components that aren't relevant to Web users.

  • Hide from Mobile

    Hides a component when it is viewed by a mobile user.

  • Hide when opened for reading; Hide when previewed for reading

    Hides a component when a document is opened in Read mode. These options are useful for components that are relevant only to new documents or documents in Edit mode -- for example, actions that modify a field.

  • Hide when previewed for editing; Hide when opened for editing

    Hides a component when a document is opened in Edit mode. These are useful for components that are relevant only to completed documents -- for example, moving documents to another database, creating response documents, or marking documents as unread.

  • Hide when printed

    Hides the component when users print a document. This is useful for removing clutter from a printed document.

  • Hide when copied to the clipboard

    Hides the contents of the component when users copy a document.

    Note: If you create or save a document from a form that contains a field with "Hide when copied to the clipboard" checked and then copy the contents of the document somewhere else, the contents of that field will not be pasted.
  • Hide if formula is true

    Hides the component under certain conditions -- for example, based on user name or access level in the access control list. For example, the following formula hides the component from all users except Barbara Meehan:

    @Name([CN];@UserName) !="Barbara Meehan"

    However, it might be better to test against roles rather than to hardcode names. This example hides the component from everyone without the Approver role:

    !(@IsMember(@UserRoles; "[Approver]"))