50. Learn about Decision Table in Pega (2024)

Introduction

Decision tables derive values that have one of a few possible outcomes, where each outcome can result from a test of a condition that includes multiple variables. A decision table lists two or more rows, and each row contains test conditions, optional actions, and a result.
Decision tables are appropriate for evaluations that include more elements compared to simple true/false evaluations.
#DecisionTable #pega #decisionrules #declare #learnVTHKrishna #cdh

Video

Hello guys welcome back to my Channel.

Today we are going to discuss about decision table and configuration.

Let's get started into the topic, so decision table is one of the declarative rules that are available in Pega.

So if you go to records Explorer under decision, you can see decision, table decision table or in terms of rule declare decision table and there are scenarios like there might be multiple inputs and there might be possibility of multiple reasons for that and we have having a scenario where we need to check many instances like in our general programming language.

If we consider there is like a nested effects, so there are many IFL statements, then we can't sit and write many when conditions and evaluated so overcoming that particular problem that has come up with an approach called as a decision table.

These are the instance of decision driver.

So here let's take a prominent example like gender suppose.

If user has entered F, then we need to set some value to female or if you use as a 2m, then we have to consider that value as a male.

Then, in that scenario you can correlate.

This particular thing decision table is having these many tabs like table results, parameters, pages and classes, test cases, specifications and history First Step, you can see here.

This is like insert a row before and this is inside a row after and this is delete arrow and this is like for column.

So this is row and these are columns, so you can add any number of columns and you can delete those as well and it is insert or before- or this is insert or after- and this is like a set property values so before coming that, so first I have added one column.

So in that column, if I click this you can see, we have to give some property.

This is not a mandatory field.

You can give it so when you are calling this particular direction table for this gender, some value should be set whether it is an more F or other value, so it will conserve that value gender, and this is label of this particular property, and this is range suppose this is a text property, so I am having only these uh operator comparison things equal to less than less than equal to greater than greater than equal to not equal to suppose we are having a situation like where we are using some integer and we are checking some value which is between like 100 to 200, for example.

For those scenarios you can give this uh use rate.

You can see here greater than equal to less than or equal to, okay and in this property.

Also, you can click on settings and you can use a Expression, Builder suppose uh.

There is a scenario where, like uh, you need to truncate some spaces over here then just you can now use substring or some other functions like that see, and you can use those expressions over here.

So it will translate the value and it will start comparing with that, and this is f- and here also, you can give some Expression Builder if required, and this is written value.

So if gender is f, then you want to return as a female as an output from this Json table.

You can give this here and suppose uh.

If it is M, then you want to give as male you can give this.

There is no mandatory to give these quotations in addition table.

Suppose you have added some one row, then it can be considered as one of the probability of output, and this is another probability of output.

Suppose uh, your password is f and it has written it has to written female.

But you want to evaluate all the rows without uh stopping the execution, then, if you go to results and click on evaluated all rows, even though at the first instance for f, it needs to be female.

The execution won't stop here, and here you can see it is concerned as when, when otherwise and now, if I am unchecking, this evaluate at all rows see it has changed to.

If else statement- and the second thing is suppose now, gender value is not f for M, it is like others, then it would be executing this, so it won't return anything.

It won't return anything.

So it will return any because this is a default uh written value and there is something called as set value.

Also I am setting some other property, also like PV node so here, for this instance, I want to set some other notes or something I can use that.

So, while returning from after the execution from this Json level, these two values we can cancel and you want to restrict users to operate these return values.

Then you can click on this, so allow changing values in cell.

Is it everyone or no one or people who are having only privileges certain privileges only they can do.

It means you can add a privilege over here for now I'm, adding as everyone click on Save, and there is an interview question as well.

How can you call a distant table from another decision table so here? If you go and go with call and you click down arrow see, no results are formed, but in the written column, if you just go for call and do go for down arrow, you can see the distance tables that are available in the class hierarchy.

So in this way you can call addition table from another decision table okay and to validate suppose.

This is a small example, but you have built a big decision table and you are not sure like.

Is there any clone, Flex or uh? You have missed anything like syntax servers or like that, so you want to check for that.

You just click on show conflicts see you got a message like that's relation table is consistent.

These show completeness this is complete and you want to export all these conditions when I click on export c1c.

In this way, you can add some relative statement and you can import this as well, and this is result step.

So, as I've said, if you go for a valuator rows, then it would become when condition 1.

This is like allowed to update columns, allow to update rows and allow to change property sets.

So here you can see right results tab.

This is very important one.

So there are two things: hello, additional results when selected property has written the result.

Suppose here, I am giving p y name or something and I can Define over here.

Suppose, if a result is female, I want to add some more properties to the values case, ID for some other property as well.

So when the result is female, you can add more values to the respective result, for the respective instance as well, I can give mail I can give and give so like this once I have defined this click on Save now in table tab.

If you go, you can see, there are return value side.

Just go here and see you can find all the written results now is you can easily change that, for example, I am showing this so in this way, if you are having a big decision table- and you want to set more values for each result, then you go with this option results and you add all the possible results and where, on which property, this result value should be set, and we Define that, and if you want to preset some properties for this relation level, you can go this and you can add your property and your value over here, and this is parameters where you can Define parameters, and you can use the same here with the param Dost, and this is like an option like say property value if you want uh, like the other way around like we have set some nodes over here right this.

In this way you can give.

If you want to add this, you can hide this, and these are the parameters, and these are pages and classes, and this is best cases and test cases.

I would be taking a separate video like how to create a test case uh for a particular applicable rule like addition table when rule or something else.

So this is all about decision table and how actually we can call this decision table.

We can invoke this Json table, so one way is like through an activity so in equity.

If you go to steps and we have a method called as property map decision table, so if you give that there would be some parameters like property name, this is returning something right, this mail, so you want to set this particular mail on a property.

Then you can Define this property name, and this is station table name, and this is allow missing properties Suppose.

There are multiple values like here: only gender you have to pass, but there are different columns where you are deriving a particular result based on three properties, and you forgot to pass values of two properties and not the third one, and if you want don't want to execute the relation table, you can just uncheck this and you want to execute the resistance table.

Even though some values to the properties are missing, then you can go with this checkbox and if you can give the reasonable name, it will remove the decision table and the other way is in flows.

Also, we can invoke addition table, for example.

Here in you can see some decision right.

So, if you add the decision shape, you can go with regression table and you can call the value.

So in this way you can invoke our destination table from an activity or a flow and from data transform.

Also, we can invoke addition table.

We are having a a function called as obtained value.

This is also one of the interview question.

So in this way we can inocitation table and we can configure this destination table hope you have learned a new concept thanks for watching this video.

Please share like and comment your feedback and stay tuned to this channel.

50. Learn about Decision Table in Pega (2024)

FAQs

What is true about decision tables in Pega? ›

In a decision table, the values in a column evaluate against the same property/operator pair, such as Account type = , to return a value or property. Developers can use a decision table when they have to evaluate many combinations of the same set of properties or conditions to return one value or property.

What does a decision table contain in PEGA? ›

Decision tables derive values that have one of a few possible outcomes, where each outcome can result from a test of a condition that includes multiple variables. A decision table lists two or more rows, and each row contains test conditions, optional actions, and a result.

How do you evaluate all rows in decision table in PEGA? ›

Under the Results tab, if you enable the Evaluate all rows option, the decision table evaluates all rows defined in the decision table. If the condition is true, the decision table performs the actions and returns an array of results that can be parsed.

In which situations should you use decision tables? ›

Decision tables can be used in all situations where the outcome depends on the combinations of different choices, and that is usually very often. In many systems there are tons of business rules where decision tables add a lot of value.

What are decision table techniques? ›

Decision table technique is one of the widely used case design techniques for black box testing. This is a systematic approach where various input combinations and their respective system behavior are captured in a tabular form. That's why it is also known as a cause-effect table.

What are the four components of a decision table? ›

The general format of a decision table has four basic parts. 1) Action entry: It indicates the actions to be taken. 2) Condition entry: It indicates conditions which are being met or answers the questions in the condition stub. 3) Action stub: It lists statements that describe all actions that can be taken.

What are rules in decision table? ›

A decision table is a scheduled rule logic entry, in table format, that consists of conditions, represented in the row and column headings, and actions, represented as the intersection points of the conditional cases in the table. Decision tables are best suited for business rules that have multiple conditions.

What is the maximum size of code in decision table in PEGA? ›

Pega Platform does not limit the number of rows in a decision table. However, as a best practice to avoid slow performance when updating the form and also avoid the Java 64 KB code maximum, limit your decision tables to no more than 300 to 500 rows.

How many parts are there in a decision table? ›

A table that indicates actions to be taken under various conditions, the decision being the selection between the alternative actions. Conventionally a decision table has four parts that are named and laid out as shown in Fig.

What is the difference between decision table and tree in Pega? ›

Both decision tables and decision trees evaluate properties or conditions to return results when a comparison evaluates to true. While decision tables evaluate against the same set of properties or conditions, decision trees evaluate against different properties or conditions.

What is the role of decision table? ›

The decision table is a software testing technique which is used for testing the system behavior for different input combinations. This is a systematic approach where the different input combinations and their corresponding system behavior are captured in a tabular form.

What are decision rules in PEGA? ›

Decision means, taking an appropriate action based on condition. Decision rules evaluates conditions and returns required results. When Condition returns true or false. Using other decision rules, the return value can be anything.

What is the maximum number of rows for export in PEGA? ›

As per pega guideline, we should not export more than 10000 row using report definition.

How do you trace a decision tree in PEGA? ›

Debugging decision trees with the Tracer
  1. In the Tracer window, click Settings.
  2. In the Event Types to Trace section, select the Decision Tree check box.
  3. Select the ruleset that contains the rule to be traced.
  4. Clear the other rulesets to avoid memory usage from tracing events occurring in other rulesets.
  5. Click OK.
May 31, 2022

How do you create decision data in PEGA? ›

  1. Configuring the DataSet-Execute method for Adaptive Decision Manager.
  2. Configuring the DataSet-Execute method for Database Table.
  3. Configuring the DataSet-Execute method for Decision Data Store.
  4. Configuring the DataSet-Execute method for Event store.
  5. Configuring the DataSet-Execute method for File.
Jul 5, 2022

What is decision table and how it is useful in testing? ›

Decision tables are very much helpful in test design technique. It helps testers to search the effects of combinations of different inputs and other software states that implement business rules. It provides a regular way of stating complex business rules which benefits the developers as well as the testers.

What are decision rules in PEGA with examples? ›

Decision tree rules contain a list of one or more input properties, and can return a property value as a result. For example, a decision tree can compute and return "today's order cutoff time" as 5 P.M. on most business days, but 2 P.M. if today is a Friday before a Monday business holiday.

What is the difference between decision table and tree in PEGA? ›

Both decision tables and decision trees evaluate properties or conditions to return results when a comparison evaluates to true. While decision tables evaluate against the same set of properties or conditions, decision trees evaluate against different properties or conditions.

References

Top Articles
Latest Posts
Article information

Author: Corie Satterfield

Last Updated:

Views: 5800

Rating: 4.1 / 5 (62 voted)

Reviews: 85% of readers found this page helpful

Author information

Name: Corie Satterfield

Birthday: 1992-08-19

Address: 850 Benjamin Bridge, Dickinsonchester, CO 68572-0542

Phone: +26813599986666

Job: Sales Manager

Hobby: Table tennis, Soapmaking, Flower arranging, amateur radio, Rock climbing, scrapbook, Horseback riding

Introduction: My name is Corie Satterfield, I am a fancy, perfect, spotless, quaint, fantastic, funny, lucky person who loves writing and wants to share my knowledge and understanding with you.