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.

Integrating Agile Workbench with CA Agile Central

Updated on June 10, 2020

In Pega® Platform 7.3, project stakeholders can use the Agile Workbench tool to capture real-time feedback about an application development project directly in the application. By using the CA Agile Central (Rally) component that is available on Pega Exchange, you can continue to use a real-time Agile methodology and integrate Agile Workbench with CA Agile Central to leverage its project management features, such as real-time release status tracking, customizable dashboards for Scrum or Kanban, and advanced reporting and agile performance metrics.

As a best practice, to integrate with an external project management system such as CA Agile Central, your Pega Platform development operator ID should match your project management system user ID. However, if your IDs for the two systems are not the same, you can provide a different, valid project management user ID for CA Agile Central. On the Operator menu, click Preferences, and update the user ID in the Project management section.

Before you integrate Agile Workbench with CA Agile Central, disconnect any existing integration to a project management system. On the Integration & security tab of the Application rule form, in the Agile Workbench integration section, click Configure integration, and then click Disconnect integration.

To integrate Agile Workbench with CA Agile Central:

  1. Download the CA Agile Central component from Pega Exchange.
  2. In the Designer Studio header, click the name of your current application, and click Definition to open the Application rule form.
  3. On the Definition tab, in the Enabled components section, click Manage components.
  4. Click Install new, select the file that you downloaded from Pega Exchange, and click Open.
  5. Select the Enabled check box to enable this component for your application, and click OK.
  6. In the list of enabled components, verify the CA Agile Central component and its version, and save your changes to the rule form.
  7. Update the PM_CAAgileCentral Authentication Profile instance and populate it with the user ID and password that you will use to access your CA Agile Central system through REST authentication. If you want to use a method of authentication other than Basic, you must delete and re-add the PM_CAAgileCentral instance, using the same name for the new version.
  8. On the Integration & security tab of the Application rule form, in the Agile Workbench integration section, click Configure integration.
  9. Select CA Agile Central.
  10. Provide the API URL for CA Agile Central, and click Connect.
  11. Provide the following additional information about your CA Agile Central system:
    • Project and release – Associate your Agile Workbench work items with a project and release by selecting an existing CA Agile Central project and release, or by creating a project and release.
    • API key – Specify the API key that allows REST integration trusted access to update the API URL that you specified in step 10. You can look up this API key in your CA Agile Central application.
  12. Click Begin integration. All of the user stories and bugs that were created in Agile Workbench are exported to CA Agile Central and associated with the project and release that you specified in step 11. A confirmation message explains the results of the integration process.
  13. Click Done after the integration is complete.
  • Previous topic How to add Entity Relationship diagrams and screenshots to an Application Document
  • Next topic Customizing the CA Agile Central integration component

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