A form is a view of your data. The fields on a form store user input that can include single-value fields, a group of values, or a list of values. After you create a form, you can associate it with an assignment or approval step in the life cycle of a case.

The presentation and validation of the fields on a form are determined by the following items:

• The field type, such as Text or Integer, that you select

• The display mode of the field, such as Required, that you select

• The property that stores the value of the field.

  Properties are implicitly created when you add a new field to a form. The property type is determined by the field type that you select when you add a field to a form.

• The validation conditions that you define

• The display mode of an embedded (reused) form, such as Read only, that you select

• harnesses

  Organize the content and structure of a portal by defining harnesses. By populating harnesses with sections, you can build a modular interface that promotes reuse and maintainability.

• Keystores

  A keystore is a file that contains keys and certificates that you use for encryption, authentication, and serving content over HTTPS. In Pega Platform, you create a keystore data instance that points to a keystore file.

• Sections

  Sections are the building blocks of your user interface. You can populate a section with components, such as fields and controls, to create a functional chunk of user interface that can be reused in different contexts for improved consistency and efficient development.

• Layouts

  You can use standard layouts to design the user interface for your application. The standard layouts are rendered in HTML5 standard mode and are styled in the skin of the application, providing an optimal user experience on desktop, tablet, and mobile phone. You can use layouts within a harness or a section while designing the user interface.

• Controls

  Use control rules to determine the appearance of a single property, such as a button or drop-down field, on a form.

• Modal dialog box

  A modal dialog box combines a pop-up window with a flow action, as the front-most screen where the user is working.

• Reusing UI Gallery examples in an application

  Accelerate application development with ready-to-use components from the UI Gallery landing page.

• Applying design templates

  Make your applications consistent and save development time by using design templates. Design templates represent common user interface patterns and specify regions in which you add user interface elements, such as icons and controls.

• Configuring views for cases

  Display relevant information and gather data from users by creating views for cases and associating the views with case types. When you create views, you decide what fields the users see and how they interact with the fields as the case moves towards a resolution.

• Building forms for case types

  You capture user input in a case by building forms. When you create, configure, and organize relevant fields in a form, you can clearly communicate to users the tasks that they need to perform to process an assignment in a case.

• Validating field input

  Ensure that the user input on a form meets the required conditions before the case moves to the next step in the life cycle. By validating field input, you check whether the data values that users enter are valid and whether the system can process the information correctly. For example, you can ensure that the customer provides their name and addr

• Validating character patterns

  Check whether the input that your user provides is relevant. By verifying character patterns with edit validate rules, you can ensure that the data that users enter into forms matches the field requirements, and reduce the number of processing errors.

• Restricting user input in a field

  Configure fields in your data model to change the way that they store or display information to create a robust data model that is tailored to your business requirements.

• Configuring a form at run time

  You can configure forms as you process a case. By incorporating edits in real time, you can develop your application in a dynamic and flexible way.

• Configuring a work area at run time

  You can configure the work area of a form as you process a case. The work area includes the content and widgets, but not the header or navigation areas of the case form.

• Configuring a region at run time

  Forms that are based on design templates have one or more regions. Each region is marked with a name or with a capital letter (A, B, C, and so on, depending on the number of regions). At application run time, each region is displayed with this letter or name at the top. You can configure any region as you process a case. By making changes to regio

• Styling controls at run time

  You can style many types of controls at run time in App Studio, rather than switching to Dev Studio and modifying the application skin. For example, for drop-down controls, you can specify text color, background fill and color, and border width and color. When you style controls directly in App Studio, you can save development time and reduce main

• Configuring a table at run time

  You can edit tables at run time by specifying a visual style, changing the table title, setting the table pagination, adding and removing columns, modifying column titles, resizing and reordering columns, and specifying minimum and maximum column widths. Editing tables at run time provides you with the flexibility to update table layouts as you pr

• Configuring a case at run time

  You can change the design of a case as you are processing it. By incorporating edits in real time, you can drive your application forward in a focused, yet flexible way.

• Supported display modes by field type

  The following table lists the display modes that are supported by each field type. You select a display mode when you add a single-value field to a form. By default, all fields have a display mode set to Optional.

• Enabling spell checking in user forms

  Configuration elements work together to provide users the ability to check spelling in user forms.

• Legacy forms

  A legacy form presents custom HTML and XML to users. Because legacy forms are deprecated, rebuild your forms by using design templates instead.

• Keystores

  A keystore is a file that contains keys and certificates that you use for encryption, authentication, and serving content over HTTPS. In Pega Platform, you create a keystore data instance that points to a keystore file.

• Restrictions on field and form reuse

  You can reference an existing field or form when you build a new form. By reusing components in your application, you save time and avoid duplication.

• Storage and display of fields