Pega Sandbox

Hi, in this tutorial, you will learn how to create a SOAP in Pega. To do so, we are going to use the service creation wizard. In dev studio, click on Configure > Integration > Create SOAP Integration  . It will open up the wizard. The first step is to provide the WSDL URL, which is the address where the XML document describing a web service can be accessed.  For this example, we are going to use the following WSDL: http://www.dneonline.com/calculator.asmx?WSDL. We click on next, and it will show the service name, port name, and endpoint. It will give us the option to test and select the operation name. When we finish testing, we click on next. Then it will show the integration layer, it will show the name of the integration, the class, and the context there, where we can define the class where this integration will be created, as well as the rulesets. We can click on preview records to check the rules that the wizard will be creating for the integration. It will show all...

In Pega you can create a data type as an external system of records. We can accomplish that using the wizard of Pega. This is the best way to create an external data source, because the wizard creates the connector, the data object, and the data page with all the configurations to make the connection to the external system of records. For this example, we are going to use a free api to source a list of the countries of the world. You can watch step by step the creation of the data source in the following video .

  Connector: A connector defines an outbound request to the service, and a connector establishes a connection to an external system by using common HTTP methods such as SOAP(Simple Object Access Protocol) or REST(Representational State Transfer). Connectors pass application data through a mapping rule with the required and optional parameters, and are in charge of mapping the response from the service to the application. How to configure the call of the connector: The connector can be called from an Activity, Data page, etc The most recommended use of a connector is a data page. On the data page, you can set up, through a data transformation, the mapping for the request data responder, and it can be called from anywhere in the application . Let's get this process through the steps : Map data to the integration : you can create a data transform to map the data from the clipboard to the service Invoke the connector : the connector can be invoked from a data page, data trans...

Connector and services: Applications often establish connections with external systems to exchange data needed to allow users to complete a task; these connections use standard frameworks to exchange information between systems . For example, an application for car insurance wants information about a car to provide insurance, so it connects to the DMV to get information about the driving history, and based on that, gives them a quote for the insurance A connection between systems consists of two parts: a connector to initiate the request and a service to fulfill the request. Connector: A connector defines an outbound request to the service, and a connector establishes a connection to an external system by using common HTTP methods such as SOAP(Simple Object Access Protocol) or REST(Representational State Transfer). Connectors pass application data through a mapping rule with the required and optional parameters, and are in charge of mapping the response from the service to the app...

Keyed data pages are used to avoid querying the database every time a user interacts with the application. Instead, they cache the information within the case, so whenever the data is accessed, it is already preloaded on the case clipboard. This makes the application more efficient and reduces database hits. When to use keyed data pages   In my experience, the most common use of keyed data pages is for dropdowns and sometimes tables. The Pega CSSA course provides examples of when to use this type of data page. From my perspective, keyed data pages are ideal when you need to filter data. You send the parameters for the data, and the keyed data page returns a filtered list based on those parameters.  Sometimes i encountered scenarios where you need to query data form an external database, and making queries every time that we change a parameter can affect the preformance to the application, this could impact directly on the user making the interface slow and could lag somet...

  Edit validate rules: Edit validate rules help us obtain the requested information in the correct format. For example, you request the SSN and you need that information in the following pattern ####-####-####, so you use an edit validate rule to ensure that the user is entering the information in the correct pattern. This configuration we made at the property level, on the advanced tab, we can define the edit validate rule for that property Pega already has edit validate rules OOTB, but in the case that you need to customize a pattern, you can do it using a Java function to create the pattern and the validation message when the pattern is not met. How to configure edit validate rules: In this video i explain step by step how to configure an edit validate rule in a porperty

Hi Everybody, im about to get my Pega Senior System Architect certification, and I would like to share with you my exam preparation and strategies to pass the exam. I started to analize first the exam blueprint, which you can find at the following link . i chose version 24.2 because it's the last available version of Pega. In the blueprint, we can find the topics and the percentage of questions that will be on the exam. Based on that, I did my math (Well ChatGPT did ), and came up with the following strategy to pass the exam. Exam Overview (From Pega Academy) Number of Questions: 60 Duration: 1 hr 30 mins Passing Score: 70% Platform Version: Pega Platform ’24.2 Prerequisite: Must already be a Certified Pega System Architect  Pega Academy Topic % of Exam   Approx. # of Questions Application Development 28%      17 Case Management 15%      9 Data and Integration 19%      11 User Experience 5%    ...