Constellation

 Traditional UI

1. Required deeps skills in Accessibility
2. Customization - CSS & JS broke apps, Upgrade issues. Save-as
3. Performance

Theme-Cosmos

• Templated UX for employee case workers 
• Less “Save-As” (if you stayed with our OOTB design templates) 
• Small improvements in 
• UI upgrades 
• Performance 
• Accessibility 
• Consistency across app portfolio

Constellation UI

• Remove business logic from UI - no action sets
• seamless UI upgrades
• SPA
• Accessibility
• Complete UX system minimizes the development time (ootb)
• Bring your own UI - architecture
• Customization to Configuration

Action sets orchestrates the work to perform on the server, while interacting with an assignment UI

Constellation runs in the browser, orchestrates the work on the server through DX APIs

Debug tools

Redux : Client cache

XRay : LiveUI Inspector

    PCore.getDebugger().toggleXRay(true)

GetState : Same as Redux tool

Pega constellation DX component

1. Install NodeJS
2. npm i @pega/custom-dx-components
3. npx @pega/custom-dx-components@~24.2 init
4. npm run create (To create component)
5. npm run startStorybook
6. npm run buildComponent

 For easier organization and maintenance, you can group components in libraries. The component libraries can be created in different rulesets, which in turn can be used for different applications.

When you publish a component to Pega Infinity™, it creates or updates a Rule-UI-Component instance. This instance is pushed by Pega Infinity to the configured Constellation App Static Service. The Rule-UI-Component instances are exported in a RAP file for deployment to other Pega Infinity environments.When a component is published, a zipped version of the component folder is stored as a Pega Infinity Rule-UI-Component rule instance. Pega Infinity automatically pushes this component zip file to the Constellation App Static Service for access during UI rendering.

The naming convention of the component key is <organization>_<library>_<component

• organization - This value is found in the organization property of the package.json file in your project's root folder.
• library - This value is requested when the component is created and can also be set as default in the tasks.config.json file.
• name - This value is requested when the component is created.

Types of constellation DX components

Field

Allows to configure interactive UI elements such as text boxes, buttons, and sliders.

Widget

Improves usability through built-in logic and functionality. For example, the attachment widget allows users to upload documents.

• PAGE (Portal widgets) - This widget can be used only in landing pages.Example, Todo and App announcements.
• CASE (Utilities pane widgets) - This widget can be used only in case views.
• PAGE & CASE (Both) - This widget can be used in portal landing pages, and the Utilities pane for both case and data views. Example, Pulse

Layout template

Provides layouts for the fields and widgets on a form. Grid, Flex are the basic React components for layouts. Layout templates provide slots called Regions. Authors can add fields, field groups, views, widgets into the regions. 

You can create three types of Constellation DX component layout templates using the Constellation DX Component Builder:

• Details : Applying the Details template renders the child components referenced in the Regions as read-only. Example: Details of Case view and Data type, Partial views use Details template use Details template.
• Form : Forms are designed to efficiently collect data from the users of your application
• Page : Page layout templates control the layout of landing pages. 

https://github.com/pegasystems/constellation-ui-gallery

https://github.com/pegasystems/constellation-ui-gallery/releases

DORA - DevOps Research and Assessment

1. Deployment frequency: 
2. Lead time for changes : The time it takes from code commit to deployment to production.
3. Mean time for recovery:
4. Change failure rate:

Container : Run instances of Docker images. They are isolated environments sharing host OS kernal, ensuring lightweight and consistent execution.

Docker hub : cloud-based registry where docker images are stored and shared publicly or privately

Configuration management with Ansible

Automate infrastructure setup and application configuration

Post-deployment configs, such as setting environment variables or configuring databases.

Monitoring tools

• Prometheus - Metric collection and alerting
• Kibana - Log aggregation and analysis
• Splunk - Operational intelligence and insights
• Grafana - Dashboards for visualizing metrics

• Continuous Integration - Code quality, Unit tests, Dependency
• Continuous Delivery - Pre prod (Manual/Click to deployment to production)
• Continuous Deployment - Deploy to production

Security -Shift left

• Left- Plan, Code, Build, Test
• Right - Release, Deploy and Monior

Data Flow

 Rule-Decision-DDF (Decision Data Flow)

1. Real time data flow
2. Batch data flow

Input

• Abstract - If this Data flow is configured as destination in other Data flow 
• Data set 
• DB Table 
• Report definition - 

Output 

• Abstract - If this Data flow is input to other Data flow
• Data set
• Data flow 
• Case 
• DB table

Processing shapes

• Compose - Combine data from two sources
• Convert - Change the class of incoming data
• Filter
• Data transform
• Merge - Similar to UNION in SQL query
• Strategy
• Text analyzer
• Event strategy

Database class mapping wizard

•  pzCreateTableForClass - Activity to create table in Pega DB, and creates Data-Admin-DB-Table instance.
• Database class mapping wizard - Creates a concrete class and maps to a particular DB table.

• Classes that inherit from Work- should be either be a class group or belongs to a class group

Job schedulers

 - Adv.Agent are grouped together, and access group configured is applied to all agents in the group.

- Adv.Agents use Agent schedules.

- On disabling an instance of System-JobScheduler-Override.

- Jobschedulers offer both perf statistics & run statistics.

Pega Calendar

1. Operator
2. Organization
3. pyCalendar on WorkPage

JVM - GC

 

Application throughput : Time taken to run the application

Major GC run : The number of times the GC run old gen (tenured) space

Minor GC run : The number of times the GC run young gen space

Heap : System allocated memory for JVM to run all applications

Old gen : The space that contains objects which survived multiple GC runs

Young GC: The space that contains objects which are new/short lived (not survived enuf GC runs)

Metaspace: The space that contains the application metadata (classes + methods). Is not part of Heap

Code cache: Cache that contains code which helps JIT compiler

It starts in the young generation (which itself is divided into multiple spaces - Eden and Survivor) and would eventually end up in the tenured generation if it survived long enough.

Adv. Agent

•  Assign the records to be processed a sequential number for the jobID as 1,2,3...10
• Support we have 3 job schedulers, configured with different activities that take batch id as parameter. Agent1 gets parameter value 0, Agent2 value 1 and Agent3 value2.
• Agent activity checks condition Param.batchID==Page.jobID%3

Case management

• Duplicate search cases - pyDuplicateSearchCases activity

pyDuplicateSearchCases parameters pyDuplicateCasesReport, CaseMatch rule. It will copy all the matched cases to pyDuplicateCasesReport pagelist.

• 
  

Approvals

1. Single level - user reference field, reporting mgr, Participant. Work queue/Business logic
2. Cascading 
• Reporting structure - RM, WG Mgr. Approval level is One, All, Custom
• Authority Matrix - Build Pagelist by using decision table.
• Create PageList & decision table D-A-O-I class. Evaluate all rows.
• pxCascadingApproval flow

Pega SLA

 Flow SLA 

1. Pega uses internal process flow (pzInternalProcessFlow) with assignment shape & sla parameter. Pega starts this flow in parallel to the current case flow
2. Creates a new internal assignment (Assign-Internal) and SLA queue item for GOAL time, and System-Queue-ServiceLevel instance which will be process by ServiceLevelEvents agent.

Case SLA

1. Pega starts OverallSLA flow with Assign-Internal assignment.
2. 
   

Stage SLA

1. pzInternalStageFlow with Assign-Internal assignment 

Step Level

1. Assign-.AddAssign

• pxAdjustSLATimes/pxAdjustSLA - This API adjusts the existing goal and deadline times of an assignment.
• DefineSLATimes Work- to add pySLAName on Work.
• 
  

Pega common data model

• 12 Entities (Ex: Common-LDM-Entity-Account)
• 12 case types : case type per each Entity
• Data objects that any of the Entities can use. For example, Address
• Local data storage (Data base tables)
• API layer for the CRUD operations
• Data pages that use connectors
• Data portal for viewing and uploading

• Common-LDM-Relation-Acct_Con direct inherit from Link-Association-M2M (Link-Association)
• SelectContactRelationships property is of type PegaList (of Common-LDM-Relation-Acct_Con)
•