When you (or another developer) cannot update a rule that
you expect to be able to update, use this topic to identify
possible causes.
Show all
Do you
need to check out the rule first?
Diagnosis
|
Action
|
If a rule form contains the read-only mark
() and
the Check Out toolbar button () is active,
you must check out the rule to update it.
|
Click the Check Out toolbar button () to check the rule out to yourself. You
can update the checked-out copy.
|
Is the
rule already checked out?
Diagnosis
|
Action
|
If a rule form contains the read-only mark
() but
the Check Out button () is not
active, the rule may already be checked out. A lock
icon () appears at
the top right of the rule form.
Click the + character at the upper left of the form
and review the panel that appears. Examine the
Checked out by field.
|
If the rule is checked out to yourself, click your
Operator ID (in the Checked out by
field) to access your checked out copy.
If the rule is checked out to another developer, you
cannot proceed until that developer checks the rule in
(or deletes the rule from his personal RuleSet).
|
Can you
update rules in the RuleSet version?
Diagnosis
|
Action
|
Note the RuleSet and version that appear in the
upper right of the rule form.
Click your name on the navigation area to open your
operator profile. Locate the RuleSets list area.
Confirm that a matching RuleSet and version (or version
prefix) appears in the RuleSets list.
|
If the RuleSet version (or a higher version, or a
prefix) does not appear on your RuleSet list, you
cannot update the rule.
(Class rules and a few other rule types do not have
versions.)
|
Is the
RuleSet version secured?
Diagnosis
|
Action
|
Examine the RuleSet version instance corresponding
to the RuleSet version of the rule. Locate the
Lock this Version? box on the
Security tab.
|
While Lock this Version? is
selected, no one can update this rule.
|
Is the
rule a Process Commander standard rule?
Diagnosis
|
Action
|
Rules in the Pega-ProCom,
Pega-RULES, Pega-IntSvcs,
Pega-WB and PegaForecaster
RuleSets are standard rules; these form the
Process Commander infrastructure and are locked.
|
You cannot update standard rules. (In many cases,
you can copy the standard rule into an application
RuleSet and update the copy.)
|
Are you
permitted to update rules of the type?
Diagnosis
|
Action
|
Open the profile display. Examine the Access
Roles list.
Which rule types you can modify is determined by
Access of Role to Object rules (and sometimes by Access
Deny rules) based on your access roles.
|
If your access role list includes
PegaRULES:SysAdm4, you can update rules of
any type. If your access role list does not include
that rule, you may not have the ability to update rules
of that type. Use an Explorer to list all Access of
Role to Object rules that have your access role as the
first key part.
Open the rule for the rule type (if any) and examine
the Modify value. If the
Modify value is empty, or contains a
production level value higher than your system
production level, you cannot modify the rule.
|
Is the
rule locked by another user?
Diagnosis
|
Action
|
You cannot update a rule while it is locked by
another user.
|
Normally, rules are locked only for at most a few
seconds, such as during the Save operation. If you
suspect this cause, wait and try again. Only the
operator holding a lock can release the lock.
The Locks report lists which operators hold what
locks. Select View > System > Locks
from the Developer portal menus to produce this
report.
|
Troubleshooting