This document describes the workflow API calls necessary to apply a simple workflow to a content item.
This simple workflow is defined in -sql/workflows/author-edit-publish.sql.
+sql/workflows/author-edit-publish.sql.Production of a content item frequently begins with a concept which is initiated by the publisher and then executed by the staff. @@ -65,18 +68,19 @@
In this case, only one assignment is made per task. You can make as many assignments per task as desired. There is currently no workflow API to set deadlines, so you must write your own DML to -insert a row into wf_case_deadlines if you wish to allow +insert a row into wf_case_deadlines if you wish to allow the publisher to set deadlines ahead of time.
-The above workflow is created in the Default context. In -practice, you may wish to create one or more contexts in which to -create your workflows. Contexts may be used to represent different -departments within an organization.
-The start_case enables the first task in the workflow, -in this case Authoring.
+The above workflow is created in the Default +context. In practice, you may wish to create one or more contexts +in which to create your workflows. Contexts may be used to +represent different departments within an organization.
+The start_case enables the first task in the +workflow, in this case Authoring.
If multiple persons are assigned to the same task, it is useful -to allow a single person to "check out" or lock an item while they -are working. This is accomplished with the following API calls:
+to allow a single person to "check out" or lock an item +while they are working. This is accomplished with the following API +calls:declare v_journal_id integer; @@ -121,8 +125,8 @@-Upon finishing a task, you must notify the workflow engine where to go next. In this case, an author wishes to simply check an item back in without actually completing the authoring task. The -set_attribute_value procedure must thus be used to set -next_place to the starting place of the workflow.
+set_attribute_value procedure must thus be used to set +next_place to the starting place of the workflow.Finish Task
The process to finish a task varies slightly depending on whether the user has previously checked out the item out or not. If @@ -150,11 +154,12 @@ end; /
In this case an author is finishing the Authoring task, -upon which the workflow engine will move the workflow to the -Authored state (as indicated by the next_place -attribute). If the author had previously checked out the item, then -only the second step is required.
+In this case an author is finishing the +Authoring task, upon which the workflow engine +will move the workflow to the Authored state (as +indicated by the next_place attribute). If the author +had previously checked out the item, then only the second step is +required.
Approval steps more commonly do not involve an explicit check-out process. The code is thus virtually identical to that @@ -180,10 +185,10 @@ /
Note the distinction between approval or rejection is determined -solely by the value of the next_place attribute.
+solely by the value of the next_place attribute.