LinkedIn
Copied!

Table of Contents

Designing applications for reuse and extension

Version:

Only available versions of this content are shown in the dropdown

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.
  • 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

  • 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.

  • Branches and branch rulesets

    Typically, you use branches in development environments in which multiple teams contribute to a single application. You use branches to develop software in parallel in a version-controlled environment. For example, your teams can develop one feature in a branch while another team develops a feature in a different branch, even if they share the same base rulesets.

  • 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.

  • Understanding continuous integration and delivery pipelines

    DevOps is a culture of collaboration by development, quality, and operations teams to address issues in their respective areas. To sustain progress and bring continued improvement, tools and processes are put in place. Use DevOps practices such as continuous integration and delivery (CI/CD) pipelines to break down code into pieces and automate testing tasks, so that multiple teams can work on the same features and achieve faster deployment to production.

  • 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

    Create an activity by selecting Activity from the Technical category.

  • 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.

Related Content

Article

Testing your application

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.