Skip to main content


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

Simulating a JSON response in automations

Updated on April 6, 2022

See how an automation presents the content in your JSON response to users by simulating a JSON response in draft mode. Simulating the JSON response provides you with an opportunity to test the automation output and update the sample data as needed.

Before you begin: Configure an automation with a JSON response. For more information, see Configuring validation for text inputs and outputs in automations.
  1. Create a new automation or open an existing automation.
    ChoicesActions
    Create a new automationFollow the steps in Creating an automation.
    Open an existing automation
    1. In the navigation pane of Dev Studio, click Records.
    2. Expand the Technical category and click Activity.
    3. Locate the automation for which you want to simulate a JSON response and click in its row.
      Automations have the activity type AUTOMATION.
    4. Click ActionsEnter draft mode.
  2. Click the Implementation tab.
  3. On the output for which you configured a JSON response, click Show JSON Sample.
    Result: The sample JSON response is displayed in a separate window. The system generates the response based on the .yaml file that you configured for the output on the Definition tab.
  4. Optional: Modify the JSON sample in the Sample data section.
  5. Optional: To revert your changes to the sample data contained in the original .yaml file, click Re-populate from yaml file.
  6. Click Save.

Tags

Pega Platform 8.7 Data Integration

Have a question? Get answers now.

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

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

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