Data Object
What is reuse layer and difference between Enterprises and implementation?
Pegasystems Inc.
US
When choosing "Enterprise" reuse layer, the Application Express creates a framework application that you can extend for reuse elsewhere in the organization. For example, you may want to extend the application for use in other regional offices. In the SAE I course, we choose "implementation" to keep the class structure in this course more "basic" because the SAE I course concentrates on basic core Pega 7 application functionality (case implementation and processing), not application class structure inheritance and design patterns. Design patterns and best practices are discussed further in the SAE II course.
NOTE: Please keep in mind that the Application Express tool is infrequently put to use, perhaps only once per major release, to create a new baseline application structure. Often the baseline structure already exists and so we just add to that structure (all the other exercises in SAE I). In addition, the primary user of this tool would be a certificed Lead or Senior System Architect. Those individuals should be intimately aware of the already existing Pega 7 class structure they are adding this new application structure to. We're just using the App Express quickly in this SAE I course to create a baseline application structure for POC purposes..
I hope this helps.
Kind regards,
Bob Lloyd
Pega Academy Self-study Support Team
Pegasystems Inc.
US
Select an option to set who can access the pages loaded by this data page record:
Select an option to set who can access the pages loaded by this data page record:
Node— Any requestor executing on the current node can access the pages. For example a group of loan processors share a page of current interest rates.Thread— The page is created in a single requestor Thread, and can be accessed as often as needed by processing in that Thread. Later accesses on another threadcause the data page to load a distinct page which may have different contents, even if it is by the same requestor. My example here is using the same page for any type of loan i.e. Auto, Home, or Personal.Requestor— The requestor can access the page(s) loaded across all threads. Accesses by separate requestors create distinct pages which may have different contents. This page is only avilable to a specific case i.e. One Loan Case.
Read / Write pages all have Thread or Requestior scope.
Pegasystems Inc.
US
I placed a pratical example in the above post.
Node: A group of loan agents sharing a page for current interest rates.
Thread: A single agent using the same page no matter what loan type is being used Auto, Home, Personal Loan.
Requestor: This page is used for only one Loan Type or Case Type.