pyRuleExecutionMessagesLogged does not return current logs
The pyRuleExecutionMessagesLogged activity is not returning results for today. The latest results are always from yesterday.
Steps to Reproduce
- Create a new user and access group.
- Set Rule Security Mode to WARN on access group record.
- Login as new user and create a new work object.
- Run the pyRuleExecutionMessagesLogged activity again and look for warnings.
A defect in Pegasystems’ code or rules causes this issue. The pyRuleExecutionMessagesLogged activity only scans logfiles that specifically have the string "log" in the name. When using a dailyRollingFileAppender, the current day's logfile does NOT have "log" in the name (in the typical confirguration). This is only added once the file is rolled.
Perform the following local-change:
Modify the pyRuleExecutionMessagesLogged activity to find logfiles of your particular naming convention.
Alternatively, update the prlogging.xml file to fit the name search performed by the pyRuleExecutionMessagesLogged activity.