A process module will typically require the following node types.
| Process | Used to define processes and status rules that are the building blocks of the module. |
| Process Specification | Used to create process specifications, which act as both Component and Worker template. |
| Group Profile | Lists the components that make up a group. |
| Status Rules | Most status rules can be defined within the process. Separate status rules are only required for status rules that are not associated with process steps, such as worker-level status rules that call group-level actions. |
| Module definition | Defines the group profiles that make up a module. |
| Form | Used to define forms. |
| Script Component | Used to create script-based components that provide module-level functionality. |
| Script | Used to create the scripts that are used by the Script Component type. These typically inherit from Component Script. |
| Resolved Script | Used to define scripts used by group-level run process step, for evaluation steps, or for form scripts. These are like normal scripts, but with referenced scripts copied in to avoid runtime complications. |
There are alternative node types which overlap with these, but which should not be used unless there is a specific reason to use them:
- The Process builder and Process model methods of building processes. These are compatible with process modules, but they do not easily achieve the level of modularity suitable for process modules.
- Process Component, which has been superceded by Process Specification.
- Worker Template, which has been superceded by Process Specification.