Collecting data

In a case type, the Data model contains the list of fields that collect and retain information relevant to the case. To access the data model, Ren performs the following steps:

1. In the navigation pane of App Studio, click Case types, and then click the Content Request case type.
2. Select the Data model tab.

Next, Ren adds fields to the data model.

In Pega Platform™, each field corresponds to a data element that stores a single value associated with a specific case. Fields fall into two basic categories: system fields and custom fields.

System fields

System fields are automatically generated by Pega Platform™.  System fields are standard with the Pega Platform and appear as choices for every case type. Examples of system fields are Case ID, Create Date/Time, and Create operator name. To view the system fields associated with a case type do the following:

1. In the Data model, click the Show system fields checkbox.

Custom fields

Custom fields are fields that are unique to the application or case type. Custom fields are created by clicking the Add field button in the Data model view.

Clicking the Add Field button opens a modal window with text entry boxes for Field name and a Type.

Each Field name is entered in a text box. Field names should be short and descriptive.

The field Type identifies the type of information stored in the system for the data element. By assigning a field type, a developer ensures that users provide valid data for that field and that the system displays the data in the correct format.

Some of Pega’s field types include:

• Text (single line) – A single line of text.
• Text (paragraph) – A large text box that accepts multiple lines of text.
• Email – A text box that validates the format for an @ symbol.
• Picklist – A short, predefined set of values.
• Attachment – Adding a document or file to a case.

Based on the idea process flow, the custom fields required by the Content Request case type are as follows:

In Pega Platform, fields that are important to a case can be designated as Primary. Fields with a Primary designation are automatically included on certain case views to reduce the amount of UI configuration necessary.

Pega automatically designates the Label and Description fields as Primary. Makers can designate additional Primary fields by performing the following steps:

1. In the Data model view, click the Primary fields button.
2. In the Primary field configuration window, click the + Add button.
3. Click the check box next to the field name(s) of those fields to be designated as Primary.
4. Click Add.
5. Fields can be removed from the Primary field configuration list by click the trash icon associated with the field name.
6. Click Submit.

Ren designates the Request details and Request type fields as Primary. Ren removes the Description field from the Primary field configuration list.

Review the following video to see Ren add the fields to the Content Request data model:

Pega Platform offers many additional field types beyond those that Ren uses in this application. They include:

• Integer: Allows input of positive and negative whole numbers including the value zero (0).
• Currency: Allows for input of an amount. Currency symbol and decimal places based on localized format.
• Date only: The calendar date displayed in a localized format.
• Phone: Digits of a phone number displayed in a localized format.

For more information on the different field types that are available in Pega Platform, see the Pega Academy topic Fields.

In Pega Platform applications, a view is what the end-user sees when they access the live application. A form is a view that collects information that is to be retained in order to process a case.

Once the relevant fields have been added to the data model, Ren can configure the form for each step that requires information to be collected and retained.

Ren completes the following steps create the form for the Enter request details step:

1. In the navigation pane of App Studio, click Case types, and then click the Content Request case type.
2. Select the Workflow tab.
3. Click on the Enter request details step to open the contextual properties pane.
4. Click the Configure View button.
5. Click the + Add button located under the Fields section.
6. Open the Fields dropdown menu.
7. Click the checkbox for each field that is being added to the view/form.
8. Click Add.
9. Click Submit.
10. Click Save.

Ren adds the following fields to the Enter request details form:

• Create operator name
• Requester email
• Requester department

Now that fields have been added to the Enter request details form, Ren is able to update fields for characteristics such as Edit mode and Required. Users must input data into required fields before a form can be submitted. By updating Edit mode, a field can be designated as Read-only.

To characterize the Requester email field as Required, Ren complete the following steps:

1. In the view, Enter request details form, click the gear icon located on the right side of the Requester email row.
2. Scroll down to the Conditions section.
3. In the Required box, click the dropdown arrow and select Always.
4. Click Save to close the Edit field window.

Ren follows similar steps to update the Create operator name field’s Edit mode to Read-only.

In the following figure, slide the center vertical line to compare the Enter request details form's configuration view with the Enter request details view that is displayed to the requester in the Web portal:

In your own Pega environment, add fields to your data model and then create forms in each Collect information step.

Be sure to designate fields that are important to the case as Primary in the data model. In the form, fields that must have data entered should be designated as Required.

You can recreate the fields that Ren added to his application or add fields that are necessary to collect data for your own process.