I am getting this message when trying to migrate a process out of the global project space
But it does not explain when I can enable it again? Why would I want to disable a feature that we need in the business process?
The message is saying that you cannot migrate it out of the global context AND keep that feature. Workflows cannot currently invoke business processes that are within projects.
But it must be in a project other than global, global has no security context and it would grant any process designer access to the process development side.
Why would we not be able to invoke a process based on who has access to edit it?
Right, workflow cannot currently access business processes in projects. That functionality is in the works, but it has not been released yet. So if you need a business process to be invoked by a workflow, you would have to keep it in the global context. And, yes, that would mean it would be visible to all process designers rather than restricted within a project.
Does this same limitation apply to Workflows accessing other resources within Projects? I.e., accessing a lookup table via a query rule within a Project.
For example, I have two lookup tables that should be held within a Project to restrict access. One of these tables is updated manually by upload. The Workflow uses that lookup table to update, and/or insert rows in the other table where necessary.