0

I have a situation. One of Our client is using Professional edition. But our managed release package has a Process builder with APEX invocableMethod in it. Professional Edition will not allow any Apex related flows/process builders etc.. Workaround will be using a traditional Trigger. However, I am unable to remove already existing Process Builder from the package so that I can insert the Trigger and install it on Client Profession Edition. Please let me know what are the steps to be taken to remove Components from managed package. Thank you.

THIS IS THE ERROR THAT I AM GETTING While installing the package in professional edition with Process Builder action type set to APEX.

"myRule_1_A1 (Action Call) - We can't find an action with the name and action type that you specified."

Improve this question
2
  • That's really odd. I believe when a managed package installs an InvocableMethod, the subscriber can invoke it even in Professional Edition (e.g. the DLRS plugin can do this when you set a rollup's invocation method to Process Builder). Strange that the package can't install such a reference itself.
    – Charles T
    Commented Nov 15, 2018 at 15:26
  • I forgot to include the error/exception that I am getting while installing the package in professional edition @CharlesT . I have updated the Question. If I can do something in Professional Edition (Client org) to get it installed, please let me know. I'll be in your debt.
    – AshSFcloud
    Commented Nov 16, 2018 at 4:28

1 Answer 1

Reset to default
2

No you cannot delete a process builder from a managed package. But you can de-activate it. Event though Can we remove a process builder component from a managed package? is 2 years old it's still relevant to date. Below is from the latest Documentation.

In a development organization, you can’t delete a flow or flow version after you upload it to a released or beta managed package.

Note: Updating based on @charlesT comments

enter image description here enter image description here

Improve this answer
9
  • can we deprecate it like Apex Global classes?
    – Pranay Jaiswal
    Commented Nov 15, 2018 at 15:24
  • @PranayJaiswal Honestly not sure about it!
    – Hemavantha Rajesh Varma Mudunu
    Commented Nov 15, 2018 at 15:25
  • 1
    I'm actually not 100% sure if the "Process" entry in that table is Process Builder or Approval Process. My instinct would be to go by the "Flow" entry which says "Upgradeable: Yes, Subscriber Deletable: Yes, Developer Deletable: No, Protectable: No, IP Protection: No"
    – Charles T
    Commented Nov 15, 2018 at 15:29
  • @CharlesT Actually I suspect you might be true!
    – Hemavantha Rajesh Varma Mudunu
    Commented Nov 15, 2018 at 15:37
  • 1
    Yeah I really don't know, I guess you'd have to experiment with a dummy package and report back. Personally I would not be comfortable releasing a managed package with a Process Builder in it. Either the logic is internal (and if the customer needs to be able to turn it off, provide a custom setting or such), or you give the customer an Invocable Process and let them create the PB and decide when to create it and turn it on/off.
    – Charles T
    Commented Nov 15, 2018 at 15:41

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .