@RituK17288411  In Pega while creating a new application especially for an Organization layer not all rules need to be created manually. Pega's low code approach allows for automated rule creation particularly in App Studio. For instance when you configure a Case Type in App Studio the platform automatically generates the necessary underlying rules in Dev Studio. This includes rules related to access roles data types and application layers. To create a new Org layer application you can start by using an existing application template which helps in reusing key elements like Case Types. You can invite collaborators to enhance the application and configure advanced settings to align with your organizational needs. This modular approach not only saves time but also ensures that the application is tailored to specific business requirements.

⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.

Building your first application

Rules in Pega applications

@RituK17288411

Pega's new recommendation is to build Modules that can be reused across Applications. 

A Module-centric design pattern, or 'Modular' Situational Layer Cake, is the optimal way to organize reusable low code assets across the enterprise.

In this design pattern, the enterprise layer is very lightweight, only holding common assets that are applicable across the enterprise, such as UI styling, security, and authentication features.

Instead, Modules contain the majority of the reusable capabilities, which are focused on the needs of a business entity, on system integration, or on utility.

Please go through this Academy course for more details(along with real time example) - https://academy.pega.com/module/modular-enterprise-reuse/v1/in/53381