Creating a workflow type involves creating and configuring many components and XML files that are specific to the workflow type, as shown in the Configuring the Registration Workflow Type section. In addition, there are several workflow-related Nucleus components that are used by all custom workflow types. These components require no additional configuration, but are available for other components to make reference to as part of their configuration:
/atg/registry/factories/WorkflowFactory
A UI-related component that is shared by all workflow types. The factory
property of each workflow registry must point to this component (for example, the /atg/registry/RegistrationWorkflows
component shown in the Registration Workflow section).
/atg/registry/filters/WdlFilter
A filter for .wdl
files. The filter
property of each workflow registry must point to this component (for example, the /atg/registry/RegistrationWorkflows
component shown in the Registration Workflow section).
/atg/workflow/process/ components
An e-mail sending component (WorkflowEmailSender
) and the associated template e-mail information (DefaultTemplateEmailInfo
). These are used by the emailNotify
and emailNotifyTaskActors
standard workflow actions.
/atg/workflow/process/configuration/ components
These supply the default configurations for some of the standard workflow actions. There are five standard actions that come with the Scenarios module and that can be included in the workflow process manager configuration for any workflow type: emailNotify
, emailNotifyTaskActors
, recordEvent
, recordAuditTrail
, and deleteSubject
. The EmailNotifyConfiguration
component configures the emailNotify
action; the RecordActionConfiguration
component configures the recordEvent
and recordAuditTrail
actions. Note that the emailNotifyTaskActors
and deleteSubject
actions do not have default configurations shared by all workflow types, because they must be configured separately for each workflow type, as demonstrated in the Registration Workflow section.