Application Context, Ruleset, Checkinout

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 24

Understanding Application context

FYI… App context can be chosen while creating the rule


While Creating rules

1. We can create rules in Implementation class and Imple App context


2. We can create rules in FW class and FW app Context
3. We can create rule in Org class with either FW app context or Impl App context.
4. We can create in FW classes with Impl App Context.
5. We can NOT create rules in Impl Class with FW app context.
 Here Context defines the Scope.
 If we create a rule in FW app context, it will be accessible to FW App, classes and Impl App,
Classes.
 If we create a rule in IMPL app context, it will be accessible only with in IMPL app and classes
but not in FW app and Classes.

Rule Set
Rule set like container of Rules. Which allows us to perform versioning of Rules.

A Rule set allows a developer to create rules in different versions.

Rule set gets associated with a Name and Version.

When we create new application PRPC has created multiple rule sets. Each of them have initial
version 01-01-01.

Versioning Increment Order will be like bellow.

01-01-01, 01-01-02, 01-01-03 ……. 01-01-99 , 01-02-01…… 01-99-99, 02-01-01 .. 99-99-99.

Example 01--09-50

01  Major Version

09  Minor Version

50  Patch Version.

How to create a new version of an existing rule.

If we have customer details section in Versions 01-01-01, If we want to modify this for next
production release, make sure we Save As this rule to Next version 01-01-02 and modify.

Now, Customer Details section is in two version In production, 01-01-01 and 01-01-02.

At Run time PRPC always tries to pick latest version.


Rule Sets are called or referred from an Application rule Form

First Open Implementation App


Here

1 and 2 are called as Implementation App rule Sets.

3 and 4 are called as Organization Rulesets.

Now Open FW Application

Here
1 and 2 are FW App Rule Sets.

3 and 4 are Organization rule Sets.

Here 3 and 4 are common to Impl and FW applications.

Implementation and FW application can access Commonly Organization rule Set Rules.

Validations

1. Application Validation 2. Rule Set Validation.

Application Validation

Open any Rule Set


An Application Validation (AV) mode ruleset can reference all rules in a ruleset that is defined in the
same application or a ruleset that belongs to any built-on application.

Rule Set Validation Mode

This option requires that you specify prerequisites. The Required RuleSets and Versions section is
enabled for this mode and can be modified or deleted.

When rule Set Validation mode is Selected, current rule set can not access other rule sets even
through other rule sets are related built on application. Those Built on application rule sets must be
mention in Pre requisites.
Recommended is Application Validation mode which has been introduced from Pega 7 onwards.

How to Create a New Rule Set Version


Creating New Version 02 for Organization rule set.

Open Organization Rule Set.

Click on edit icon against Organization Rule Set


Click on PLUS icon to add new version
Save.

For this moment onwards when we create rules in Organization rule set. PRPC displays two versions.

Done.

How to create a new developer Operator


To create an operator , we can open the existing operator and save as that.

Open current operator

Save As this
Save. Done.

Check in – Check out of Rules


Check in / Check Out prevents Parallel Development.

By Default the Rule Will be Without check in- Check out feature.

To Enable Check In/ Check out for all rules follow below steps.

Open the rule set.


Go to security tab

Select Use Check out.


Save.

Now Open Any rule,

We see check out button. That means rule is in “check in Mode”

Click on Check out to edit the rule.


Now , we can see Save Button. That means after modifying the rule, we can save the changes and
check in back.

Now Try to Open and check out the same rule with other developer ID.

Click on check out


Status—
Check Out failed. Original Record already locked by AdminImpl@allstate.com on
20190214T230758.338 EST

DONE.

For all rule sets of all applications, This Check in / check out feature should be enabled.

Locking A Rule Set Version:-

Locking a Rule Set Version prevents Create, Update and Deletion of rule in that specific versions.

Locking 01 Of Org Rule Set.

Before Locking, if we create any rule in Organization rule set, it displays Version 01 and 02
Let’s lock version 01.

Expand Version 01
Click on lock and save.

Before we lock a rule set version make sure, all the rules in the version are checked in.

Click on tick mark beside search to see all the check out rules.
To check in all these rule at a time

Click on Bulk actions.

Select All
Enter some text in Bulk Prefix Field and Click in Insert.

Click on start to start check in process.


Close.

Now come back to rule set version

Click on lock and save.


Submit

Save. Done

Now If we try to create a rule, PRPC will show only 02 Version.


Version ONE is Locked.

Done.

You might also like