I've written a process builder flow with some conditions where the action is calling an @invocable Apex class. Now, when I'm moving this through change set to higher environments there the flow is getting deployed only partially. Surprisingly the action for the first condition is blank in the target org even though I didn't get any errors while deploying. Any idea what I'm missing here?

P.S- Both the orgs are Spring'16.


If the process calls an @invocable, you'll want to deploy the @invocable class first in one change set, the deploy the process in a second change set afterward. The class it's calling needs to already exist in the org for you to be able to reference it in your process when you deploy it. Ditto for any fields or other conditions that it references.

| improve this answer | |
  • Why exactly can't you deploy both components and execute testing on one deploy? I mean I understood what happens but i'm just curious to know why. – Alexander Aeons Torn Jun 7 '16 at 12:07
  • 1
    PB will look for the reference and won't be able to find it. The reference won't be the same in the SB as it is in the next org or Production. Until that reference is established, it won't get associated as needed. You're not able to control the order that happens in when using a change set. – crmprogdev Jun 7 '16 at 12:10
  • Whenever I'm adding the components to the change set and migration starts automatically on its own the action call of the flow in the source org is getting removed!! Strange things are happening.I really can't find a plausible reason. – Sagnik Jun 7 '16 at 12:24
  • Wait a min. The source org? Haven't heard of that one! – crmprogdev Jun 7 '16 at 12:26
  • Yes source org. So what is the workaround? Do I've to do this manually? – Sagnik Jun 7 '16 at 12:27

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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