Defining display settings of fields and elements

You can define the display properties of field and elements displayed on a content form. Different field and element types will have different display properties.

  1. To hide an entire section in a content form from all users, select Hide Section. You must specify a default value in any required fields within the section to use this option.
  2. Click properties to open the display properties of a field or element. The following field properties can be set. Different field and element types will have different display properties.
    1. To display a field or element as a required field select Identify this as a required field. Users must complete this field or element.
    2. To hide a field on the content form from all users select Hide field. You must specify a default value if the field is a required field.
      Note: Administrators and managers can choose to display hidden fields and elements in a content item by clicking Show hidden fields.
    3. Type the number of pixels to use in Field Width to set the size of the displayed field. If you leave this blank, the default field size will be used.
    4. Type a number into the maximum or minimum characters or words fields to set limits on the number of characters or words a user can enter in a field.
    5. To change the label of a field or element, enter a name Field label.
    6. Type field specific help into Field help text. This displays above the field or element in the content form.
    7. The content of some fields can automatically be generated, such as the Name and Display title fields by selecting Generate. If selected, the field will no longer be editable.
      • When selected in the Name field, a numerical name will automatically be generated.
      • When selected in other fields you also select the field or element to use to generate the content of the field, as well as other options such as field size.
    8. Select the users or groups you want to grant edit access to a field or element by clicking Select Editors.
    9. Select the users or groups you want to grant view access to a field or element by clicking Select Viewers.
    10. You can restrict the range of dates and times that users can select in date and time fields by selecting a start and end date or time. You either select a specific date, or select the number of days, hours or minutes after the creation date to begin the range, or the number of days, hours or minutes after the start date to end the range.
    11. You restrict the items available to be selected on fields such as "Select Categories" or "Select Workflows" by selecting the items you want a user to select from. You can also restrict a user to select a single item.
    12. You can restrict the maximum and minimum sizes of files added to a file resource element. You can also restrict the mime type of files that can be added to file resource elements. You add multiple mime types separated by a space.
    13. A "custom JSP" field is available on some element types. You use this to reference a JSP file to use instead of the element's default view in the user interface. You can write JSP to control the look and feel of an element, and to restrict the values that can be entered into an element.

      The JSP page must be stored in the WAR file directory for the Authoring portlet.

      The JSP page may also need to be stored in the client war directory of the servlet or portlet that calls the JSP, such as when using the authoring tool element, or if using the Web Content Management API. For example, if displaying custom fields in content that is opened using the edit button on an authoring tool, you would need to also save the custom field JSP in the WAR file directory for the local rendering portlet.

    14. You can edit the default behavior of rich text elements.
      Use stylesheet, hide fonts/size/color
      Select this option if you want the text style to be determined by a style sheet. Content creators will not be able to edit text properties such as fonts style, text size and text color.
      Limit image picker to library images
      Select this to prevent content creators from inserting images from the file system. They will only be able to select images stored as image components.
      Disable source mode
      Select this to prevent content creators from viewing the rich text editor in source mode.
      Filter active content on save
      Select this to prevent users from saving active content, such as scripts, in the rich text element.
    15. You can also select to use either the default rich text editor of the authoring portlet, or a third-party rich text editor as the rich text editor for a rich text element:
      Portlet default editor
      If selected, this will use the default rich text editor of the current authoring portlet. If the default editor is not available, the standard rich text editor will be used.
      Custom

      Selecting Custom allows you to use a 3rd-party rich text editor as your default editor. Before using a compatible third-party rich text editor, you should read the installation and configuration instructions of the third-party rich text editor. These should include instructions for enabling the third-party rich text editor to be used in a Web Content Management solution.

      When configuring a third-party rich text editor, you will need to copy a JSP file supplied by the third-party rich text editor. This will be used to launch the third-party rich text editor. You enter the name of this JSP file in the Rich Text Options section of the authoring portlet configuration.

      If the third-party rich text editor is not available, the default rich text editor of the authoring portlet will be used. If the default editor is not available, the standard rich text editor will be used.

      Note: Storing JSP Files

      JSP files can be located:

      • within the was_profile_root/installedApps/node-name/wcm.ear/ilwwcm.war directory of your server.

        The JSP page is also stored in the client war directory of the local rendering portlet or of the servlet or portlet that calls the JSP, if using the Web Content Management API. For example, to render a JSP page on a local rendering portlet, you would also need to store a copy of the JSP file under was_profile_root/installedApps/node-name/PA_WCMLocalRendering.ear/ilwwcm-localrende.war

      • within any other Web application running on portal. When referencing JSP files in another Web application, use the following path: contextPath;jspPath

        For example: /wps/customapplication;/jsp/editor.jsp

  3. Click Done to close the properties view.
Note: Using the reset and apply button.

When editing display properties, click the Reset button to return the display properties to the values entered the last time the authoring template was saved.

Click Apply to apply values entered in the properties fields. For example, apply the width of the field to the value entered in "field width" field.