Glossary:Autopopulated property
- auto-populated property, autopopulated property, APP
- A Page or Page List property that automatically obtains data directly from a specified data page. The values can be an entire object from the PegaRULES database or copies of pages developed by a Data Page rule. To enable autopopulation for a Page mode or Page List property, configure the Data Access fields on the General tab of the Property form.
A Page or Page List property that automatically obtains data directly from a specified data page. The values can be an entire object from the PegaRULES database or copies of pages developed by a Data Page rule. To enable autopopulation for a Page mode or Page List property, configure the Data Access fields on the General tab of the Property form.
A Page or Page List property that automatically obtains data directly from a specified data page. The values can be an entire object from the PegaRULES database or copies of pages developed by a Data Page rule. To enable autopopulation for a Page mode or Page List property, configure the Data Access fields on the General tab of the Property form.
A Page or Page List property that automatically obtains data directly from a specified data page. The values can be an entire object from the PegaRULES database or copies of pages developed by a Data Page rule. To enable autopopulation for a Page mode or Page List property, configure the Data Access fields on the General tab of the Property form.
An entity that you use to cache data on demand to a clipboard page for use by one or more applications. A data page rule defines the source, scope, refresh strategy, editability, and structure of the cached data. Data pages were previously known as declare pages.
A relational database that holds the rules, data instances, work items, history, and other concrete objects from the internal classes of the Pega Platform system. External classes are not part of the PegaRULES database.
An entity that you use to cache data on demand to a clipboard page for use by one or more applications. A data page rule defines the source, scope, refresh strategy, editability, and structure of the cached data. Data pages were previously known as declare pages.
The basic building blocks of an application, rules define the behavior of an application. There are many types of rules, each defining a different type of behavior. For example, rules define the display of a form, the fields that are used in your application, and the flows that define the process of completing work.
The system can reuse rules throughout your application. For example, in an application for ordering replacements parts, you can define a user interface to capture an address, and reuse the same rule for the UI to capture both the mailing address and the billing address for the order.
You define rules in an application to create a business solution for your organization and customers. Rules provide flexibility during the development process and help you design applications more efficiently, so that they can be implemented again in future projects.
A data structure that holds name-value pairs. Pages are stored in the system memory or in the database. Various types of pages are defined in the system, such as data pages that are created when the data is referenced, named and unnamed pages, parameter pages, clipboard pages, and so on. Every unit of information in an application is a pairing of a name and a value, known as a data element. For example, a data element that stores the email address of a customer has the name "email," and the value "john.smith@company.com." Pages store data elements so that the application can use it to process the case.
An entity that models data in your business processes and defines what information you need to provide to reach your business goal. For example, in a process of hiring new employees, you can create properties that correspond to the personal details of a candidate, such as a name, a surname, and an address. Then, when you review applications from different candidates, you provide values specific to each candidate. To save time and make your application more relevant to customers, you can reference properties in different elements of your application, and then populate them with data at run time. For example, you can include a property that references a customer name in an email that your application sends automatically. As a result, each time that the email message is personalized and includes an actual customer name. Properties help you collect and provide consistent data irrespectively of the method in which users interact with your application. By referencing properties, you ensure that a user receives the same information through a website, an email, or a mobile app.
A view of your data that displays information or collects input from users as they create, update, and resolve cases in your application. Open your case type from the Application Explorer to access the options for configuring a form.