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.

Introducing PRPC 6.2 - Implementation and Methodology

Updated on June 10, 2020

Direct Capture of Objectives wizards are now "case management aware". Every new application incorporates the potential to support multi-level cases, with structures that can grow and evolve as needed, even during production use.

This topic summarizes a few of the new features.

  • The Application Profiler wizard now supports entry of complex case types. Additionally, you can use either the built-in rich text editor or Microsoft Word to enter and revise use case text. See DCO 6.2 - Creating Application Profiles and Discovery Maps.
  • The Application Document wizard has been redesigned to provide greater flexibility and control over the structure of the output document. You can include attachments, reorder the chapters, preview the document structure before generation, and include or exclude portions of the document easily. The output can include the case tree. Screen capture can occur as a background operation. See DCO 6.2 - Using the Application Document Wizard.
  • The Application Accelerator now supports case structures. You can view and update the case tree as well as the Discovery Map.
  • The Use Case rule form and the use case modal window are redesigned so that you can use Microsoft Word for authoring, an alternative to the rich text editor.

Use Case Form

  • Previous topic Integrating Agile Workbench with an external project management system
  • Next topic Understanding the Class structure and RuleSets generated by the Application Accelerator

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