Global Subprocesses

When global subprocesses are used in a workflow, they cannot be changed from this location; they are read-only (as indicated by the lock symbol next to the subprocess). You can perform basic tasks, such as change the name and bind parameters, but the internal process cannot be edited. However, if you want to make a change to a global subprocess so that it is reflected in all workflows that use this subprocess, you can edit the original subprocess by selecting it from the Subprocesses resources folder (using the Universal Browser).

You can also choose to make a local copy of a global subprocess if you decide that the global subprocess does not fully meet the needs of the workflow. When you make a subprocess local, you can make changes that are reflected only in the current workflow. The Global Subprocesses list does not change.

In addition, if you have created a subprocess specific to a workflow and you want to re-use it in other workflows, you can make the subprocess global, which adds it to the Global Subprocesses list. However, you cannot make a local subprocess global if it has references to data outside the subprocess (excluding parameters). For example, if you are using a workflow level variable in a bind or expression, you must remove this external data reference before you are able to create a global subprocess. The subprocess must be self-contained for it to work as a global subprocess.

Global subprocesses are designed the same as local workflow subprocesses. They are configured in isolation and can contain any activity or variable that any manually created subprocess can have. These subprocesses can have input and output parameters that can be bound when they are added to a workflow, and they can also be composed of several user-defined activities. Global subprocess cannot be deleted if it is being used by a workflow or subprocess.