+ Start a Discussion
Jax.ax1308Jax.ax1308 

Packaged Triggers

I have built a trigger and the test class for a custom object that we added to a managed released package. The trigger is visable under the custom object object but not avalible to add it to the users profile. (Enabled Apex Class Access).

The trigger works perfect in the Dev Org and this is the only thing I can find. It seems like it is installed correctly just not enabled. 

Does anyone have any experence with packaging triggers/classes? 
JayNicJayNic

Triggers do not need to be enabled access to the user profiles. This is because they are guarenteed to run as long as the user has access to the object itself.

 

In short: it's working