Is it possible to move a triggers such as BeforeDelete to a workflow or process? What would be the best/most optimal design for such a case? Process objects are triggered on creation and edit, but I would need one that just says delete. I also tried to scope moving the effort to workflows but did not see a way to move the logic to workflows either.

closed as unclear what you're asking by dphil, Eric, Sergej Utko, Chris Duncombe, crmprogdev Mar 21 '15 at 14:38

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • I have thought of a batch process, but is there a better way? – amanda fouts Mar 20 '15 at 18:09
  • Your question doesn't make sense. Can you please elaborate? – the_phantom Mar 20 '15 at 18:27
  • Triggers can only be moved to workflows if the trigger should have never been written in the first place (Click not code). A trigger is meant to provide different functionality than a workflow would for the most part. – Eric Mar 20 '15 at 19:07

Workflows only trigger on inserts and updates. As such, you can't do configuration-based logic on deletes. This is one of the times when Apex Code is required.

Not the answer you're looking for? Browse other questions tagged or ask your own question.