import workflows with missing custom actions
If a workflow contains a custom action from another environment, and then the workflow is imported into another environment, without that custom action. The import will fail.
Please implement a mechanism to cope with missing actions, so that the workflow can be imported in and give the end user the option to remove the incompatible action.
Henning Eiben commented
Even if the custom Xtension exists in the target-environment the import will fail - or at least the actions will be inaccessible.