Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Adding fields while creating cases in DX API v1

Updated on August 5, 2022

Define the initial fields that users see when they create new cases in your Pega Digital Experience (DX) API-based application by editing the appropriate harness in Pega Platform. For example, you can specify that new loan cases include fields that capture account details.

Note: To enable field-level security for case creation, ensure that you have the pxCreateCaseDX privilege. For more information, see Additional privileges in Security Settings for DX API.
In the New harness that applies to new case forms, the controls and sections determine the starting fields for cases in your external application.
  1. Expand the User Interface category, and then click Harness.
  2. Search for and open the New harness that applies to the Work- class.
    See the following figure for reference:
    The harness that contains sections with starting fields
  3. In the harness, click the section to which you want to add fields, and then click the View properties icon.
  4. In the Panel properties dialog box, next to the section name, click the Open icon.
  5. On the section form, on the Design tab, add the fields that you require.
    Note: You can retrieve the list of available starting fields by using the GET /casetypes/{ID} endpoint.
    For example: For a new loan case, in the Structural list, drag a dynamic layout to the section, and then add fields such as Text input and Currency to capture the account details of your customer.
  6. Save the section.
Result: The controls that you added to the section are now the starting fields in any new case.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us