Skip to main content


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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Configuring the JSON data transforms settings column on the Data Transform form

Updated on April 5, 2022

Pega Platform displays the Settings tab on the data transform rule form for the JSON data model format. Use the Settings tab to enable multidimensional array output and to specify fields to skip during auto-mapping. You might want to skip fields that do not have meaning outside of Pega Platform, such as pyObjClass.

Before you begin: Create a data transform with a JSON data model format. For more information, see Configuring data transform.
  1. In the data transform that you create, click the Settings tab.
  2. To enable multidimensional array output, select the Enable multidimensional array output check box.
    Select this option when auto-mapping is enabled on the Definition tab and you have a Page List property with only one non-skipped property that has the same name as its parent. If you enable multidimensional array output, the Page List property will result in a multidimensional array in the JSON output. If you do not select the Enable multidimensional array output check box, the Page List property is displayed as an array of objects.
    For example:
    Multidimensional array option enabled
    Clipboard page                                          Resulting JSON
            .pxResults(1)                                          {
             .pxResults(1)                                          pxResults: [[{
             .Name = “John Smith”                                    Name: “John Smith”
                                                                    }]]            
                                                                   }

    In this example, the pxResults field in the JSON output has two array characters, denoting the output as an array of arrays.

    Multidimensional array option disabled
    Clipboard page                                          Resulting JSON
            .pxResults(1)                                          {
             .pxResults(1)                                          pxResults: [{
             .Name = “John Smith”                                    pxResults: [{
                                                                    Name: “John Smith”
                                                                   }]
                                                                  }]
                                                                 }

    In this example, the output is an array of objects, in which each element has a pxResults field.

  3. In the Date format for serialization field, select the output format to use when serializing a data page:
    • When you select Pega API, the system formats the output as:

      Date: 1996-07-26

      Date Time: 1996-07-26T09:30:00.000Z

      Time of Day: 09:30:00.000Z

    • When you select Pega Internal, the system formats the output as:

      Date: 19960726

      Date Time: 19960726T093000.000 GMT

      Time of Day: 093000

  4. "> To specify which fields to skip processing during auto-mapping, in the Fields to skip when auto-mapping section, click Add field to add a field to the list.
  5. To specify the default auto-map empty behavior, select an empty behavior in the Default Automap Empty Behavior field.
    Note: Select this option when the Auto-map all data check box is selected on the Definition tab.
  • Previous topic Data Transform form - When, Otherwise, and Otherwise When actions
  • Next topic Data Transform form - Completing the Pages & Classes tab

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