For each task in the Process Definition (as defined by<task> elements), it is possible to associate a task description. The description specifies information that may be attached to a task, that is properties (name and data type) associations (name and type of associated object), and mandatory aspects. A user may view and edit this information in the Task dialog within the Alfresco Explorer.

The Task Model is expressed as a Content Model, as supported by the Data Dictionary. To create a Task Model, create a new Content Model file for Process Definition with the .xml extension.

<?xml version="1.0" encoding="UTF-8"?>
<model name="bookwcmwf:workflowmodel"
xmlns="http://www.alfresco.org/model/dictionary/1.0">
<imports>
<import uri="http://www.alfresco.org/model/wcmworkflow/1.0"
prefix="wcmwf" />
<import uri="http://www.alfresco.org/model/bpm/1.0" prefix="bpm">
</imports>
<namespaces>
<namespace uri="http://book.com" prefix="bookwcmwf" />
</namespaces>
</model>

<types>
<type name="bookwcmwf:submitReviewTask">
<parent>wcmwf:startTask</parent>
</type>
</types>

<type name="bookwcmwf:submitReviewTask">
<parent>wcmwf:startTask</parent>
<properties>
<property name="wcmwf:submitReviewType">
<title>Serial or Parallel Review</title>
<type>d:text</type>
</property>
</properties>
<associations>
<association name="wcmwf:webproject">
<source>
<mandatory>false</mandatory>
<many>false</many>
</source>
<target>
<class>wca:webfolder</class>
<mandatory>true</mandatory>
<many>false</many>
</target>
</association>
</associations>
</type>

<type name="bookwcmwf:verifyBrokenLinksTask">
<parent>wcmwf:workflowTask</parent>
<mandatory-aspects>
<aspect>bookwcmwf:reviewInfo</aspect>
<aspect>bpm:assignee</aspect>
</mandatory-aspects>
</type>
<aspects>
<aspect name="bookwcmwf:reviewInfo">
<properties>
<property name=" bookwcmwf:reviewerCnt">
<title>Reviewer Count</title>
<type>d:int</type>
<mandatory>true</mandatory>
</property>
</properties>
</aspect>
</aspects>

A Process Definition represents a formal specification of a business process and is based on a directed graph. The graph is composed of nodes and transitions. Every node in the graph is of a specific Type. The Type of the node defines the runtime behavior. A Process Definition has exactly one Start-state and End-state.

The following table describes some of the key terms used in a Process Definition:

The following table summarizes the Node Types available in jBPM out of the box.

There are two ways of building the Process Definition. One is by hand, that is create a jPDL XML document. The second option is by designer, that is use a tool to generate the jPDL XML document. To create a Process Definition, create a new Process Definition file with the extension .xml.

<?xml version="1.0" encoding="UTF-8"?>
<process-definition xmlns="urn:jbpm.org:jpdl-3.1" name="bookwcmwf:bookworkflow">

<swimlane name="initiator"/>
<swimlane name="approver">
<assignment class="org.alfresco.repo.workflow.jbpm.AlfrescoAssignment">
<pooledactors>#{bpm_groupAssignee}</pooledactors>
</assignment>
</swimlane>
<swimlane name="assignee">
<assignment class="org.alfresco.repo.workflow.jbpm.AlfrescoAssignment">
<actor>#{bpm_assignee}</actor>
</assignment>
</swimlane>

<start-state name="start">
<task name="bookwcmwf:submitReviewTask" swimlane="initiator"/>
<transition name="" to="initialise"/>
</start-state>
<swimlane name="assignee">
<assignment class="org.alfresco.repo.workflow.jbpm.AlfrescoAssignment">
<actor>#{bpm_assignee}</actor>
</assignment>
</swimlane>
<task-node name="initialise ">
<task name="bookwcmwf:verifyBrokenLinksTask" swimlane="assignee" />
<transition name="abort" to="end">
<action
class="org.alfresco.repo.workflow.jbpm.AlfrescoJavaScript">
<script>
var mail = actions.create("mail");
mail.parameters.to = initiator.properties["cm:email"];
mail.parameters.subject = "Adhoc Task " +
bpm_workflowDescription;
mail.parameters.from =
bpm_assignee.properties["cm:email"];
mail.parameters.text = "It's done";
mail.execute(bpm_package);
</script>
</action>
</task-node>
<end-state name="end"/>

For localized workflow interaction it is necessary to provide Resource Bundles containing UI labels for each piece of text that is exposed to the user. With the appropriate Resource Bundles, a single workflow instance may spawn tasks where the user interface for each task is rendered in a different language, based on the locale of the user. Specific structure has to be followed in order to define labels for UI in Resource Bundle.

<model_prefix>_<model_name>.[title|description]
<model_prefix>_<model_name>.<model_element>.<element_prefix>_ <element_name>.[title|description]

Add all the properties that relate to this Process Definition and model.

bookwcmwf_bookworkflow.workflow.title=Book Workflow
bookwcmwf_bookworkflow.node.verifybrokenlinks.transition.abort.title=Abort Submission
bookwcmwf_workflowmodel.type.bookwcmwf_reviewTask.description=
Review Documents to approve or reject them

Create a file book-serial-group-messages.properties in the specified location,<install-alfresco>/tomcat/shared/classes/alfresco/extension. Copy the downloaded content into the file.

The custom web client configuration file contains information on how to display these custom Content Types, Aspects, and Associations. You need to make sure that the web client program recognizes this new custom aspect and displays it in the web-based interface. In order to make this happen, you need to configure the web client file, web-client-config-custom.xml, in the extension folder.

Open the web-client-config-custom.xml file from the specified location<install-alfresco>/tomcat/shared/classes/alfresco/extension. Copy the downloaded content into the file.

The custom model context file defines the Spring bean that will be used to bootstrap the definition of your custom Model, Workflow, and Resource Bundle. It lists one or more custom Model files, Workflow files, and Resource Bundles. When Spring starts up, it will instantiate this bean and will load your files from the disk.

Create a custom model context file and name the file as<your-custom-model-name>-context.xml, for example, bookWorkflowModel-context.xml. Create the file in the specified location<install-alfresco>/tomcat/shared/classes/alfresco/extension. Copy the downloaded content in the file.

In order to identify this workflow for WCM, open the web-client-config-wcm.xml file from the specified location<install-alfresco>/tomcat/webapps/alfresco/WEB-INF/classes/alfresco and insert the highlighted XML code within the workflows tag, as follows:

<workflows>
wcmwf:submit ,bookwcmwf:bookworkflow
</workflows>

Now that we have completed workflow implementation, let's test the workflow.

Follow the steps below to test workflow.