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.

Designing applications for reuse and extension

Updated on April 5, 2022

Save time and speed up your application development process by designing your applications for reuse and extension. When you create reusable elements, such as rules and classes, you can implement them again in future projects, to make your work more efficient.

For example, if you create a rule that defines a service-level agreement, you can include this rule in any future cases that you design. At the same time, you improve the flexibility of your projects because you can select from specific elements that your current business project requires.
  • Naming conventions for records

    Give informative and descriptive names to the records that you create in Pega Platform, such as rules and data instances, to help you manage your resources and provide quick context for other developers. As a result, you speed up application development and promote reuse across your application.

  • Creating a rule

    To save time and ensure that your projects adhere to the unique needs of your clients, create rules and data instances using reusable elements of your application. By combining a rule type, name, class, and ruleset, you provide a unique identity for each rule that you create.

  • Organizing rules

    For an improved management of your application, organize its building elements – rules – in a logical and coherent way. You can group rules into rulesets and classes, so that you can conveniently reuse them during application development. As a result, you reduce development time and costs.

  • Rule resolution

    Rule resolution is the search algorithm that the system uses to find the best or most appropriate rule instance to apply in a situation.

  • Changing the scope of rules

    Adjust your application to your specific business needs by changing scope of rules. For example, you can move a rule to another ruleset or class, so that you can reuse the rule in a different part of your application.

  • Checking out a rule

    To avoid accidental rule changes or conflicts that might result from multiple developers working on the same rule, perform a check out, so that you can lock the rule and safely make changes to it. By checking a rule out before editing, you avoid unwanted rule changes, and as a result save time and maintain a better quality application.

  • Restoring the earlier state of a rule

    During application development, you can undo recent changes to a rule and replace the current rule with a previous copy, even if another developer created the newer copies.

  • Finding deprecated rules in sections

    Find sections that use deprecated rules by using an application upgrade utility. Once found, these legacy rules can be updated to newer rules.

  • Exploring rules in your application

    To ensure that your application includes all the features that your business process requires, explore rules that define these features. By exploring rules before you define new elements of your app, you can also avoid duplicating resources, and as a result, save time and development costs.

  • Delegating a rule or data type

    To delegate a rule or data type to enable your business line to configure simple application logic without involvement from IT, complete the following steps.

  • Importing the legacy ruleset from the Resource Kit

    Applications that require deprecated rules that are no longer included in the Pega Platform distribution need to import those legacy rules from the Resource Kit.

  • Referencing properties

    Provide the data necessary to process your cases by referencing information in the form of properties. When you refer to a property, your application calls a specific piece of information, such as a customer phone number or an address.

  • Branched application development

    Your teams can develop multiple features simultaneously without overwriting work and causing conflicts by implementing branched application development. During branched development, developers can make changes in one ruleset that affect other developers only after you merge the changes into a target ruleset. As a result, you speed up application development and can clearly analyze what changes your application includes.

  • Unit testing individual rules

    An incorrect rule configuration in an application can cause delays in case processing. To avoid configuration errors such as incorrectly routed assignments, unit test individual rules as you develop them. To expedite future rules testing, you can create reusable test cases from the unit test.

  • Managing relevant records and components

    Save time during application development by reusing elements such as relevant records and components.

  • Calculating values and making decisions

    To provide automated solutions for your application users, define automatic was of making decisions and calculating values in your business processes.

  • Calculating or validating values automatically

    To save time and reduce the risk of errors during calculation, provide tools for your application that calculate and validate values in an automatic way.

  • Creating an activity

    Automate a system task for which a more appropriate rule type is not available by creating an activity. With activities, you define a sequential set of instructions, or steps, that the activity completes automatically. Each step calls a method or supported rule type to perform the required processing.

  • Creating binary file rules

    Enhance and customize your application by creating a binary file rule that in a form of a rule stores a graphics file, such as an image, or other non-text files. Binary file rule type provides the security, inheritance versioning, and deployment benefits of rule resolution to a file.

  • Adding images to Image Library

    Customize the look-and-feel of your application by including your own images in elements such as logos, displaying an image for a button or link control, using custom sprites in the UI design, and determining the content that users see when the system displays a guardrail warning. As a result, you provide a unique and personalized application that can precisely reflect your business requirements.

  • Creating a toggle

    To enable or disable functionality that is under development, or to control access to a feature, create a toggle. When you create a toggle, a when rule for the toggle instance is created by default.

  • Optimizing application load time

    You run a preflight optimization to reduce an application’s unnecessary static content and improve its loading time.

  • Previous topic The Microjourney in the Pega Express methodology - frequently asked questions
  • Next topic Naming conventions for records

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