Edit Input

This is used to convert a value from one format to the other.

This mainly uses JAVA code to perform the conversion. The JAVA code always appends {return theValue;} to the code.

It is of type Rule-Edit-Input.

Some of the built-in Edit Input rules in PEGA are,

DateTime-Calender  à Converts the JAVA date to a standard Date format.

toUppercase  à Converts the received text to UPPERCASE.

appendDash  à Appends a Dash (-) at the end of the text

Example Edit Input Rule

It is referred mainly in Property rules under the Edit Input option of the Advanced tab.

Creating an Access Group:

On Selecting Access Group from Security, a new Pop-Up will be displayed.

Provide a new Access Group Name,

An Access Group is created like the one below.

Creating an Application

On Selecting Application from Application Definition, the below screen will be Popped Up.

Provide a Name and Version for the Application

Click on Create

The Application Created will be as below,

Specify all the Application Rule Sets that will be used in the Application.

Rule-Obj-FieldValue

Field Values rules (Rule-Obj-FieldValue) are mainly used for supporting localization by overriding an english word or a sentence in other supported languages.

Provide a value in the Localized Label field ( No data available as above). This is the value that will be changed to other languages as required.

References:

1)      Referenced in Property rules as below,

Some of the standard Field Value rules:

pyStatusCustomerStat à Localizes customer satisfaction status. (Used mainly for frameworks like CPM)

pyActionPrompt à Localizes the Flow Action names.

pyCountry à Localizes Country names.

Standard Library functions for localization:

getLocalizedValue() àReturns the localized value of the property.

getLocalizedText() à Get the localized text for the proeprty specified.

Other standard PEGA rules for Localization:

GetLocalizedTextForString à Activity

GetLocalizedValue à HTML rule to return the Localized value for display purpose.

Rule-Declare-DecisionTable (Part 2)

Show Conflict:

Conflicts in the decision table will be shown with a warning message along the row.

This means that the row in unreachable. ( Can never be reached )

In the above example, always the steps either 1 or 2 will return the result. This leaves the Step 3 always unreachable. Such rows will be displayed with a warning message when the Decision Table rule is saved.

Show Completeness:

Automatically displays all the possible combination of values, thereby reducing the chances of situations that could result in returning the default/ otherwise return value.

Heading Row:

Each column except the “Return” column corresponds to a property.

Click on the cell to open up a pop-up like this.

Property à refers to a single value property

Label à Label displayed in the decision table rule

Use Operator has the below list of options
=
<
<=
>
>=
!=

Check the Use Range check box to provide Starting and Ending range value for the property.

Rule-Declare-DecisionTable (Part 1)

Decision Table is used to provide an output from one of the several possible outcomes.

Each possible outcome is based on a certain condition/ value of a property or a set of properties.

Can be referenced from one of the several possible PEGA rules:

1.       Flow à Rule-Obj-Flow

2.       Activity à Rule-Obj-Activity

3.       Declare Expression à Rule-Declare-Expressions

Various buttons to add/delete a row/column in the Decision Table.

When we have multiple columns, then each column’s value will be evaluated before returning the value from the RETURN column.

Each row in the decision table acts as an if condition. When one if fails, then the next else if row, with multiple/single column condition will evaluated before giving the result.

Rule-Obj-When

When rule is used to evaluate a logical statement involving comparisons among values of properties.

Conditions Tab:

Value of the properties can be evaluated against any of the comparison operators, like
=
>
<
>=
<=
!=

Advanced Tab:

This functions similar to the Conditions tab with below comparison expressions, like
Equal
Greater
Less
Not Equal
Greater/Equal
Less/Equal

Only difference between specifying conditions in the above 2 tabs is that,

With conditions tab, properties can be evaluated against only similar logical conditions.

(ex: we A and B and C, we cannot have A and B or C )

Whereas with Advanced Tab, any kind of logical expression can be implemented.