Rulesets

Question 1

What are the restrictions for a branch name

Answer 1

1: have to start with a letter, 2: can contain only alphanumeric or dash characters 3: max 16 character long can be

Question 2

What is a ruleset?

Answer 2

• a container - an organizational structure - used to identify store and manage a set of rules - group rules together for deployment - major subset of rules - major aspect in access control, grouping interrelated rules, managing rules and moving applications - an application is comprised of a list of rulesets - a fundamental building block of an application

Question 3

Which rule types does not belong to a ruleset version?

Answer 3

• Application - Class - Ruleset - Ruleset Version - Access of Role to Object - Access Deny - Library

Question 4

What have to be set up to be able to use check out functionality?

Answer 4

• For Operators: “Allow Rule Check out” on Security tab - For Ruleset: “Use check-out?” on Security tab

Question 5

Private edit is good for?

Answer 5

prototyping or test changes a rule that is not available for standard check out.

Question 6

Which privilege is required to do private edit?

Answer 6

pxAllowPrivateCheckout (PegaRULEs:Sysadm4 standard access role provides this privilege)

Question 7

Where can you see all checked-out rules?

Answer 7

Development landing page (DesignerStudio > Application > Development > Checked Out Rules)

Question 8

Where can you see your private edits?

Answer 8

Private Explorer (Checkmark icon on the header)

Question 9

Where can you see checked in comments?

Answer 9

History tab of the Rule

Question 10

How can a privately edited rule be checked in into a locked ruleset?

Answer 10

It’s not possible: We need to select an unlocked ruleset version in which we want to check-in the private edit.

Question 11

What bulk action is doing?

Answer 11

check-in, open, or delete several checked out rules at the same time

Question 12

Rulesets could have prerequisites?

Answer 12

No, ruleset always have at least one ruleset as a prerequisite.

Question 13

System assembles a complete required ruleset version list from …

Answer 13

• All ruleset versions on this list - All ruleset versions listed as prerequisites for those ruleset versions - All lower-numbered ruleset versions of this ruleset and the rulesets included in the same major version

Question 14

Which ruleset you should use as a prerequisite if your ruleset dependent on only Pega 7 base Rules?

Answer 14

Pega-ProcessCommander:07-10-99

Question 15

How you can avoid having to update the ruleset after product updates?

Answer 15

Use 99 patch version

Question 16

Ruleset prerequisites are validated when …

Answer 16

• when we save a rule - at import

Question 17

You have to list all the direct prerequisites and the prerequisites of the parents as well for every ruleset. (True/False)

Answer 17

False, if you save a rule into Delta:01-01-01 which depends on Alpha:02-01-01, and Alpha:02-01-01 depends on Beta:02-01-01, only list Alpha:02-01-01 as a required ruleset for Delta:01-01-01. There’s no need to list Beta:02-01-01 because it is already listed in Alpha:02-01-01.

Question 18

Rule resolution will always check all the versions of the prerequisite rulesets. (True/False)

Answer 18

False, Rules in versions below the major version are not visible to rule resolution. For example, if you list Alpha:02-01-01 that depends on Beta:02-01-01, Alpha:02-01-01 won’t see rules in Beta:01-XX-XX.

Question 19

Ruleset prerequisites are governing

Answer 19

development and import

Question 20

Ruleset list governs

Answer 20

rule execution at runtime.

Question 21

Ruleset prerequisites are validated in runtime as well. (True/False)

Answer 21

False, Because ruleset prerequisites are enforced during development, the system does not need to validate them during runtime processing

Question 22

Where you can see the ruleset list of a user?

Answer 22

Operator menu > Profile

Question 23

Ruleset order in the ruleset list has no importance.

Answer 23

False, The order of the rulesets is important as it is used by the rule resolution algorithm. We generally refer to the rulesets with higher precedence as being “on top” of those with lower precedence.

Question 24

Ruleset list is assembled when you start a case type.

Answer 24

False, The list is assembled during login.

Question 25

Where system starts looking for ruleset references?

Answer 25

The process starts by finding the versioned application rule referenced on the access group of the operator.

Question 26

Privately checked out rules and the personal ruleset is not listed in the ruleset list.

Answer 26

False, If the operator is allowed to check-out rules a personal ruleset is added at the very top of the list. The personal ruleset has the name of the operator ID.

Question 27

A ruleset is typically locked when …

Answer 27

development is finished and the application is moved to the test environment.

Question 28

You can always unlock a locked ruleset.

Answer 28

It is best practice to never unlock a locked ruleset. If changes are required to a locked ruleset, create a new patch version of the ruleset That way consistency is ensured across environments.

Question 29

You can always go back and change an old ruleset version if you have identified a defect.

Answer 29

Development should occur only in the highest version of a ruleset and only that version should be unlocked.

Question 30

A ruleset version can be locked even if some rules in it are checked out.

Answer 30

False, A ruleset version cannot be locked if any rules in that version are checked out.

Question 31

What is Ruleset Stack tab for?

Answer 31

The RuleSet Stack tab on the Application Structure landing page (DesignerStudio > Application > Structure > RuleSet Stack) helps in following the best practices of ruleset locking and versioning. Available functions: Package & Roll Lock & Roll

Question 32

Checked out rules will prevent you to increment a ruleset? (True/False)

Answer 32

True, We can use the Lock and Roll feature to lock and roll (increment) versions in a single step. Before using the Lock and Roll we need to make sure that there aren’t any rules checked out.

Question 33

You should never skip any number when you increment patch number of a ruleset. (True/False)

Answer 33

If the last release built was promoted to testing or production it might be worth considering skipping a few patch numbers reserving those for emergency fixes. For example, consider the following situation. Ruleset version 01-02-04 was promoted to QA and then production. The next release with a few new features is planned to go into production in two weeks. The development of the next release is done in 01-02-10, reserving 01-02-05 to 01-02-09 for emergency fixes.

Question 34

List all tools which help managing rulesets

Answer 34

Copy/Merge RuleSet tool Delete a Ruleset tool Skim a Ruleset tool Rulebase Compare tool

Question 35

What is Rulebase Compare tool for?

Answer 35

to identify differences in the rules on two different systems

Question 36

What is Skim a Ruleset tool for?

Answer 36

collects the highest version of every rule in the ruleset and copies them to a new major or minor version of that ruleset on the same system, with patch version 01. Consider a skim for each major application release.

Question 37

What Detele a Ruleset tool for?

Answer 37

allows us to delete an entire ruleset or a specific version of a ruleset. Consider the effect before of deleting rulesets that has been promoted to production.

Question 38

What is Copy/Merge Ruleset tool for?

Answer 38

to copy rulesets and ruleset versions into new versions or to merge several ruleset versions into one version.

Question 39

What is Lock and Roll tool for?

Answer 39

lock and increment versions in a single step

Question 40

What is Package and Roll tool for?

Answer 40

to package and prepare the ruleset to copy to another server