Skip to main content


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

Setting up a connection to a development system

Updated on July 1, 2021

User: System Administrator

Pega Agile Studio Implementation Guide
Note: You can skip this step if your development system is not built on Pega Platform or if you are not planning to connect to a system.

You can establish a connection between Agile Studio and one or more Pega Platform development systems built on Versions Pega 8.8.

This connection allows users to create, view, and update user stories and bugs within the Agile Workbench feature of their Pega Platform development system and allows developers to associate rule changes with their Agile Studio user stories and bugs.

All connection setup tasks are performed in your development system. Repeat the setup process in each development system where you are planning to track and monitor project work. For information on connecting a Pega Platform development system to Agile Studio from the Integration & security tab of your application, see Integrating Agile Workbench with Pega Agile Studio.

For information on connecting development systems on earlier versions of Pega Platform to Agile Studio, see Working with Development Systems on Previous Pega Platform Releases on the Agile Studio product page.

Agile Studio to Pega Platform integration provides an operator for authentication. For the SOAP Services, this operator ID is PM_ SOAPOper and for REST it is AS_RESTOper. For added security, before you put Agile Studio into production, you may want to change the password on this operator ID in Agile Studio and in the authentication profiles in the development environment. The authentication profile used by SOAP is PM_Integration_AuthProfile and REST uses PM_AgileStudio_AuthProfile. To enable an OAuth 2.0 connection for the REST connections, add a client registration data instance and update the service package as specified in Accessing the Pega API by using OAuth2.0.

On the Pega development side, create an OAuth provider and delete and recreate the PM_AgileStudio_AuthProfile Authentication Profile as specified in Accessing protected API resources by using OAuth 2.0.

Note: Before a developer starts the integration with workbench, update the User ID field present in the Project Management section under the operator preferences to use AS_RESTOper.

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