pega-interview-questions

 

42. What do you mean by workspace or studio?

Ans: A workspace is an environment that provides particular features and tools.

43. A system admin complained that he could not access the admin studio? What could be the potential reason?

Ans: One needed some tools to access Admin Studio; they are:

SysAdmin4

PegaRULES: SysOpsAdministrator 

PegaRULES: SysOpsObserver

44. In Pega 8.4, what are the new components added for application development?

 Ans:

In-app development, some cool new features are included :

  • Role-based workspaces are used.
  • Reusable components are managed effectively.
  • Developers can review entire project highlights on a single page.

45. What is a prediction studio?

Ans: A prediction studio is a dedicated workspace for data scientists to control the life cycle of advanced analytics models. The prediction studio consists of predictive models, self-learning or adaptive models, and text models.

46. What are the benefits of DCO?

Ans:

  • DCO means Direct Capture of Objectives. DCO is a process of storing, acquiring, and organising data with the help of Pega’s integrated tools.
  • DCO includes Processing tools for gathering and organising application artefacts. 
  • DCO technology and good practices help organisations increase their ROI and allow them to fulfil their goals in many ways.
  • DCO allows

47. What are some types of portals provided by the PRPC?

Ans: PRPC consists of four types of portals

  • Custom portals
  • Fixed portals
  • Mobile portals
  • Composite portals.

48. Explain Requestor Type in Pega?

Ans: The requestor type in Pega is the requestor that accesses the Pega platform like an external application, an internal background process, or a browser session.

49. Explain activities in the context of Pega?

Ans: In Pega, platform activities make process automation. In Dev Studio, activities contain a series of steps that perform in the given order to keep activities short. 

50. Explain the declarative rule in the context of Pega.

Ans: A declarative rule is an instance of a subclass of the Rule-Declare class. They allow the automatic processing of values.

51. How can you resolve work objects using activity?

Ans:To resolve work objects using activity, we have to follow the steps they are:

First step: open the object.

Second step: set the correct ticket on your flow or click on Finish Assignment.

52. How can you measure the performance of your application in Pega?

Ans:There are different ways to measure the performance of your application in Pega.

Performance analyser tool, DB trace, Autonomic Event Services (AES), and Alerts

53. How do you specify if expression triggers f/w or b/w chaining?

Ans:By checking the Chain tracking tab, you can specify if an expression triggers f/w or b/w.

54. Explain the Different types of harnesses that you have used?

Ans:Pega applications typically use four standard harnesses to organise the content of user forms they are: new, perform, review, conform,

55. What is the Declare Index in Pega?

Ans:Declare index is a rule that exposes aggregate properties like List, page, or Group for reporting purposes. They are a part of the system admin category.

56. What is Rule Resolution in Pega, and what are its benefits?

Ans:Rule Resolution is a search algorithm the system uses to determine the most appropriate or the best rule to apply and complete the process. With automated rule resolution, one can save time and make sure you implement resources efficiently.

57. Can we refer to the property without exposing it in Reports?

Ans:Yes, without exposing we can refer to the property in the display tab.  We can’t refer to the property without exposing it in the criteria fields of the content tab.

58. Do we need to create an Agent Schedule?

Ans:No. we can not create Agent schedules manually.

The Agent Manager on our Process Commander system generates at least one agent schedule instance for each agent’s rule.

59. How do we handle Escalation?

Ans:Escalation means any processing within a Process Commander application that causes high-priority work objects to become visible to users and managers and to be processed immediately. Escalation can occur through a service level rule associated with the flow and through background processing by the Pega-ProCom agent

60. What is the use of the RDB-Open method?

Ans:RDB- Open method retrieves a single row of data from an externas database and then adds the retrieved data into a specified clipboard page as property values and names.

61. What are the types of flow in Pega?

Ans:

The types of flow in Pega are 

  1. Process flows
  2. Screen flows
  3. Subflow’s
  4.  Straight through process flows

62. What do you mean by workspace or studio in the context of Pega? What are the different types of workspaces offered by Pega?

Ans: In the workspace, there are specialised functionalities and tools to work. With different workspaces, we can manage and develop our application. In the Pega platform, there are four role-based authoring workspaces called Studios

  1. App Studio
  2. Dev Studio
  3. Prediction Studio
  4. Admin Studio

With the help of studios, we can enhance productivity and speed up the application process by providing role-based capabilities to users. 

63. What is meant by a Data Page in the Pega Platform?

Ans: In the Pega platform, the data page helps to recover data from a stated data source and  it caches the same within the memory. Moreover, a data page controls the data source integration, isolating business actions from this integration.

64. Distinguish between Utility and Activity in Pega.

Ans: In Pega, Activity is helpful to automate the process and also useful to configure the system to automate claim uploads. It is also possible to do without the intervention of the user.

An activity consists of sequential steps that execute in the order of instruction. 

Similarly, in the Pega platform, utility is useful when a user calls the Activity in a flow.

The utility is a form in a Pega flow, whereas Activity is a rule or instance of the Rule-Obj-Activity rule type. 

65. Distinguish between the terms obj-open-handle & obj-open in Pega.

Ans: Obj-open:- Within the obj-open term, a user will get many records out of the table as per the basis from the specified class. Also, it opens as a case or an instance of a class given.

66. How can you connect with multiple Pega applications?

Ans: We can connect with many Pega Apps using SOAP, HTTP, MQ, and JMS.

67. How can you check an activity's local variables' values?

Ans: We can check these values of an activity using the log message.

68. Which table will you use to add a note in the Pega platform?

Ans: The following is the table used to add a note in the Pega platform-

pc_data_workattach

69. How do you finish the work object within the Activity?

Ans: To finish the work object in the Activity, we use JavaScript.

70. Distinguish between Edit Validate and Edit Input rules in the context of Pega.

Ans: 

Edit Validate rule- The edit validate rule is helpful to validate the value of property through Java code. Further, these rules are helpful for property-validate, Rule-Obj-Activity, etc.

Edit Input rule - These rules help convert the data entered by the users into the format required.

71. Where do you store the work objects in Pega?

Ans: By default, the work objects are stored within the pc_work table. Further, if you wish to keep these objects under a user-built table, you can do the following-

  • Create a schema that is similar to the pc_work table.
  • Alter the group mapping of a class to a new table created earlier.

72. Define StepStatusGood and StepStatusFail rules in Pega.

Ans: The rules StepStatusGood and StepStatusFail are used when they check the pxMethodStatus property value as "Good" or "Fail." It is when the condition is defined within @baseclass. 

Conclusion

Dear readers, we at HKR commit to provide quality and reliable sources at all times. In this post we have provided the curated list of interview questions prepared by our experienced faculty members. If you are going to face an interview, these questions might help you sail the interview easily, prepare yourself and get through with the knowledge before going to the interview. Stay tuned to our website for more valuable content. We wish you all the best for your interview.

Comments

Post a Comment

Popular posts from this blog

Split For Each shape in pega - Parallel processing in Pega

Image
  Split For Each shape in pega Parallel processing in Pega We can allow users to perform multiple tasks independently to complete the work, in pega we can this as parallel processing. In a stage or flow rule, we can add smart shapes to achieve this parallel processing. Smart shapes in pega Pega has defined some smart shapes like  Split Join ,  Split-For-Each,  and  Spin-Off . We have to use these smart shapes in sub-process shape. Each shape can call one or more processes to proceed in parallel. Split For Each shape in pega Split for each allows us to run a single process multiple times by looping through a Page List or Page Group. The main flow continues when processes on the PageList/PageGroup processed. I Will explain with an example:  In a Service Request case type when the user submits a request it should be going for the inspection process. Used Split Join shape to fulfill this requirement with two sub-processes. When all sub-processes are complete, t...
Read more

Queue processor FAQ

Image
  Queue processor FAQ A queue processor rule is an internal background process that you configure for queue management and asynchronous message processing. Use standard queue processor rules for simple queue management or low-throughput scenarios, or use dedicated queue processor rules for higher-scaling throughput, and customized or delayed processing of messages. Best practice is to configure queue processors instead of using standard agents to manage message queuing in Pega Platform. For details, see   Background processing best practices . Frequently Asked Questions about queue processors include the following: How do I queue a message to a queue processor? You can queue a message to a queue processor by performing either of the following actions: Use the   Queue-for-Processing   activity method. Use the   Run in Background   SmartShape when you create a case. For more information, see   Queue-For-Processing method   and   Running a backg...
Read more

Tickets in PEGA – its Configuration, Usage & Execution

Image
Tickets in PEGA – its Configuration, Usage & Execution   What is Ticket in Pega? Tickets are rule instances of class   Rule-Obj-Ticket . A ticket (available under   Process   Category) can be used to jump to or go to another part (either backward or forward) of the current sequence of execution Tickets do not have any processing logic. Why do we need Ticket? In a flow processing, case usually flows through a pre-defined sequence of events. However, there may be certain exceptional scenarios where we need to leave the regular sequence of event and process an exceptional sequence. Tickets are used to process out-of-sequence events. Tickets are entry point to a flow to handle any errors or exceptions or events defined by the user. Business Scenario Let us assume that OSP has a loan processing   application   and the sequence of events is as below: Client applies for a loan by submitting appropriate documents Loan officer reviews the documents and approves ...
Read more