A critical part of a workflow is the process. At a high level, a process simply can be described as a model or graphical representation of a procedure. It diagrams the logical flow and relationship of the individual components that comprise the procedure. This unique combination of components forms a methodical process.
At a low level, a process is a network of actions, each serving a distinct and functional purpose that work in tandem with one another to drive toward an end result. Each process can function individually or be used as part of several other processes.
This interconnectivity and multi-purpose use model enables you to design and implement complete and integrated processes. Since most processes are used iteratively and interchangeably, you can continually make adjustments and improve performance. Eventually, you will have a set of efficient, repeatable best practices you can use, as well as a model for other processes.
As an example, think of a process as a segment of a major interstate with roads constantly merging and diverging. There are several entrance and exit points and every junction leads to a different destination. Each segment can be used to get from one particular point to another, or be combined with several other segments to reach another destination. The more you use and become familiar with the product, you will discover that you can employ processes in a variety of ways to reach your end objective.
You can nest workflows within other workflows, so that one workflow can automatically launch another. A "sub-process" like this is sometimes referred to as a "child" workflow, with the main process referred to as the "parent". The child process must be set up and configured so that it can function on its own (for example, with its own actions, attributes, event listener, etc.). To nest workflow processes, simply drag the "child" workflow to the canvas and then draw an arrow to it from the action you want to launch it.
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.