Skip to main content

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

Copying response time-out in Pega Sales Automation

Updated on March 19, 2021

After the update, copy the response time-out value from Dev Studio to App Studio. Copy the value manually to preserve any customizations of the setting from your pre-8.7 system.

Pega CRM 8.7 Feature Adoption for Pega Cloud

The update utility does not copy the value of response time-out.

  1. In Dev Studio, type ResponseTimeOut in the search field, and then click on the search icon.
  2. From the search results, select the response time-out application setting that you wish to carry over to your Pega Sales Automation updated to 8.7.
    The ResponseTimeOut tab opens.
    ResponseTimeOut tab in Dev Studio
    Screen capture of the response time-out tab in Dev Studio with example values.
  3. Copy the values for each of the production levels.
  4. In App Studio, go to SettingsConfigurations.
  5. In the Microsoft Integration configuration set, find the Response time out setting, and then click on the gear icon to edit the setting.
    The Configure setting window opens.
    ResponseTimeOut tab in App Studio
    Screen capture of the response time-out tab in App Studio.
  6. In the window, paste the values that you copied in step 3 and click on Submit.
  7. Optional: In the Configure setting window, you can add a value to the Constant per production level field.
    The system uses the Constant per production level value if the particular production fields are left empty.
Result: The response time-out values are copied to your updated Pega Sales Automation 8.7.
  • Previous topic Pega Sales Automation procedures
  • Next topic Lead stages sourced from case life-cycle in Pega Sales Automation

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us