topic Approve and reject as a part of a workflow in Alfresco Archive

Approve and reject as a part of a workflow

fbehfar — Sat, 09 Feb 2008 12:38:07 GMT

Hi,I'm trying to deploy a workflow, in some part of it, it needs to have a Approve/Reject workflow. this workflow will be automatically started when a content upload, then a notification will be sent to a specified user, this user should read the content (or if it was necessary update it) then he sh

Re: Approve and reject as a part of a workflow

rob562435 — Mon, 11 Feb 2008 06:46:19 GMT

First a question: when you look in the task overview what status information is given to the taks, in other words on which tasknode the task has arrived?

Rgrds, Rob

Re: Approve and reject as a part of a workflow

rob562435 — Mon, 11 Feb 2008 06:55:44 GMT

Next I think the problem is the fact that you coded the decision node as a task node. The decision node needs a condition to decide which branch to take. What you should do is remove the decision node and add the two transition definitions to the Notify CCM tasknode, as follows:

   <task-node name="Notify CCM"> 
      <task name="crwf:CCManagerReview" swimlane="CCM"></task> 
      <transition name="Not approved" to="Notify Customer"></transition> 
      <transition name="Approved" to="Notify Analysis"></transition> 
   </task-node> 
‍‍‍‍‍‍

You do not need a decision node in this case.
(You may modify the task naming to your needs of course, this is only to show how to…)
In case you use a decision node you have to add conditions otherwise the decision node does not work. The decision node is a background "task" that never results in buttons for users. In case a user has to decide this should be implemented as normal task nodes with multiple branches (transitions).

Hope this helps….

Rgrds, Rob

Re: Approve and reject as a part of a workflow

fbehfar — Mon, 11 Feb 2008 12:49:11 GMT

Hi,
Thanks Rob,
well let me explain you my workflow:
a user uploads a content, by uploading, the workflow will start on that content:
1. CCM(Change and Configuration Manager) recieves a task on his task to do list
2. by opening the task he sees a description of the task and the he should review the uploaded document
3. after reading the document, he decides to approve or reject the document (it's a change request document)
4. if he approves the document then a pool task will added to the Analysis group pool task list
5. if he rejects the document then the uploader of the document will recieve a task or a notification of rejection
.
.
.
.
I don't know how to implement this, actually I need a Approve/Reject buttons to do it, but I don't know how!!!! do I have to change anything else in my workflow or model???

Thank you again,
FSB

Re: Approve and reject as a part of a workflow

fbehfar — Tue, 12 Feb 2008 11:50:29 GMT

Hi rob,
I could finaly implement it.
but another question, if a task was defined as a pool task, and then the first one who takes the task, how can I have his ID (the owner ID). actually I want to define a swimlane as an owner and assign some task to the owner (how took the task from the pool task list)
I have tried all these but they don't work!!!

   <swimlane name="Owner">
   <assignment class="org.alfresco.repo.workflow.jbpm.AlfrescoAssignment">
   <actor>#{taskInstance.actorId}</actor>
   </assignment>
   </swimlane>‍‍‍‍‍

   <swimlane name="Owner">
   <assignment class="org.alfresco.repo.workflow.jbpm.AlfrescoAssignment">
   <actor>#{person.properties["cm:owner"]}</actor>
   </assignment>
   </swimlane>‍‍‍‍‍

thank you in advanced,
FSB

Re: Approve and reject as a part of a workflow

rob562435 — Fri, 15 Feb 2008 10:13:01 GMT

Hi there,

Sorry I did not (in time) reacted on your previous question.
About the question you put here I can only give you a hint on the way I set up the assignments without swimlanes. Swimlanes are predefined and as far as I know do not work well with variables in the way I guess you want to.

As an example: I defined for the various roles a variable (multiple) that is filled with the information needed in an assignment. The assignment would look like:

 <task-node name="reAssignNeeded">
  <task name="qcp:reAssignNeeded">
   <assignment class="org.alfresco.repo.workflow.jbpm.AlfrescoAssignment">
    <actor>#{qcp_processManager}</actor>
   </assignment>‍‍‍‍‍

The varialbe is given a value with code like:

   <action class="org.alfresco.repo.workflow.jbpm.AlfrescoJavaScript">
    <script>
     <variable name="qcp_processManager" access="write"/>
     <variable name="bpm_package" access="read"/>
     <expression>
      qcp_processManager = people.getPerson(bpm_package.children[0].properties["qcp:processManagerRole"]);
     </expression>
    </script>
   </action>‍‍‍‍‍‍‍‍‍

In your case the variable would be given the value of the "owner" (in case the current user: "person" would do, see also the JavaScript API WIKI http://wiki.alfresco.com/wiki/JavaScript_API).
After the variable is given the name of the current user an automated transition must be performed to the next task node with the assignment as shown above.

I hope this helps.

Rgrds, Rob