Support Article
BadClassDef errors observed in production only
SA-11399
Summary
After migrating your application to production, an activity called by an agent produces bad class definition errors. This is only observed in production.
Error Messages
WARN - Unable to load RULE-OBJ-ACTIVITY CUST-EXAMPLE-INT-WORKCLASS MYACTIVITY #20150128T070123.456 GMT due to
Database-BadClassDef Cust-Exampl-Int-WorkClass; This may cause the wrong rule to run during rule execution.
Steps to Reproduce
Refactor classes and migrate application to higher environment to observe the issue.
Root Cause
The root cause of this problem is a defect in the application rules.
The activity had a privilege class on the security tab that was incorrect; it specified a class that did not exist
Resolution
This issue is resolved through the following local-change:
Update the privilege class to be the same as the class name of the activity.
Published July 10, 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.