If you get the following exception despite that no policies are defined for your event you might read this tech doc to learn how to look for left over policies in the run time database and delete them:
Error building data for matching events
Policy Xpress will trigger policies that are stored in the object store. If you result in the exception below and do not believe you have a policy defined you might want to conduct the procedure below to check for your object store data integrity:
Error building data for matching events at com.ca.identitymanager.policyxpress.engine.PxProvider.getPoliciesForEvent(Px Provider.java:136) at
Once the event is executed it is looking up the database for a policy and if it finds one it will fire it up. This info is stored in two tables in the IM Object Store database:
The PX_When table has 6 columns. Two of them are called: EVENTNAME and POLICYUN. The EVENTNAME holds the name of the event and the POLICYUN references a policy object from the PX_Policy table. We would like to check if there is a dangling reference between the tables where the PX_When is pointing to a non-existent PX_Policy object. This might have happened during a previous delete. If such a dangling reference exists it might explain this failure because the policy object will not be able to be constructed resulting possibly in this NULL pointer exception. If such a dangling reference exists we should be able to clear it manually.
Here is what you should do: