Error when saving rule to database using moving rule refactoring

General
, ,
1

Hello,

I want to move the a rule and when I execute the actual moving action, the system simply shows the error that the corresponding couldn’t be saved to the database. Please have a look at the attached screen shot.

Please advise in which log file I can look into in order to analyze this issue further and get it resolved?

As of now I haven’t found the issue in the follow log file using Configure - System - Operations - Logs:

Appender File (click to view)
SECURITYEVENT /opt/tomcat/work/Catalina/localhost/prweb/PegaRULES-SecurityEvent.log
ALERTSECURITY /opt/tomcat/work/Catalina/localhost/prweb/PegaRULES-ALERTSECURITY.log
PEGA /opt/tomcat/work/Catalina/localhost/prweb/PegaRULES.log
ALERT /opt/tomcat/work/Catalina/localhost/prweb/PegaRULES-ALERT.log

Best regards,

Tadeusz

2025-01-24_10-24-34.png
2025-01-24_10-24-34.png1292×141 7.16 KB

2

I found the solution:

  1. You open the System Log file: Pega - Look at the mentioned log file above
  2. You remove your Operators Name in the field: “Filter By”
  3. You set the value 5000 (initially it is 500) in the field: “Lines per Page”
  4. Navigate to the last page (=highest number)
  5. Navigate backwards till you find the exception which is mentioned in the moving rule UI
  6. You see the corresponding stack trace in the log an you can do further analysis.

As a reference please have a look at the full stack trace the exception I received when using the moving rule functionality.

Exception_Moving_Rule_HomeMain.txt (22.5 KB)