Skip to main content

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

Exploring the application definition

Updated on January 14, 2022

Analyze and edit basic information about your application by exploring the application definition. In the application definition, you can edit what built-on applications your software uses to source elements, manage branched development, and add components to extend the functionality in your application.

  1. In the header of Dev Studio, click the name of the application, and then click Definition.
  2. On the Definition tab, explore and edit the application definition to meet your business needs:
    • To reuse elements and assets from other applications, such as rules or features, explore the Built on applications section.

      For more information, see Adding built-on applications.

    • To expand the functionality of your application by adding components, explore the Enabled components section.

      Components represent reusable features, such as a tool to capture multimedia within an application. You can create your own component or you can use ready-made components that are available on Pega Marketplace.

      For more information, see Installing components.

    • To define the look and feel of your application by applying a skin, explore the Presentation section.

      For more information, see Specifying a skin for your application.

    • To define a URL to launch your application, explore the Application URL alias section.

      For more information, see Adding an application URL alias.

    • To define advanced configurations for your application, explore the Advanced section.

      For more information, see Configuring advanced application settings.

    • To provide separate sandboxes for application developers to avoid conflicts and overrides, explore the Development branches section.

      When you create branches, developers can build and modify rules without interfering with the work of another team that works on the same application.

      For more information, see Branches and branch rulesets.

    • To enrich your application with a specific element, such as assets that are associated with a specific case type or access group, explore the Application rulesets section.

      For more information, see Organizing rules into rulesets.

  • Adding built-on applications

    To save time and reduce development costs you can reuse elements between your applications, such as rules and features, by adding built-on applications. When you build your application stack, you ensure that you meet business requirements in an efficient way.

  • Configuring advanced application settings

    Incorporate advanced options into your application to ensure that the software that you develop meets your unique business requirements. For example, you can define how your application renders the UI, or enable your system to automatically manage background processes.

  • Managing application cases and data

    Explore the application definition to gain a holistic view of data in your application and cases that are available for creation at run time. As a result, you can globally manage resources in your application from one place.

  • Configuring applications for reuse

    To save time and immediately start application development, make your application available as a template. When you save your application as a template, other users can quickly build a new application from that sample. The newly created application automatically inherits template logic, data, and personas.

  • Setting your application password

    Improve your application security by setting an application password, which limits the number of users who can make changes to your application. For extra security, you can periodically update this password based on your security framework and security plan.

  • Specifying the content of application documentation

    Provide guidance and methodology information to developers and other stakeholders by defining which information the application documentation includes. As a result, you can provide relevant details about your software and the methodology that your team implements.

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