2: Authentication

Here I have decided to make a few episodes by designing a case type for Evictions. I cover the high-level business process of an eviction as it is currently, and how we can design an application to replace it. In future episodes we will get deeper into the implementation and build.

I recently joined a new project and noticed some flaws in the data design, specifically around the non-use of declare indexes. I discuss their uses and value in this episode. Not enough Pega developers know how to properly use a declare index, if at all. Please listen in, this has some very valuable information for all skill levels and can really help advance your career skills.

In this episode we go over the LSA Application Build retired exam 1. It is the Wager Application. This problem asks for a high-level design with class / case / data structures for solving it. Listen in on my approach to design a solution. Message me on LinkedIn with any feedback. Link for retired exam 1: https://community1.pega.com/community/lead-system-architects/question/73-74-lsa-architecture-application-build-exam-retired-exam

I cover the idea of authentication and how it is handled within Pega PRPC. Discuss things like authentication types, prweb.xml file, authentication service rules, security policies, SSO and more.

A brief technical overview of what I believe to be some of the main concepts in Pega PRPC. I will cover from a high-level what is Pega, how it stores data, what form its stored in, what happens behind the scenes and some common Pega terms and their equivalents in general computer science/software engineering language.