![]() ![]() There are rules to accomplish almost anything you need to do in creating an application. The Pega based product has a little more than 180 specific rule types. These two rule types are just the tip of the iceberg. There many types of rules in Pega they are referred to as “Rule Types.” We have actually already referenced two rule types in the example above. We referenced a Property rule (for creating a new piece of data) and an Access When rule (for controlling who and when the new field can be used / accessed). (this type of setting cites a completely separate rule. The secondary rule has all the necessary configurations to manage the details of the need in this case, security and access to data)īy creating this rule and setting its configurations you would have created a new field for the application. No coding, just rule creation and rule configuration. Leverage an Access When rule to control who and when the field is presented and available ![]() (this provides a drop down list which limits the choices available to the end user) Set values for the drop down to: Potential, New, Loyalty, VIP (this provides the ability to set a drop down list for selectable values for the property. This would limit a user’s choices to only those values you allow) (there are other configurations for data types - Boolean, Currency, Number, Date Time etc) Meaning, you would set its configuration to fulfill your needs. You could: You would create a “Property” rule named CustomerType and then you would configure the rule. In a typical application this would be done by going into the database and adding a new field (inserting a new column in a table). In Pega you create a new instance of a specific rule RULE type (a Property rule). Let’s assume you want to be able to categorize your customers in more fine ways so you can more easily target your services and marketing. Let’s say you need to create a new field for customer type. In Pega the creation of a new piece of data is accomplished via the creation of a rule. In addition, one of the key, and powerful, methods of configuring a rule is to leverage a separate rule. A great deal of building an application in Pega is about creating rules which reference or leverage other rules. Each type of rule has specific settings / configurations which can be selected or set. So, creating and configuring a rule is about filling out a set of forms. The first question becomes, what is a rule in Pega. The best description available is this: ![]() It’s architectural design is all about managing processes via computer software. Pega accomplishes this feat via Rules. Pega is a rules engine which is specifically designed for creating BPM applications. In fact, the key to understanding Pega is understanding Rule Types. However to explain all of this we first have to explain and make clear the concept of a rule. Instead, creating an application is done by visualizing the business contexts, diagramming processes and creating instances of specific rule types (lots and lots of rule instances of many different types). Yep, it’s true. Creating a new custom application with Pega is done without creating a database, without inserting new columns, no relating one table to another and without hand writing lines of code. Without writing line of code followed by another line of code.Without relating database tables to each other.Applications created in Pega are created: So, let’s start with the most mind boggling portion of Pega. This question is often followed with a, “yeah, but what is it and how does it work?” There is a fairly common reaction to this description when it is supplied to someone new to BPMS and or Pega. The above description is the typical description of Pega. Pega, originally know as PRPC (PegaRULES Process Commander), is an application development language which is non-linguistic in nature. Meaning, it is an application development language and platform which is used to create computer software. It is “non-linguistic” because you don’t write lines of code. Instead software is created in Pega via visual designs, rule creation and configuration. you don’t understand what I’m saying (funny how that works). because if you don’t understand what I’m saying. In fact developing a new application in Pega is mostly about creating rules which then leverage other rules. Fundamentally that approach is about rules, Rules, RULES and RULES. Over the years I’ve watched people struggle with learning and understanding Pega. The struggle is not only about understanding the concepts but also coming to terms with Pega’s approach. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |