PegaRULES is utilized to streamline the progression of a case or business process, guiding users through various stages and steps required to accomplish a specific task. PegaRULES offers built-in functionality for reporting and provides a basic user interface. It is currently implemented on an older version of the Pega platform, specifically Pega 7.1.7 or 7.2, which may employ technologies, such as Cosmos.

I am an application developer or software developer, and I use PegaRULES for writing down the code for full stack development, starting from the UI to the backend to the database. I write everything down for developing the application for the end users. For example, the end users could be bank employees or employees working for healthcare and insurance organizations.

I have worked with it for multiple use cases, such as insurance, banking, asset management, and oiling. I'm currently using it in banking operations. Before that, I used it in insurance, and prior to that, it was used in asset management.

It's built on the base core product.

Pega provides a lot of out-of-the-box capabilities in terms of rules. You need not write anything. If there is anything that's specific to your company's need, then you'll go ahead and do a "save as" and work on those activities. That said, PegaRULES already provides most of the out-of-the-box activity for sending emails, sending correspondences, or most of the items that you do on general web applications.

Our customers range from banking to insurance to telco. In banking, customers use Pega for marketing, sales management, and onboarding processes as in loan onboarding or customer onboarding. They also use it for customer service, for example, when a customer calls up the bank to handle a payment inquiry or a problem. Pega also handles collections. We also deal with many of the operational processes inside the banks. 

In insurance, we work with Pega on property, casualty, and health. In insurance, we have built underwriting systems, and systems to manage attack claims, as well as the sales and customer management service part.

When it comes to telcos, it's primarily in the marketing area. Besides that, we have customers in the government sector. So, in government sectors, it is primarily to automate many of the citizen services, as well as to automate many other online operations.

It is just for business rules. An example would be that you want to apply for a credit card limit, and if the credit limit amount is less than a certain value, we won't necessarily do a real-time check. We do basically auto adjudication. So, the rules can be used as part of the flow.

PegaRULES is used more for business process management. Perhaps in a bank or any other organization. If you want to automate anything, you may require a tool, which is, simply building the same thing in Java. 

People choose Pega because it's a flow-oriented tool that is already predefined and you can plug and play.

The solution is used in banking, telecoms, and in insurance.

We use the solution as a low-code development tool. The tool has pre-built rules. Hence, they can be reused and configured as per client requirements.

Our customer base is varied, ranging from insurance to banking to government. In the insurance domain Pega is used for things like policy, as middleman management, policy administration and claims administration. In the banking realm, it's used across multiple areas from CRM systems, customer service, sales automation, and things like loan origination, payment investigations and payment arrangement management. In the government sector, it's used particularly as a case management software to manage processes.

Most of our customers are enterprise businesses, we are partners of Pega and our company functions as a system integrator. I am co-founder and Chief Technology Officer. 

We primarily use the solution in claims for our clients in the insurance industry.

We worked with different frameworks and components that Pega offers to build a complex process management solution for a large scale financial institution.

We developed an an underwriting platform for an insurance company. In this project I mainly worked as a senior developer. I have more than four years of PEGA experience in both technical and business consulting. My company is an official PEGA partner.