Skip to main content

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

Creating a specification

Updated on January 14, 2022

Defining and creating specifications for an application is an iterative process that requires input from all stakeholders. If the information about a specification is detailed and up-to-date, the specification is more useful during the application development process.

Note: To take advantage of the latest Pega Platform tools, use features instead of specifications. For more information, see Adopting feature-driven development.

You can associate a specification with one or more rules that implement it. For example, a single specification can correspond to an entire process, a single step in a flow, and an alternate path.

  1. Access specifications from one of the following locations in Dev Studio:
    • From the Dev Studio menu, click ConfigureApplicationProfileSpecifications.
    • From the Application Overview landing page, click the Specifications link in the Details section.
    • On the Settings tab of a case type that you open from the Case Type Explorer, click Specifications.

      The value displayed next to the Specifications option shows the number of case-wide specifications that are defined.

    Result: Any specifications that are currently defined for the application or case are listed. You can filter the list of specifications based on case type and supporting case type, type of rule that the specification corresponds to, status, complexity, release, and iteration. You can also filter by searching for keywords in the specification name and description.
  2. Click Create specification to open the Add/Edit Specification modal dialog and specify the following information:
    • The name of the application
    • The case type or supporting case type
    • The Ruleset and Ruleset version
  3. On the Details tab of the rule form, specify additional information, such as a short description and detailed description of the specification, the status and complexity of its implementation, the type of rule it corresponds to, the target release and iteration, the primary business objective that it supports, and its business impact.
  4. In the Attachment section, add attachments (files and URLs) that provide more information about the specification.
  5. In the Advanced section, specify more information about the specification, including the actors and subject matter experts involved, requirements associated to the specification, and conditions for the successful implementation of the specification.
  6. On the Implementations tab, view, add, or remove the rules that correspond to, or link to, the specification.

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