Pega is a platform for digital process automation, customer engagement, and operational excellence. It allows users to develop applications, implement mobility features, manage case lifecycles, and perform extensive user interface design. Pega is preferred over other tools due to its ability to eliminate coding and simplify processes using inbuilt functionalities. The document discusses various Pega concepts like workspaces, classes, activities, debugging tools, and certifications. It also covers new features introduced in Pega 8.4 and differences between key concepts like pages and properties.
User Stories vs. Use Cases
● User Stories
● Определение User Story
● Структура пользовательской истории
● Принципы проверки на качество User Story
● Use Cases
● Определение Use Cases
● Структура Use Cases
● Принципы составления Use Cases
What is an Application programming interface(API)?Akmal Ali
An application programming interface (API) is a set of subroutine definitions and communication protocols for building software. APIs make it easier for developers to use certain technologies by abstracting implementation details and only exposing necessary objects and actions. The term API was first used in 1968. APIs are used for libraries, frameworks, operating systems, remote access, web services, and design. They allow modular programming by hiding complex implementation details from users. Common examples of APIs include OpenGL, OpenMP, DirectX, and Java APIs.
SOLID Design Principles applied in JavaIonut Bilica
Video: https://www.youtube.com/watch?v=0cU-4LrcWI0
SOLID Design Principles applied in Java: rules to develop scalable and easily maintainable code
Speaker: Ionut Bilica - Senior Software Developer @ Luxoft Romania.
During this talk we will discuss about the SOLID Principles described by Robert C. Martin, applying them in the Java programming language. Each principle will be explained in detail, with practical Java examples.
We will asses how these principles make it easy to develop the software for the entire duration of the project, and how some problems can appear if these principles are not applied. We will present common code fragments that do not respect these principles, and we'll see how we can correct them. Taking the SOLID principles into consideration, we will also analyse a real Java project using a Static Code Analyzer tool (e.g. STAN).
Finally, we will discuss the strategies on how to apply these design principles in "greenfield" projects, as well as "legacy" projects, while offering some tips and tricks.
The document discusses demystifying APIs. It begins with an introduction to APIs, including their evolution and benefits. It then discusses RESTful APIs and their key aspects like uniform interface and use of HTTP methods. The document outlines best practices for API design, development, and challenges. It provides examples of designing APIs using Node.js and Hapi.js and discusses challenges like security, authentication, rate limiting, and scalability. Tools mentioned include Express, Swagger, Postman, and Kong.
Simple REST-API overview for developers. An newer version is here: https://www.slideshare.net/patricksavalle/super-simple-introduction-to-restapis-2nd-version-127968966
Learn how to set up an end-to-end testing framework Cypress Automation Testing Tutorial in an angular app. Also, visit the Github code to set up the project.
Testing web services is very important part of integration testing on web projects.
In this presentation you can learn the best approaches, tools and features of Web Services testing. Soon I'll share url with a video from my presentation.
User Stories vs. Use Cases
● User Stories
● Определение User Story
● Структура пользовательской истории
● Принципы проверки на качество User Story
● Use Cases
● Определение Use Cases
● Структура Use Cases
● Принципы составления Use Cases
What is an Application programming interface(API)?Akmal Ali
An application programming interface (API) is a set of subroutine definitions and communication protocols for building software. APIs make it easier for developers to use certain technologies by abstracting implementation details and only exposing necessary objects and actions. The term API was first used in 1968. APIs are used for libraries, frameworks, operating systems, remote access, web services, and design. They allow modular programming by hiding complex implementation details from users. Common examples of APIs include OpenGL, OpenMP, DirectX, and Java APIs.
SOLID Design Principles applied in JavaIonut Bilica
Video: https://www.youtube.com/watch?v=0cU-4LrcWI0
SOLID Design Principles applied in Java: rules to develop scalable and easily maintainable code
Speaker: Ionut Bilica - Senior Software Developer @ Luxoft Romania.
During this talk we will discuss about the SOLID Principles described by Robert C. Martin, applying them in the Java programming language. Each principle will be explained in detail, with practical Java examples.
We will asses how these principles make it easy to develop the software for the entire duration of the project, and how some problems can appear if these principles are not applied. We will present common code fragments that do not respect these principles, and we'll see how we can correct them. Taking the SOLID principles into consideration, we will also analyse a real Java project using a Static Code Analyzer tool (e.g. STAN).
Finally, we will discuss the strategies on how to apply these design principles in "greenfield" projects, as well as "legacy" projects, while offering some tips and tricks.
The document discusses demystifying APIs. It begins with an introduction to APIs, including their evolution and benefits. It then discusses RESTful APIs and their key aspects like uniform interface and use of HTTP methods. The document outlines best practices for API design, development, and challenges. It provides examples of designing APIs using Node.js and Hapi.js and discusses challenges like security, authentication, rate limiting, and scalability. Tools mentioned include Express, Swagger, Postman, and Kong.
Simple REST-API overview for developers. An newer version is here: https://www.slideshare.net/patricksavalle/super-simple-introduction-to-restapis-2nd-version-127968966
Learn how to set up an end-to-end testing framework Cypress Automation Testing Tutorial in an angular app. Also, visit the Github code to set up the project.
Testing web services is very important part of integration testing on web projects.
In this presentation you can learn the best approaches, tools and features of Web Services testing. Soon I'll share url with a video from my presentation.
Swagger is a specification and complete framework implementation for describing, producing, consuming, and visualizing RESTful web services. The overarching goal of Swagger is to enable client and documentation systems to update at the same pace as the server. The documentation of methods, parameters, and models are tightly integrated into the server code, allowing APIs to always stay in sync. With Swagger, deploying managing, and using powerful APIs has never been easier.
An API is a set of routines, protocols, and tools that allow software applications to communicate with each other. It defines the functionality that is independent of implementation. An API expresses the operations, inputs, outputs, and types of a software component. It allows creation of applications that can access features or data from an operating system, application, or other service. An API acts as an intermediary that allows two applications to communicate, delivering requests from one app to a provider and returning the response.
JPA and Hibernate are specifications and frameworks for object-relational mapping (ORM) in Java. JPA is a specification for ORM that is vendor-neutral, while Hibernate is an open-source implementation of JPA. Both use annotations to map Java classes to database tables. JPA queries use JPAQL while Hibernate supports both JPAQL and its own HQL. Additional features covered include relationships, inheritance mapping strategies, custom types, and querying.
The document provides an introduction and overview of APIs, REST, and OpenAPI specification. It discusses key concepts like resources, HTTP verbs, and OpenAPI structure. It also demonstrates OpenAPI syntax using JSON and YAML examples and highlights best practices for documenting APIs with OpenAPI.
Swagger is a simple yet powerful representation of your RESTful API. With the largest ecosystem of API tooling on the planet, thousands of developers are supporting Swagger in almost every modern programming language and deployment environment. With a Swagger-enabled API, you get interactive documentation, client SDK generation and discoverability.
This document describes a hybrid automation framework built with Java using Selenium. The framework uses a combination of data-driven and keyword-driven approaches. It utilizes tools like Log4j, POI Excel files, TestNG, and Maven. The framework architecture includes modules for controllers, tests, data, object repositories, reports, logs, and exception handling. Test cases and test suites are defined and stored in Excel files. The framework execution flow is depicted in a diagram.
The document introduces Oracle's RAD (Rapid Application Development) Stack, which provides a full-stack solution for developing data-driven business applications. The RAD Stack consists of Oracle REST Data Services (ORDS) for building REST APIs, APEX for low-code application development, and Oracle Database for data storage and SQL. It notes the benefits of the stack being easy to use, robust, fully supported by Oracle, and allowing both simple and sophisticated applications to be built.
The API-first design approach treats APIs as first-class citizens. The entire system or project is built around the idea that components connect via APIs. The first step is, therefore, to design the APIs and their connections.
However, there is a gap between the beautiful world of API specifications and the reality of agile development. This gap means that published API specifications are often incomplete, missing examples or simply outdated. The API specification meant to help developers can be a thorn in one’s side because keeping the specification in sync with its implementation is a manual process, tedious and prone to be forgotten during the rush to deliver.
We show how this gap can be bridged effectively using the API specification as the only source of truth driving the API implementation with proven tools enabling automation.
This document provides an overview of a RESTful JSON API. It discusses that the API uses a REST design with JSON as the output format. It also describes other common protocols like SOAP and XML-RPC. The API is intended for use by desktop, mobile, and third-party web applications that can communicate over HTTP. Key aspects covered include input-output design, error handling, documentation, and user authentication using OAuth. The API implementation leverages the Sinatra framework with common logic modules to share data and configuration across applications. SDKs are also discussed to help integrate external apps with the API.
Swagger UI enables generating documentation for RESTful APIs that is updated as the server code changes. It works with Spring Boot by adding dependencies, a configuration file, and annotations. This exposes API endpoints in the browser for testing and provides descriptive documentation of each service's title, function, inputs, and outputs.
This document provides guidance on how to write effective test cases. It discusses test case components like objectives, preconditions, steps, and expected results. It emphasizes making test cases clear, concise, reusable, and up-to-date to reflect any application changes. The document also highlights techniques like breaking tests into focused subsets and attaching relevant artifacts.
The document provides an introduction to Java Enterprise Edition (Java EE) including:
1. An overview of what Java EE is, its key deliverables and basic multi-tier architecture with components and containers.
2. The benefits of Java EE for developers, vendors and businesses including application portability and large developer community support.
3. A brief description of the most common Java EE technologies, specifications, APIs and how applications are assembled and deployed on Java EE platforms.
The theory of SOLID principles was
introduced by Robert C. Martin in his 2000
paper “Design Principles and Design
Patterns”.
SOLID => Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion.
The document is a presentation on ASP.NET MVC. It provides an overview of ASP.NET MVC, including that it is a new presentation option for ASP.NET that allows for simpler programming, easier testing, and more control over HTML and URLs. It then demonstrates building a simple ASP.NET MVC application and unit testing controllers. It concludes by discussing factors to consider when choosing between ASP.NET WebForms and MVC.
The document discusses AJAX (Asynchronous JavaScript and XML), which is a web development technique for building interactive web applications. It allows for asynchronous data retrieval, which means requests are made in the background without interfering with the display and behavior of the existing page. This improves responsiveness as users can interact with the page during data loading. The key components that AJAX uses are XML, HTML, CSS, DOM, and JavaScript. JavaScript plays the important role of binding these components together and enabling asynchronous communication with the server in the background.
The article 'Design Patterns for REST-APIs, plus a quick primer on what they are' is here: https://hersengarage.nl/rest-api-design-as-a-craft-not-an-art-a3fd97ed3ef4
Angular is an open-source TypeScript-based front-end web application platform maintained by Google. It uses MVC and dependency injection patterns. Key features include components, services, routing and calling remote services. Version 1 was released in 2009 as AngularJS and the latest version is Angular 5. It is used to build large web applications and sites like Google and Uber.
Prashant Jain has 4 years of experience developing applications in Pega PRPC. He has experience with application development, testing, troubleshooting, and implementing banking processes. He is proficient in building class structures, flows, activities, and rules. He has worked on projects for Lloyds Bank, AICPA, and Macquarie Bank developing applications and automating processes in areas like case management, enrollment, and releases.
Thilan Peiris is a Certified Senior System Architect with over 6 years of experience designing and developing BPM solutions using PEGA technologies. He has extensive experience leading projects for clients such as CRICO, Telerx Marketing, and New York Life Insurance. His roles have included performing requirements analysis, preparing technical designs, implementing interfaces, ensuring code quality, and collaborating with teams. He is proficient in technologies like Java, PRPC, SQL, and agile methodologies.
Swagger is a specification and complete framework implementation for describing, producing, consuming, and visualizing RESTful web services. The overarching goal of Swagger is to enable client and documentation systems to update at the same pace as the server. The documentation of methods, parameters, and models are tightly integrated into the server code, allowing APIs to always stay in sync. With Swagger, deploying managing, and using powerful APIs has never been easier.
An API is a set of routines, protocols, and tools that allow software applications to communicate with each other. It defines the functionality that is independent of implementation. An API expresses the operations, inputs, outputs, and types of a software component. It allows creation of applications that can access features or data from an operating system, application, or other service. An API acts as an intermediary that allows two applications to communicate, delivering requests from one app to a provider and returning the response.
JPA and Hibernate are specifications and frameworks for object-relational mapping (ORM) in Java. JPA is a specification for ORM that is vendor-neutral, while Hibernate is an open-source implementation of JPA. Both use annotations to map Java classes to database tables. JPA queries use JPAQL while Hibernate supports both JPAQL and its own HQL. Additional features covered include relationships, inheritance mapping strategies, custom types, and querying.
The document provides an introduction and overview of APIs, REST, and OpenAPI specification. It discusses key concepts like resources, HTTP verbs, and OpenAPI structure. It also demonstrates OpenAPI syntax using JSON and YAML examples and highlights best practices for documenting APIs with OpenAPI.
Swagger is a simple yet powerful representation of your RESTful API. With the largest ecosystem of API tooling on the planet, thousands of developers are supporting Swagger in almost every modern programming language and deployment environment. With a Swagger-enabled API, you get interactive documentation, client SDK generation and discoverability.
This document describes a hybrid automation framework built with Java using Selenium. The framework uses a combination of data-driven and keyword-driven approaches. It utilizes tools like Log4j, POI Excel files, TestNG, and Maven. The framework architecture includes modules for controllers, tests, data, object repositories, reports, logs, and exception handling. Test cases and test suites are defined and stored in Excel files. The framework execution flow is depicted in a diagram.
The document introduces Oracle's RAD (Rapid Application Development) Stack, which provides a full-stack solution for developing data-driven business applications. The RAD Stack consists of Oracle REST Data Services (ORDS) for building REST APIs, APEX for low-code application development, and Oracle Database for data storage and SQL. It notes the benefits of the stack being easy to use, robust, fully supported by Oracle, and allowing both simple and sophisticated applications to be built.
The API-first design approach treats APIs as first-class citizens. The entire system or project is built around the idea that components connect via APIs. The first step is, therefore, to design the APIs and their connections.
However, there is a gap between the beautiful world of API specifications and the reality of agile development. This gap means that published API specifications are often incomplete, missing examples or simply outdated. The API specification meant to help developers can be a thorn in one’s side because keeping the specification in sync with its implementation is a manual process, tedious and prone to be forgotten during the rush to deliver.
We show how this gap can be bridged effectively using the API specification as the only source of truth driving the API implementation with proven tools enabling automation.
This document provides an overview of a RESTful JSON API. It discusses that the API uses a REST design with JSON as the output format. It also describes other common protocols like SOAP and XML-RPC. The API is intended for use by desktop, mobile, and third-party web applications that can communicate over HTTP. Key aspects covered include input-output design, error handling, documentation, and user authentication using OAuth. The API implementation leverages the Sinatra framework with common logic modules to share data and configuration across applications. SDKs are also discussed to help integrate external apps with the API.
Swagger UI enables generating documentation for RESTful APIs that is updated as the server code changes. It works with Spring Boot by adding dependencies, a configuration file, and annotations. This exposes API endpoints in the browser for testing and provides descriptive documentation of each service's title, function, inputs, and outputs.
This document provides guidance on how to write effective test cases. It discusses test case components like objectives, preconditions, steps, and expected results. It emphasizes making test cases clear, concise, reusable, and up-to-date to reflect any application changes. The document also highlights techniques like breaking tests into focused subsets and attaching relevant artifacts.
The document provides an introduction to Java Enterprise Edition (Java EE) including:
1. An overview of what Java EE is, its key deliverables and basic multi-tier architecture with components and containers.
2. The benefits of Java EE for developers, vendors and businesses including application portability and large developer community support.
3. A brief description of the most common Java EE technologies, specifications, APIs and how applications are assembled and deployed on Java EE platforms.
The theory of SOLID principles was
introduced by Robert C. Martin in his 2000
paper “Design Principles and Design
Patterns”.
SOLID => Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion.
The document is a presentation on ASP.NET MVC. It provides an overview of ASP.NET MVC, including that it is a new presentation option for ASP.NET that allows for simpler programming, easier testing, and more control over HTML and URLs. It then demonstrates building a simple ASP.NET MVC application and unit testing controllers. It concludes by discussing factors to consider when choosing between ASP.NET WebForms and MVC.
The document discusses AJAX (Asynchronous JavaScript and XML), which is a web development technique for building interactive web applications. It allows for asynchronous data retrieval, which means requests are made in the background without interfering with the display and behavior of the existing page. This improves responsiveness as users can interact with the page during data loading. The key components that AJAX uses are XML, HTML, CSS, DOM, and JavaScript. JavaScript plays the important role of binding these components together and enabling asynchronous communication with the server in the background.
The article 'Design Patterns for REST-APIs, plus a quick primer on what they are' is here: https://hersengarage.nl/rest-api-design-as-a-craft-not-an-art-a3fd97ed3ef4
Angular is an open-source TypeScript-based front-end web application platform maintained by Google. It uses MVC and dependency injection patterns. Key features include components, services, routing and calling remote services. Version 1 was released in 2009 as AngularJS and the latest version is Angular 5. It is used to build large web applications and sites like Google and Uber.
Prashant Jain has 4 years of experience developing applications in Pega PRPC. He has experience with application development, testing, troubleshooting, and implementing banking processes. He is proficient in building class structures, flows, activities, and rules. He has worked on projects for Lloyds Bank, AICPA, and Macquarie Bank developing applications and automating processes in areas like case management, enrollment, and releases.
Thilan Peiris is a Certified Senior System Architect with over 6 years of experience designing and developing BPM solutions using PEGA technologies. He has extensive experience leading projects for clients such as CRICO, Telerx Marketing, and New York Life Insurance. His roles have included performing requirements analysis, preparing technical designs, implementing interfaces, ensuring code quality, and collaborating with teams. He is proficient in technologies like Java, PRPC, SQL, and agile methodologies.
Nilesh Kumar Singh has over 2 years of experience as an ADF developer. He has extensive skills in Oracle ADF, Java, SQL, and PL/SQL. He has worked on several projects for clients like AT&T, Ally USA, and General Motors developing applications using technologies like ADF, APEX, and databases. His responsibilities included requirement gathering, designing, developing, testing, and documenting applications.
The document provides a summary of Nilesh Kumar Singh's professional experience and qualifications. It details his over 2 years of experience as an ADF and Java developer, including specific skills in Oracle ADF, APEX, SQL, and PL/SQL. It also lists his educational background of a Bachelor's degree in Mechanical Engineering and various technical training certifications. Key projects are summarized, including roles in developing web applications for AT&T and General Motors.
This resume is for K. Ramesh Babu, who has 4 years of experience in software development including experience with Adobe Experience Manager (AEM), Java, BPM Savvion, and web technologies. He has worked on projects for clients like Visa Inc. and Wipro Technologies developing websites and applications. His roles have included AEM development, configuration, testing, and administration as well as requirements analysis, design, and project management.
This document contains the resume summary of Naresh Chirra. It summarizes his 3 years of experience developing web applications using Java/J2EE technologies. It also lists his academic qualifications including a B.Tech in computer science, and provides details of 7 projects he worked on, including the technologies used and his roles and responsibilities. The projects involved developing applications for various clients in areas like automation testing, HR management, logistics, and social networking.
This document is a resume for S V Prasad Rompalli summarizing his professional experience and qualifications. He has over 11 years of experience in applications support and production support involving Java, Sybase ASE database, and Unix shell scripting. His most recent role was as an IT Technology Consultant providing support for Java applications at Sybase India Pvt Ltd from 2007 to 2014. He also has experience in database development, Unix production support, and data migration projects.
This document is a resume for Pranjali Mundra, who has over 7 years of experience as a Pega and Java developer. She has 3 years of experience working with Pega Technology and over 3 years of experience with Java and related technologies. She is looking for a position that utilizes her skills and experience in delivering software solutions as part of a team or independently. Her experience includes working as a Senior Software Developer at Incessant Technologies and as a Software Engineer at Pegasystems Worldwide. She has a Bachelor's degree in Computer Science.
Pratheeshkumar provides a summary of his professional experience, including over 3 years of experience in testing and development. He has experience with technologies like C#, Java, Python, SQL Server, Selenium, and security testing tools. Some of the projects he has worked on include a web application for employee information and timekeeping, a DevOps project integrating development and operations, and an application for remote script execution. He also lists his education qualifications and awards received.
Debasish Hotta is a software test engineer with 4-5 years of experience in manual and automation testing of e-commerce applications. He has expertise in test case design, requirements analysis, defect tracking, Selenium automation, API testing, and SQL. Some of his projects include developing automated test cases using Robot Framework for a smart tech e-commerce application and writing Webdriver scripts to test the functionality of an online cosmetics store. He aims to leverage his skills in test automation, Java, SQL, and agile methodologies to contribute to quality assurance.
This document contains the resume of Atish Gaikwad seeking a managerial role in software development. It summarizes his 9+ years of experience in areas like software development, testing and team leadership. It details his technical skills like C#.NET, ASP.NET, SQL Server and his experience delivering projects for clients in various roles and responsibilities like requirement gathering, designing, development, testing and implementation.
Swapnil Shelke has over 4 years of experience developing web applications using Java technologies like Web DynPro, CAF, and BPM within SAP environments. He has worked on projects involving requirement analysis, design, development, and deployment of applications. His roles have included developing applications, administering SAP Enterprise Portals, and supporting patching, upgrades, and implementations.
Ankit Ojha has over 9 years of experience in integration middleware technologies including Oracle SOA Suite, OSB, and Java. He currently works as a manager at Capgemini where he acts as a lead designer and module lead for projects integrating various systems. Some of his responsibilities include designing architectures, developing interfaces, and coordinating with clients and teams.
The document is a resume for Shruti Kulkarni, who is seeking a position as a software tester. She has over 2 years of experience in manual testing, automation testing, functional testing, integration testing, and regression testing. She has expertise in bug tracking and has experience testing REST APIs, web applications, and SAS systems. She provides details on 5 projects she has worked on, including the technologies used, her role, and her responsibilities. The resume highlights her skills in software testing and experience across different domains.
Secrets of going codeless - How to build enterprise apps without codingNewton Day Uploads
The document discusses methods for building enterprise applications without coding, known as codeless development or CAAD (Computer Aided Applications Development). It describes how CAAD uses pre-built components and templates to create applications through a point-and-click interface, removing the need for extensive programming. The methodology involves four phases - plan, develop, release, and review. Key aspects of the CAAD process include defining the application purpose and requirements, prototyping the design, user testing iterations, and ongoing maintenance after release. Site constructs provide predefined user interface elements to help bridge communication gaps between technical and non-technical users.
Design and Monitoring Performance of Digital PropertiesIRJET Journal
This document discusses the design and monitoring of digital properties such as web applications and APIs. It proposes using the Django framework to develop a web application and integrate APIs. It describes using cron jobs to perform backend tasks and external libraries for the frontend. An Elastic agent would be installed to monitor application performance on Kibana dashboards. This provides an end-to-end solution for developing, integrating, and monitoring digital properties using open source tools.
S V Prasad Rompalli is seeking a team leader or team member position utilizing over 11 years of experience in applications and production support using Java, Sybase databases, and Unix shell scripting. He has worked on several projects providing support for Java applications and databases, developing stored procedures, and writing Unix scripts. His objective is to work in a challenging position using his operational support skills while improving his knowledge and contributing to organizational growth.
Ankit Rustagi has over 11 years of experience in software development. He currently works as a Senior Advisory Consultant at IBM India Pvt Ltd. Previously he has worked as a Lead Engineer at PureSoftware Ltd, Senior Consultant at Capgemini India Pvt Ltd, and Senior Associate at Simplion Technologies Ltd. He has extensive skills in Salesforce development including Apex, Visualforce, Lightning, and administration. He also has experience with technologies like Java, JavaScript, HTML, and SQL. He holds certifications in Salesforce Platform Developer I, Salesforce Administrator, and SAFe 4 Practitioner.
Kiran has over 7 years of experience as a Java developer. He has extensive skills in technologies like Spring MVC, Hibernate, Struts, JPA, Java, J2EE, Oracle, and MySQL. He has worked on several projects for clients in the insurance, government, and logistics domains, developing applications for tasks like policy issuance, claims management, transport management, and rate management. His responsibilities included design, coding, testing, enhancements, and interacting with clients on requirements.
Joyce M Sullivan, Founder & CEO of SocMediaFin, Inc. shares her "Five Questions - The Story of You", "Reflections - What Matters to You?" and "The Three Circle Exercise" to guide those evaluating what their next move may be in their careers.
A Guide to a Winning Interview June 2024Bruce Bennett
This webinar is an in-depth review of the interview process. Preparation is a key element to acing an interview. Learn the best approaches from the initial phone screen to the face-to-face meeting with the hiring manager. You will hear great answers to several standard questions, including the dreaded “Tell Me About Yourself”.
Success is often not achievable without facing and overcoming obstacles along the way. To reach our goals and achieve success, it is important to understand and resolve the obstacles that come in our way.
In this article, we will discuss the various obstacles that hinder success, strategies to overcome them, and examples of individuals who have successfully surmounted their obstacles.
We recently hosted the much-anticipated Community Skill Builders Workshop during our June online meeting. This event was a culmination of six months of listening to your feedback and crafting solutions to better support your PMI journey. Here’s a look back at what happened and the exciting developments that emerged from our collaborative efforts.
A Gathering of Minds
We were thrilled to see a diverse group of attendees, including local certified PMI trainers and both new and experienced members eager to contribute their perspectives. The workshop was structured into three dynamic discussion sessions, each led by our dedicated membership advocates.
Key Takeaways and Future Directions
The insights and feedback gathered from these discussions were invaluable. Here are some of the key takeaways and the steps we are taking to address them:
• Enhanced Resource Accessibility: We are working on a new, user-friendly resource page that will make it easier for members to access training materials and real-world application guides.
• Structured Mentorship Program: Plans are underway to launch a mentorship program that will connect members with experienced professionals for guidance and support.
• Increased Networking Opportunities: Expect to see more frequent and varied networking events, both virtual and in-person, to help you build connections and foster a sense of community.
Moving Forward
We are committed to turning your feedback into actionable solutions that enhance your PMI journey. This workshop was just the beginning. By actively participating and sharing your experiences, you have helped shape the future of our Chapter’s offerings.
Thank you to everyone who attended and contributed to the success of the Community Skill Builders Workshop. Your engagement and enthusiasm are what make our Chapter strong and vibrant. Stay tuned for updates on the new initiatives and opportunities to get involved. Together, we are building a community that supports and empowers each other on our PMI journeys.
Stay connected, stay engaged, and let’s continue to grow together!
About PMI Silver Spring Chapter
We are a branch of the Project Management Institute. We offer a platform for project management professionals in Silver Spring, MD, and the DC/Baltimore metro area. Monthly meetings facilitate networking, knowledge sharing, and professional development. For more, visit pmissc.org.
In the intricate tapestry of life, connections serve as the vibrant threads that weave together opportunities, experiences, and growth. Whether in personal or professional spheres, the ability to forge meaningful connections opens doors to a multitude of possibilities, propelling individuals toward success and fulfillment.
Eirini is an HR professional with strong passion for technology and semiconductors industry in particular. She started her career as a software recruiter in 2012, and developed an interest for business development, talent enablement and innovation which later got her setting up the concept of Software Community Management in ASML, and to Developer Relations today. She holds a bachelor degree in Lifelong Learning and an MBA specialised in Strategic Human Resources Management. She is a world citizen, having grown up in Greece, she studied and kickstarted her career in The Netherlands and can currently be found in Santa Clara, CA.
1. 10/13/22, 11:10 AM Top 50+ Most Asked Pega Interview Questions and Answers (2022) - JavaTpoint
https://www.javatpoint.com/pega-interview-questions 2/25
Top 50+ Most Asked Pega Interview Questions and
Answers
1) What is Pega? / Explain in brief about Pega.
Pega is a popular BPM tool and a platform that allows users to develop apps, perform integration
with the external system and implement mobility easily. It is mainly concerned with customer
engagement and digital process automation.
2) What are the main usages of Pega?
Pega is a platform that facilitates users to develop applications, implement mobility, help in
managing the case life cycle, extensive user interface design, managing the decisions and
implementing the DevOps and Robotic Automation, extensive User Interface Design, and reporting
etc. Pega is preferred over other tools that it eliminates coding, simplifies the process by using
inbuilt functionalities and mainly stands for reusing the existing rules and modifying accordingly.
Pega is built on Java. Its latest version is Pega 8.2, which stands for Build for Change.
3) What are the new components added in the Pega 8.4 version for
application development?
From the application development point of view, the following are some of the new features added
in Pega 8.4:
⇧ SCROLL TO TOP
2. 10/13/22, 11:10 AM Top 50+ Most Asked Pega Interview Questions and Answers (2022) - JavaTpoint
https://www.javatpoint.com/pega-interview-questions 3/25
In Pega 8.4, we can use role-based workspaces.
The new version provides developers with the capability to review complete project
highlights on a single page.
It also provides effective management of reusable components.
4) What are the different developer tools used in Pega?
The developer tools used in Pega are: Designer Studio and Pega Express.
5) What are the different debugging tools available in Pega?
Different debugging tools available in Pega are: Tracer, Clipboard, SMA and PLA.
6) What are the certifications available for developers in Pega?
Following is the list of main certifications available for developers in Pega:
CSA: CSA stands for Certified System Architect. It is the basic level of certification as the
entry-level for a developer.
CSSA: CSSA stands for Certified Senior System Architect. This is an advanced level of
certification for developers. The developers with this certification are considered experts in
building, judging, and leading a team with good technical aspects.
LSA: LSA stands for Lead System Architect. This is the most advanced level of certification for
developers. The developers with this certification are considered leaders of development who
are thorough with all the functionalities and implement accordingly.
7) What do you understand by workspace or studio in Pega?
A workspace or studio in Pega is an environment that provides specific tools and features.
8) What are the different types of harnesses used in Pega?
There are several types of standard harnesses available in Pega, but the most commonly used
harness is new, perform, review, conform, Tabbed, perform screen flow, Tree Navigation etc.
⇧ SCROLL TO TOP
3. 10/13/22, 11:10 AM Top 50+ Most Asked Pega Interview Questions and Answers (2022) - JavaTpoint
https://www.javatpoint.com/pega-interview-questions 4/25
9) What are the various workspace supported in the latest release of Pega?
The latest release of Pega supports the following four types of workspace:
App Studio
Dev Studio
Admin Studio
Prediction Studio
10) What are the different types of classes that PRPC support?
Following are the different types of classes that PRPC supports:
Base class: It is the ultimate base class, and its child classes are work-, Data-, Rule-, Assign-,
History-, etc. Pega always supports two types of classes which are abstract classes and
concrete classes.
Abstract Classes: The Abstract Classes are the classes that end with '-' and abstract classes
cannot create any work object instances.
Concrete Classes: The Concrete Classes do not end with '-', and they will create work object
instances.
11) What are the different techniques used in activities?
Following is the list of some different techniques that are used in the activities:
Program by IIT Roorkee EICT
Learn from IIT Professors & Industry Practitioners.
Advance Your Career Now!
Intellipaat Open
Page- Remove
⇧ SCROLL TO TOP
4. 10/13/22, 11:10 AM Top 50+ Most Asked Pega Interview Questions and Answers (2022) - JavaTpoint
https://www.javatpoint.com/pega-interview-questions 5/25
Page- New
Object - List
Object -Open
Object - Save
RBD -Save
RBD - List
RBD - Delete
12) What do you understand by id DataPage and what is its scope?
DataPage is Single Page or a Page list where it stores the data that the system needs to populate
work item properties for its calculation or other processes.
13) What is the difference between Page property and Page List property?
How are they implemented?
Difference between Page property and Page List property:
Page property: Page property refers to a particular class and is used to access the property
of that class.
Page List property: Page List Property also refers to a particular class, but it is a collection of
individual pages of the same class which can be accessed through numeric indexes.
14) What is the difference between page-validate and property-validate
methods in Pega?
Differences between page-validate and property-validate methods in Pega:
Page-validate:
The page-validate method is used to validate all the properties present on a page.
If a page has embedded pages, the page-validate method works recursively to validate all the
properties.
The page-validate method consumes a lot of system resources and takes more time.
⇧ SCROLL TO TOP
5. 10/13/22, 11:10 AM Top 50+ Most Asked Pega Interview Questions and Answers (2022) - JavaTpoint
https://www.javatpoint.com/pega-interview-questions 6/25
If you want to validate specific properties, it is preferred to use the obj-validate method with
a rule-obj-validate rule.
Property-validate:
IIT Madras CCE Cloud
Computing
Get 1:1 Mentorship.Learn from IIT Madras
Faculty & Industry Experts. Apply Now!
Intellipaat Open
A property-validate method is used to impose restrictions on property values.
We have to use the edit validate rule along with the property-validate method to impose
restrictions.
The property-validate method can be used to validate multiple properties simultaneously.
15) What do you understand by work object? How can you create a work
object in Pega?
A work object is the primary unit of the work completed in an application. It is the primary collection
of data that a flow operates on. While using an application, a work object is created, updated, and
eventually closed (resolved).
Every work object has a unique ID (property pyID), an urgency value, and a status (property
pyStatusWork).
Following are the steps that we have to implement in creating a work object in Pega:
First, add a button such as a section or a header.
⇧ SCROLL TO TOP
6. 10/13/22, 11:10 AM Top 50+ Most Asked Pega Interview Questions and Answers (2022) - JavaTpoint
https://www.javatpoint.com/pega-interview-questions 7/25
Expand the cell property within the button and click on the action tab.
Add an action set to the button.
Add focus class as well as flow name to the button.
Catch the present work object ID with "Param.prevRecordkey".
Open the case using the "Obj-Open-By-Handle".
Copy the data from pagers using the Page-Copy.
16) Is it possible to begin a flow using activity? If yes, then what is the
method used in it?
Yes. It is possible to begin a flow using activity. The name of the method used in this is Flow-New.
17) What are the differences between declare pages and regular pages?
Differences between declare pages and regular pages:
Declare Pages:
Declare pages are created using declarative rules.
The declare keyword must be specified while creating a declare page.
Declare pages are read-only pages, and these pages cannot be deleted or updated directly.
Regular pages:
Regular pages or user pages are created using a page new method.
These pages can be easily updated or deleted directly
, and these pages are automatically deleted once logout from the system.
18) What is a portal in Pega, and where it will be configured?
Portal is an interface that appears for the users (Developers or End Users). Portal can be configured
in Access Group. For example, Developer portal, manager portal, user portal, admin portal etc.
19) What are the different types of requestors in Pega?
⇧ SCROLL TO TOP
7. 10/13/22, 11:10 AM Top 50+ Most Asked Pega Interview Questions and Answers (2022) - JavaTpoint
https://www.javatpoint.com/pega-interview-questions 8/25
Following are the different types of requestors in Pega:
Browser requestor: The browser requestor starts with the letter 'H'.
Batch requestor: The batch requestor starts with the letter 'B'.
Application requestor: The application requestor starts with the letter 'A'.
Portal requestor: The portal requestor starts with the letter 'P'.
20) What are classes in Pega? What are the different types of classes
available in Pega?
Pega is a platform that allows users to reuse rules across case types and applications. It facilitates
developers to frequently reuse rules in their systems, ranging from single data pieces to complete
processes. Reusing the rules increases the quality of the application that can also draw a positive
impact on the development time. The Pega platform divides the rules into classes according to their
re-usability inside an application. Each cluster is called a class.
There are three different kinds of classes used to make an application:
Work Class: The work class includes the processes, data items, and user interfaces. These are
all part of the work class, which provides the rules that govern how to process a case.
Integration Class: The Integration class consists of the rules that specify how the application
interacts with other services, such as the integration resources connecting to a customer
database or a third-party web server.
Data Class: The data class stores the rules that specify the data objects used in the
application, such as a customer data type or order items data type etc.
When a rule is added in the App Studio, it automatically selects the proper class. You have to
concentrate on what you want the rule to accomplish rather than how to develop it. You can also
write the rule in Dev Studio if you need control over the class. The Dev Studio is preferred if you
write a rule that you can reuse in another app.
⇧ SCROLL TO TOP
8. 10/13/22, 11:10 AM Top 50+ Most Asked Pega Interview Questions and Answers (2022) - JavaTpoint
https://www.javatpoint.com/pega-interview-questions 9/25
IIT Madras CCE Cloud
Computing
Get 1:1 Mentorship.Learn from IIT Madras
Faculty & Industry Experts. Apply Now!
Intellipaat Open
21) What do you understand by DCO in Pega?
In Pega, DCO stands for Direct Capture Object. It is an apple dev tool that includes the following
things in the application.
Application profiler wizard
Appl Accelerator
Appl Doc Wizard
Appl use cases
Appl requirements
22) What is SLA? What is its usage?
SLA is an instance of Rule-Obj-Service Level Rule type that can be added to assignment and work
objects. There are two-time intervals for SLA as Goal and Deadline, and it indicates the expected
time for the assignment and time to resolve the work object. If an assignment isn't completed
before the time limit, the system can automatically raise the assignment and cancel the entire flow,
and so on.
23) What are the different types of SLA? Explain them briefly.
Following are the different types of SLA used in Pega:
⇧ SCROLL TO TOP
9. 10/13/22, 11:10 AM Top 50+ Most Asked Pega Interview Questions and Answers (2022) - JavaTpoint
https://www.javatpoint.com/pega-interview-questions 10/25
Assignment SLA: As the name suggests, the Assignment SLA refers to an assignment. This
SLA begins with the creation of the assignment and ends with the completion of the
assignment. The assignment urgency is set in the attribute pxUrgencyAssignSLA on the newly
Assigned Page.
Case Level SLA: The Case Level SLA is an SLA that is referred to at the case level. This SLA is
relevant throughout the lifecycle of a case. It starts when a case is opened and is completed
when the case is closed. The standard property pySLAName is used to identify this SLA under
the work page, and it is set in pyWorkPage's pxUrgencyWorkSLA parameter. The
pxUrgencyWorkSLA property under pyWorkPage is used to control the urgency of case-level
SLAs.
Stage Level SLA: The Stage Level SLA is an SLA that is referred to at the stage level. It starts
when a case enters a stage and ends when it exits the stage. The pxUrgencyWorkStageSLA
property under pyWorkPage is used to control the urgency at the Stage level.
Step level/Flow level SLA: An SLA is called a Step level or Flow level SLA when referred to as
a step or flow level. A step-level SLA starts when a process or step is initiated and ends when
it is completed. A flow level SLA is started when a flow is begun and stopped when a flow is
stopped. If a step SLA is present, it takes precedence over a flow SLA. Step SLA can be
referenced in every step under the stage in the case type rule. The process tab of the flow
rule refers to a flow SLA. The pxUrgencyWorkStepSLA property under pyWorkpage controls
the flow or step level urgency.
⇧ SCROLL TO TOP
10. 10/13/22, 11:10 AM Top 50+ Most Asked Pega Interview Questions and Answers (2022) - JavaTpoint
https://www.javatpoint.com/pega-interview-questions 11/25
24) How can we trace SLA in Pega?
We can use the following steps to trace SLA in Pega:
By terminating the agent.
By delaying it.
By initiating the agent.
Delay it again.
In the requestors, select the delayed requestor and click on the tracer.
Send this case to a particular assignment containing the SLA within 60 seconds.
25) What is the difference between activity and Utility in Pega?
Following are the key differences between activity and Utility in Pega:
In the Pega platform, activity is used to automate processing. It can be configured to allow
the system to automate claim uploads without user intervention.
An activity contains a sequence of steps that perform in the instructed order.
Activity is a rule of Rule-Obj-Activity, and Utility is a shape in the Pega flow. This shape refers
to an activity with the usage type which is selected as a Utility.
There are several usage types for an activity such as Utility, Connect, Assign, Notify, or Route.
The Utility is used when you want to call activity in a flow.
26) What is the RuleSet in Pega?
In Pega, the RuleSet is a collection of rules of business that defines an instance. The RuleSet is an
essential subset of PegaRULES that is necessary to reference instances in the database.
27) What are the key advantages of case management in Pega?
Following are the key advantages of case management in Pega:
It can improve the processes of case management with holistic support.
It also increases the efficacy of case-flow for automatic and dynamic responses.
⇧ SCROLL TO TOP
11. 10/13/22, 11:10 AM Top 50+ Most Asked Pega Interview Questions and Answers (2022) - JavaTpoint
https://www.javatpoint.com/pega-interview-questions 12/25
It ensures consistency and removes errors with context-based and real-time management.
It is time-efficient and saves time, costs and effort needed to implement case management.
28) What is DCO in Pega? What are the benefits of using DCO in Pega?
In Pega, DCO stands for Direct Capture of Objectives. It is acquiring, organizing, and storing data by
using Pega's integrated solution, the Pega Platform. DCO includes the processes and tools used for
gathering and organizing application artefacts. This technology is used by IT, business, and testing
teams and other resources to save time, effort, and money while also improving the quality of
projects and their impact on society.
DCO is not a methodology or a tool. Instead, it is used to centralize data to be used continually
across departments at the right time and the right level. DCO also eliminates communication
obstacles by providing a centralized repository for linked application artefacts (objectives,
requirements, specifications, and implementation rules). All resources have real-time as-built
documentation and a single view of the application.
Following are the tools DCO uses to automate the work:
Case Lifecycle Manager
New Application Wizard
⇧ SCROLL TO TOP
12. 10/13/22, 11:10 AM Top 50+ Most Asked Pega Interview Questions and Answers (2022) - JavaTpoint
https://www.javatpoint.com/pega-interview-questions 13/25
Application profiler
Document generation
Effort Estimation
Specification documents
Benefits of using DCO in Pega:
DCO is used to enable collaborative teams to model situations that the application's end
users must address. The modelling and simulation tools facilitate users to take a critical
interim step after documenting the application but before incurring the cost of development
to see if the software meets our objectives. When you work out solutions as a part of the
software development life cycle, it is a rare chance to get a problem in production.
Organizations also use DCO to improve their efforts and use iterative processes. It makes the
software development process more visible, allowing teams to learn and improve constantly.
DCO technologies give organizations several ways to deliver go-live, increasing their return
on investment and allowing them to accomplish their objectives reliably.
29) What are some types of portals provided by the PRPC?
PRPC provides the following four types of portals:
Custom Portals
⇧ SCROLL TO TOP
13. 10/13/22, 11:10 AM Top 50+ Most Asked Pega Interview Questions and Answers (2022) - JavaTpoint
https://www.javatpoint.com/pega-interview-questions 14/25
Mobile Portals
Composite Portals
Fixed Portals
30) What is the difference between obj-open and obj-open-by-handled in
Pega?
Key differences between obj-open and obj-open-by-handled in Pega:
Obj-Open: In Obj-Open, you will get multiple records from a table according to the criteria from
the specified class. It also opens an instance of a given class.
OBJ-open-handle: In OBJ-open-handle, you have had to pass the pzInskey as an instance handle.
This method opens only one record at a time, and it also opens the object by the handle to the
pzInsKey value.
31) How can you save the instances of a class in a particular database?
We can save the instances of a class in a particular database by creating a separate database table
to the working class within a DB or the external DB.
32) How can you resolve work objects using activity?
We can resolve the work objects using activity in the following way:
First, open the object.
Set the right ticket on your flow to reach resolution status or use "FinishAssignment".
33) What are work objects in Pega?
Work objects are the primary unit of the completed work in the application. It is a collection of
essential data in which a flow operates. All the work objects contain an urgency value, unique ID,
and status.
34) What are the different types of layouts available in Pega?
⇧ SCROLL TO TOP
14. 10/13/22, 11:10 AM Top 50+ Most Asked Pega Interview Questions and Answers (2022) - JavaTpoint
https://www.javatpoint.com/pega-interview-questions 15/25
Following are the different types of layout available in Pega:
Screen Layout: The screen layouts are only used within a harness and are typically used to
establish portals for an application.
Dynamic Layout: The dynamic layout is a DIV-based layout, and it is used to display content
in a variety of ways.
Column Layout: A Columns layout is used to allow us to show major content, like a work
item, alongside supporting stuff, like an attachment.
Grid Layout: The grid layout is also called table layout. It makes obtaining and comparing
data easier for the users. In this layout, tables are used as a flexible base for users to process
vast volumes of data in your apps. An example of a grid layout is "tables" in price comparison
software, and it can assist customers in quickly identifying the best deal.
Tree Grid Layout: The tree layout is used to view, navigate and access the properties in
embedded pages. It facilitates users to swiftly extend and collapse branches of the tree to
identify entries of current interest.
In dynamic and column layouts, you can add content to a section, such as properties, controls, and
other sections. The format of the skin determines the positioning, alignment, width, and
arrangement of components in a layout.
35) What is the difference between Pega BPM and Appian BPM?
A list of key differences between Pega BPM and Appian BPM:
Comparing
Feature
Pega BPM Appian BPM
Application Pega BPM is used to develop
applications without hard
coding.
Appian BPM requires work automation of
enterprise with data management.
Latest Version The latest version of Pega BPM
is Pega - 7.2.
The latest version of Appian is Appian - 18.1.
Integrations
Supported
Pega BPM supports Data
Collection Systems and
Various CRMs
Appian BPM supports only Compatible
Datasheets.
⇧ SCROLL TO TOP
15. 10/13/22, 11:10 AM Top 50+ Most Asked Pega Interview Questions and Answers (2022) - JavaTpoint
https://www.javatpoint.com/pega-interview-questions 16/25
Supported OS Pega BPM supports Windows,
Linux, Mac, and Web-Based
OS.
Appian BPM supports Windows, Windows
Mobile, Android, iPhone, Mac, and Web-Based
OS.
Customer
Types / Mainly
used in
Pega BPM is mainly used in
medium and large businesses.
Appian BPM is mainly used in small, medium,
and large businesses.
36) What do you understand by Prediction studio in Pega?
In Pega, the prediction studio is the studio that is used to build machine-learning models for
adaptive, predictive, and text analytics.
37) What are the different types of standard harnesses we can use in
Pega?
There are several different types of harnesses available in Pega. But, the most commonly used
standard harnesses are new, perform, review, conform, Tabbed, perform screen flow, Tree
Navigation etc.
38) How can you create a dynamic layout in Pega?
1. First, select and open a section form that already exists.
2. Now, expand the structural list on the Design tab and drag the dynamic layout onto the work
area.
3. Click the view properties icon in the dynamic layout header.
4. Set the layout format in the properties window in any one of the following ways:
Choose one of the predefined formats.
Select other and then specify the custom layout format in the adjacent field to use a
skin-defined custom layout format.
5. Select when you want the dynamic layout to appear in the visibility field in either of the
following ways:
Choose one of the predefined options.
⇧ SCROLL TO TOP
16. 10/13/22, 11:10 AM Top 50+ Most Asked Pega Interview Questions and Answers (2022) - JavaTpoint
https://www.javatpoint.com/pega-interview-questions 17/25
Select condition (expression) and then the open condition builder icon to construct
your own condition.
6. At the end, submit the form.
39) What is the name of the table that is used for adding a note in Pega?
In Pega, the table used for adding the note is pc_data_workattach.
40) What is the main advantage and disadvantage of declaring pages in
Pega?
Advantage of the declare pages in Pega:
The main advantage of declaring pages is that it can prevent multiple DB hits. Suppose there are
multiple requestors in a node, so whenever the first user login into the application, then load activity
will be fired and create a declare page and then load the data on that page. The requestors on that
node see this declare page and use the data on that page.
A disadvantage of the declare pages in Pega:
The main disadvantage of this is its read-only to the requestors. It can't add the additional data and
can't delete the specific data.
41) What are the various types of declarative rules present in Pega?
The various types of declarative rules present in Pega are:
⇧ SCROLL TO TOP
17. 10/13/22, 11:10 AM Top 50+ Most Asked Pega Interview Questions and Answers (2022) - JavaTpoint
https://www.javatpoint.com/pega-interview-questions 18/25
Declare Expressions
Declare Constraints
Declare On change
Declare trigger
Declare Index
42) What are Declare Triggers in Pega?
Declare Triggers are used to run an activity when instances of a specific class are created, updated,
or deleted in the DataBase. Declare Triggers are always Forward Chaining.
43) What are the most important debugging tools available in Pega?
The most important debugging tools available in Pega are:
Clipboard
Tracer
SMA
PLA
44) What is the prediction studio in Pega?
In Pega, the prediction studio is the studio used for building machine learning models for text
analytics, predictive, and adaptive models.
45) What do you understand by Agent in Pega? What are the different types
of Agents?
Agents are the internal background process being operated on a server for running an activity.
There are mainly two types of agents, i.e. agent queue and data-agent-queue.
46) What are the different kinds of joins available in the reports in Pega?
⇧ SCROLL TO TOP
18. 10/13/22, 11:10 AM Top 50+ Most Asked Pega Interview Questions and Answers (2022) - JavaTpoint
https://www.javatpoint.com/pega-interview-questions 19/25
Following are the different kinds of joins available in the reports in Pega:
Inner join
Outer join
Right Outer join
Left Outer join
47) What do you understand by a WSDL file?
WSDL stands for Web Service Description Language. This is a description language written in the
XML format, and it is a standard for defining the functionality of a Web Service.
48) What is Notify in Pega?
In Pega, notify is required to configure your flow to automatically send notification messages about
assignments and connect a notify shape to the assignment. A notify shape identifies a notify activity.
49) What is the key difference between the Decision Tree and the Decision
Table?
The Decision Tree is used to check multiple properties. On the other hand, the Decision Table is used
for checking only one property.
50) What is the access group in Pega, and what is its functionality?
An access group in Pega is an example of a Data-Admin-Operator-Access Group class used to
create a set of RuleSet for the requestors. It is the role of the developer to define the access groups
and assign them to different users.
Access group is used to control the security based on the job functions. It is the instance of Data-
Admin-Operator-AccessGroup. Following are the various aspects that can be controlled through an
access group:
Default and available types of works (also called work pools).
Primary rulesets (Access Control to rulesets).
⇧ SCROLL TO TOP
19. 10/13/22, 11:10 AM Top 50+ Most Asked Pega Interview Questions and Answers (2022) - JavaTpoint
https://www.javatpoint.com/pega-interview-questions 20/25
Assigned roles.
Portal layout.
Default ruleset for making changes (Default ruleset whenever the user creates/ saves as a
rule).
51) Why is paging used in a list view?
Paging is used in a list view to split the list view into diverse pages and set the numeral of records
displayed on a page.
52) What is a requestor type in Pega? What are the different types of
requestor types in Pega?
In Pega, a Data-Admin-Requestor instance defines a requestor type. The BROWSER requestor type
indicates the characteristics of interactive user connections, such as guest connections, utilizing
Internet Explorer or another web browser. Agents employ the BATCH requestor type for background
processing. Pega Platform comes with four requestor types for the system name we specify during
installation and a reserved requestor type prpc.BROWSER for exceptional cases.
Generally, we only require the four requestor types that contain our system name. If we want to
modify the system name after installation, we have to go to Designer Studio => System => Settings
=> System Name to get to a landing page tab where we can make the change. When we change a
system's name, new requestor instances are created that correspond to the previous name's
instances. If the prior system name did not include all requestor types for some reason, the missing
requestors are also produced when the system is renamed.
Following are the different requestor types in Pega:
Application: The application requestor type is used by listeners and external client systems
to access the Pega Platform, such as through a service request (other than JSR-168 requests
using Rule-Service-Portlet rules). Requestor IDs that begin with the letter A are used in
requestor sessions that use this requestor type instance.
Batch: The batch requestor type is used by listeners, services, agents, and daemons executing
background processing. The requestor ID for requestor sessions using this instance begins
with the letter B. All BATCH requestors have access to the PRPC.
⇧ SCROLL TO TOP
20. 10/13/22, 11:10 AM Top 50+ Most Asked Pega Interview Questions and Answers (2022) - JavaTpoint
https://www.javatpoint.com/pega-interview-questions 21/25
Browser: The browser requestor type is used for accessing the Pega Platform portal via a
web browser via HTTP or HTTPS or from a browser displaying a Pega composite application.
The requestor ID for requestor sessions utilizing this instance starts with the letter H.
Portal: The portal requestor type is used in conjunction with Service Portlet rules for HTTP
access as a portlet. The requestor ID for requestor sessions utilizing this instance starts with
the letter P.
You may also like:
Java Interview Questions
SQL Interview Questions
Python Interview Questions
JavaScript Interview Questions
Angular Interview Questions
Selenium Interview Questions
Spring Boot Interview Questions
HR Interview Questions
C Programming Interview Questions
C++ Interview Questions
Data Structure Interview Questions
⇧ SCROLL TO TOP