Embedded process activity

Embedded process activity permits you to add process within another process by adding activities and attributes (variables, roles, states, milestones) to the parent map.

Use embedded processes to create logical group of activities and if you need to add attributes to a running job rather than perform a discreet operation in the case of a subjob.

Note A subjob cannot be searched or viewed independently from the parent job.

An embedded process activity is useful in scenarios, such as:

  • Initial process map is too large.
  • A process may be reused in other maps.
  • A process may be reused by another department or company.

You can embed smaller process maps into the main map (parent map). The standard processing rules for an embedded process map are similar to other process maps.

The activities in an embedded process may need to use or modify variable values in the parent. If you embed a process map you must declare the same variable names in the embedded process (child) as the parent. All variables created in the parent or child map are visible to the entire job.

  • You cannot assign resources to a process map once it is embedded in the parent map.
  • You can include a synchronous embedded process within an asynchronous map. But you cannot include an asynchronous embedded process in a synchronous map.
  • If a parent map is synchronous, the synchronous embedded process is performed synchronously.
  • If a parent map is asynchronous, any synchronous or asynchronous embedded processes are performed asynchronously.

See also: