Question
VOIS
IN
Last activity: 4 Oct 2018 13:54 EDT
Unable to delete a rule.
Hi All,
I want to lock a ruleset 01-01-03 for QA deployment, when i am trying to lock a ruleset, in that one rule is checked out, when i opened the rule. It is saying. "There has been issue;Please consult your system administrator"
Can you please let me know, in this senario, how to checkout the rule.
Thanks,
Shweta
***Updated by moderator: Lochan to add Categories***
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Accepted Solution
Accenture
IN
Hi Everyone,
@Shweta: This issue might be resolved for you. But please find the solution below for future reference.
Reason:
The above problem usually appear when we delete /delete checkout one rule, but accidental pressing continues <-- (Backspace button), server slowness or some other technical issue the rule got corrupted.
Solution:
1- Create an Activity
2- Open the object (obj-open) , pass the class name and rule name
3- Call apply-datatransform method call "pzPreDeleteChecOut" ,check Pass parameter
4- Property-Set for setting the action Param.action = "deletecheckedout" and param.memo = "<Anything>"
5- Call apply-datatransform method call "pzSetRMAction" ,check Pass parameter
6- Call ProcessRMAction , check Pass parameter
Run the activity.
J.P. Morgan Services India PVT Ltd
IN
HI Shweta,
Please go through this link. It might help.
https://collaborate.pega.com/discussion/remove-duplicate-values-pagelist-using-same-pagelist
Thanks,
Neha
Blue Rose Technologies GmbH
BE
Hello Shweta,
Please have a look on the below link :
https://community.pega.com/support/support-articles/unable-delete-private-checkout-rules
Let me know if it helps.
Infosys
NL
Hi Shwetaaa,
This issue we have faced few times. I'm not sure about the root cause of this but I've noticed I can access the rule when I use a different node in same environment. So it might be some node specific cache issue. As an escape route you can either delete this rule using an admin activity or executing a delete query in database directly if you have the permission.
Thanks
Sumit Kumar Bhowmik
Pegasystems Inc.
IN
Hi
Can you check your tracer or log to see what is going wrong and share your observation ?
Pegasystems Inc.
IN
You can login with the person who has this rule checked out and use bulk actions to delete check out if rule is not opening directly.
Let us know if this helps.
Areteans Technologies
AU
Do Revalidate and save of that particular rule. It might be corrupted
Capgemini Sverige AB
SE
Hi Shweta,
There should be unlock option in Actions tab of that rule, you will be able to delete that once you unlock it.
Srini
Capgemini Sverige AB
SE
You should login with the same credentials to whom it had checked out.
VOIS
IN
Hi All,
The rule is no longer exist and got corrupted. I do not have database access where i can delete the rule record neither pzInskey of the rule. In this senario any advice to delete the rule.?
Thanks,
Shweta
BlueRose Technologies
AU
Hi Shweta,
Please use connect-sql rule for deleting the corrupted rule on giving pzInskey from pr4_rule. Let me know, if anything else required.
Thanks,
Prudhvi
Pegasystems Inc.
US
Hi Shwetha,
@Prudhvi_N, We cannot create Connect-SQL on internal tables.
@shwetha, Can you please let us know if you have tried to know who checked out the particular record and ask them to check out or discard the rule.
If you can't find them, I'm afraid you'll have to delete the rule entry in pr4_rule and also delete the same from the table pwbv4_rule_locking. All checked out rules are present in the user specific ruleset. The ruleset of the checked out rule will be operator ID. Using the above statement we can find the checked out rule and delete it.
BlueRose Technologies
AU
Hi Chatr,
We have to delete the rule entry from pr4_rule_property table, not pr4_rule. Under circumstances, we can use connect-sql for internal tables as well.
Thanks,
Prudhvi
Pegasystems Inc.
US
Hi Prudhvi,
Just wondering, did Shweta mention that the corrupted rule is a property? (If she mentioned that the rule is a property I'm pretty sure there is some problem with PDN loading comments in my login). Coz, only property rules will be saved under pr4_rule_property table. As the size of properties, flows etc are large, for faster query execution we save some rule types in separate tables rather than pr4_rule. If the corrupted rule is a property, then yes, we have to delete it from pr4_rule_property table.
Now, coming to the connect-SQL rule, They are meant for external database tables. Yes, we can create the connector directly using the create menu on internal tables and we can execute them. But that is not a recommended approach. If you use connector and metadata wizard to create the connector, it will not allow you to create the connector on tables which contain keys starting with px,py,pz.
Please go through the following help document where the use of connect-SQL is provided (https://community.pega.com/sites/default/files/help_v721/procomhelpmain.htm)
Areteans Technologies
AU
Hi did Revalidate and Save didnt work ?
Tata Consultancy Services
US
Hi,
Try clearing up the cache and do a 'revalidate and save'. If doesn't work check the error/exception in the tracer.
Inovar
SA
Please try it in a private window. It may be because of cache.
VOIS
IN
Hi Thanks all for providing the answer. I have tried the below approaches:-
1) I have tried "revalidate and save" option.
2) tried login with the same user who has checkedout the rule but no luck as rule doesnt exit. Getting below error
There has been an issue; please consult your system administrator.
3) This is a report defination rule.
Thanks
VOIS
IN
Hi Thanks all for providing the answer. I have tried the below approaches:-
1) I have tried "revalidate and save" option.
2) tried login with the same user who has checkedout the rule but no luck as rule doesnt exit. Getting below error
There has been an issue; please consult your system administrator.
3) This is a report defination rule.
Thanks
Areteans Technologies
AU
Hi Shwethaa,
Raise a Pega Product support SR for the same
Pegasystems Inc.
IN
Hello!
Let us know if you do log an SR for this and its ID. That way we can track it and follow-up this discussion with the resolution.
Regards,
Lochan | Community Moderator | Pegasystems Inc.
Accepted Solution
Accenture
IN
Hi Everyone,
@Shweta: This issue might be resolved for you. But please find the solution below for future reference.
Reason:
The above problem usually appear when we delete /delete checkout one rule, but accidental pressing continues <-- (Backspace button), server slowness or some other technical issue the rule got corrupted.
Solution:
1- Create an Activity
2- Open the object (obj-open) , pass the class name and rule name
3- Call apply-datatransform method call "pzPreDeleteChecOut" ,check Pass parameter
4- Property-Set for setting the action Param.action = "deletecheckedout" and param.memo = "<Anything>"
5- Call apply-datatransform method call "pzSetRMAction" ,check Pass parameter
6- Call ProcessRMAction , check Pass parameter
Run the activity.
Adqura
IN
We had similar issue as some of the rules got corrupted. Since we wanted to use the same name as the rule was being referred in multiple places, we had to delete and recreate the rule. We wrote a simple activity with following steps to delete the rule.
1. Open the object (obj-open) , pass the rule name and class name of the rule instance type for example to delete a data flow open class Rules-Decision-DDF
2. Obe-Delete
Attached a screenshot for reference..