Support Article
Pega log files SLA error
SA-11491
Summary
User is facing an issue with the SLA attempting to run unnamed escalation activities when a Service Level rule does not want one executed.
On the surface, it seems as though the “callActivity” at line 133 of the Java, step #19 (rule name: ExecuteSLA) code is what is being called. The exception suggests the name of the activity being called is empty.
Error Messages
2015-06-11 02:59:22,014 [ PegaRULES-Batch-4] [ STANDARD] [ Admissions:01.01.20] ( internal.mgmt.Executable) ERROR - Activity name not specified for execution in arguments: {pyClassName=SG-Admissions-Work-ExternalRequest-Info, pxObjClass=Rule-Obj-Activity, pyActivityName=}
java.lang.IllegalArgumentException
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3171)
at com.pegarules.generated.callActivity_071001_KhcknoEKbSvWlpqH0tlTMw.callActivity07_10_01(callActivity_071001_KhcknoEKbSvWlpqH0tlTMw.java:122)
at com.pegarules.generated.callActivity_071001_KhcknoEKbSvWlpqH0tlTMw.invoke(callActivity_071001_KhcknoEKbSvWlpqH0tlTMw.java:82)
at com.pega.pegarules.generation.internal.library.LibraryRuntime.resolveAndinvokeFunctionViaReflection(LibraryRuntime.java:133)
at com.pega.pegarules.generation.internal.library.LibraryRuntime.invokeLibraryRuntime(LibraryRuntime.java:110)
at com.pega.pegarules.session.internal.mgmt.Executable.invokeLibraryRuntime(Executable.java:8545)
Steps to Reproduce
Configure SLA without activity, it tries to run un-named escalation activities when a Service Level rule.
Root Cause
The root cause of this problem is a defect in Pegasystems’ code/rules logic in step 19 of the ExecuteSLA activity when evaluating blank Goal or Deadline escalation actions.
Resolution
This issue is resolved in Pega 7.1.6 release.
Published July 29, 2015 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.