Join the social network of Tech Nerds, increase skill rank, get work, manage projects...
 

  • Two level or multilevel workflow for Liferay 6.2

    @bhagwan.khichar
    Recommendations Offline Message

    • 0
    • 1
    • 0
    • 0
    • 5
    • 0
    • 0
    • 0
    • 1.98k
    Comment on it

    Hello guys, many times developers got stuck into the issue that How to create Two level or multilevel workflow for Liferay 6.2. So here below I have created two level or multilevel workflow for liferay 6.2. In which first approver approve the task after that second approver can approve. Copy all code and save in XML file.

    1. <?xml version="1.0"?>
    2. <workflow-definition
    3. xmlns="urn:liferay.com:liferay-workflow_6.2.0"
    4. xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    5. xsi:schemaLocation="urn:liferay.com:liferay-workflow_6.2.0 http://www.liferay.com/dtd/liferay-workflow-definition_6_2_0.xsd"
    6. >
    7. <name>Two_Level_Approver</name>
    8. <description>A approver can approve a workflow content.</description>
    9. <version>1</version>
    10. <state>
    11. <name>created</name>
    12. <metadata>
    13. <![CDATA[{"xy":[36,51]}]]>
    14. </metadata>
    15. <initial>true</initial>
    16. <transitions>
    17. <transition>
    18. <name>FirstApproval</name>
    19. <target>FirstApproval</target>
    20. </transition>
    21.  
    22. </transitions>
    23. </state>
    1. <!--  First Reject -->
    2.  
    3. <task>
    4. <name>FirstReject</name>
    5. <metadata>
    6. <![CDATA[{"transitions":{"resubmit":{"bendpoints":[[303,140]]}},"xy":[328,199]}]]>
    7. </metadata>
    8. <actions>
    9. <action>
    10. <name>reject</name>
    11. <script>
    12. <![CDATA[
    13. Packages.com.liferay.portal.kernel.workflow.WorkflowStatusManagerUtil.updateStatus(Packages.com.liferay.portal.kernel.workflow.WorkflowConstants.toStatus("denied"), workflowContext);
    14. Packages.com.liferay.portal.kernel.workflow.WorkflowStatusManagerUtil.updateStatus(Packages.com.liferay.portal.kernel.workflow.WorkflowConstants.toStatus("incomplete"), workflowContext);
    15. ]]>
    16. </script>
    17. <script-language>javascript</script-language>
    18. <execution-type>onAssignment</execution-type>
    19. </action>
    20. <notification>
    21. <name>Creator Modification Notification</name>
    22. <description>Permit Issuer : First Approval Rejected</description>
    23. <template>Your submission was rejected in First Approval by ${userName}, please modify and resubmit.</template>
    24. <template-language>freemarker</template-language>
    25. <notification-type>email</notification-type>
    26. <notification-type>user-notification</notification-type>
    27. <execution-type>onAssignment</execution-type>
    28. </notification>
    29. </actions>
    30. <assignments>
    31. <roles>
    32. <role>
    33. <role-type>site</role-type>
    34. <name>Site Administrator</name>
    35. </role>
    36. <role>
    37. <role-type>site</role-type>
    38. <name>Site Content Reviewer</name>
    39. </role>
    40. <role>
    41. <role-type>site</role-type>
    42. <name>Site Owner</name>
    43. </role>
    44. </roles>
    45. </assignments>
    46. <transitions>
    47. <transition>
    48. <name>resubmit</name>
    49. <target>FirstApproval</target>
    50. </transition>
    51.  
    52. </transitions>
    53. </task>
    54.  
    55. <!-- FirstApproval -->
    56. <task>
    57. <name>FirstApproval</name>
    58. <metadata>
    59. <![CDATA["xy":[40,62]}]]>
    60. </metadata>
    61. <actions>
    62. <action>
    63. <name>FirstApproval</name>
    64. <script>
    65. <![CDATA[
    66. workflowContext.put("notificationSenderName", "Permit Issuer");
    67. ]]>
    68. </script>
    69. <script-language>groovy</script-language>
    70. <execution-type>onEntry</execution-type>
    71. </action>
    72. <notification>
    73.          <name>Case Submission</name>
    74.      <description>Permit Issuer: Case Submission Notification</description>
    75.          <template>
    76.           Your Case has been submitted with following Case Number: 23434, you can check the status of your case using this case number.
    77.           </template>
    78.          <template-language>freemarker</template-language>
    79.          <notification-type>email</notification-type>
    80.          <recipients>
    81.           <user />
    82.          </recipients>
    83.          <execution-type>onAssignment</execution-type>
    84. </notification>
    85. <notification>
    86.     <name>First Review Notification</name>
    87.     <description>Permit Issuer: New Permit Request</description>
    88.     <template>We got a new Permit Request,  Please review the request.</template>
    89.     <template-language>freemarker</template-language>
    90.     <notification-type>email</notification-type>
    91.     <notification-type>user-notification</notification-type>
    92.     <execution-type>onAssignment</execution-type>
    93. </notification>
    94.  
    95.  
    96.  
    97. <notification>
    98.     <name>First Review Completion Notification</name>
    99.     <description>Permit Issuer: First Approval Completed</description>
    100.     <template>First Approval Status: 
    101.     Your submission has been Approved at First Approval by ${userName} with following comments [${taskComments}]. Request has been sent for Second Approval. </template>
    102.     <template-language>freemarker</template-language>
    103.     <notification-type>email</notification-type>
    104.     <recipients>
    105.     <user />
    106.     </recipients>
    107.     <execution-type>onExit</execution-type>
    108. </notification>
    109.  
    110. </actions>
    111. <assignments>
    112. <roles>
    113. <role>
    114. <role-type>organization</role-type>
    115. <name>Organization Administrator</name>
    116. </role>
    117. <role>
    118. <role-type>organization</role-type>
    119. <name>Organization Content Reviewer</name>
    120. </role>
    121. <role>
    122. <role-type>organization</role-type>
    123. <name>Organization Owner</name>
    124. </role>
    125. <role>
    126. <role-type>regular</role-type>
    127. <name>Administrator</name>
    128. </role>
    129. <role>
    130. <role-type>regular</role-type>
    131. <name>Portal Content Reviewer</name>
    132. </role>
    133. <role>
    134. <role-type>site</role-type>
    135. <name>Site Administrator</name>
    136. </role>
    137. <role>
    138. <role-type>site</role-type>
    139. <name>Site Content Reviewer</name>
    140. </role>
    141. <role>
    142. <role-type>site</role-type>
    143. <name>Site Owner</name>
    144. </role>
    145. </roles>
    146. </assignments>
    147. <transitions>
    148. <transition>
    149. <name>approve</name>
    150. <target>Firstapproved</target>
    151. </transition>
    152.  
    153. <transition>
    154. <name>reject</name>
    155. <target>FirstReject</target>
    156. <default>false</default>
    157. </transition>
    158. </transitions>
    159. </task>
    160.  
    161. <!-- Second Reject -->
    162.  
    163. <task>
    164. <name>SecondReject</name>
    165. <metadata>
    166. <![CDATA[{"transitions":{"resubmit":{"bendpoints":[[303,140]]}},"xy":[328,199]}]]>
    167. </metadata>
    168. <actions>
    169. <action>
    170. <name>reject</name>
    171. <script>
    172. <![CDATA[
    173. Packages.com.liferay.portal.kernel.workflow.WorkflowStatusManagerUtil.updateStatus(Packages.com.liferay.portal.kernel.workflow.WorkflowConstants.toStatus("denied"), workflowContext);
    174. Packages.com.liferay.portal.kernel.workflow.WorkflowStatusManagerUtil.updateStatus(Packages.com.liferay.portal.kernel.workflow.WorkflowConstants.toStatus("incomplete"), workflowContext);
    175. ]]>
    176. </script>
    177. <script-language>javascript</script-language>
    178. <execution-type>onAssignment</execution-type>
    179. </action>
    180. <notification>
    181. <name>Creator Modification Notification</name>
    182. <description>Permit Issuer: Second Approval Rejected</description>
    183. <template>Your submission was rejected at Second Approval by ${userName} with following comments [${taskComments}], please modify and resubmit.</template>
    184. <template-language>freemarker</template-language>
    185. <notification-type>email</notification-type>
    186. <notification-type>user-notification</notification-type>
    187. <execution-type>onAssignment</execution-type>
    188. </notification>
    189. </actions>
    190. <assignments>
    191. <roles>
    192. <role>
    193. <role-type>site</role-type>
    194. <name>Site Administrator</name>
    195. </role>
    196. <role>
    197. <role-type>site</role-type>
    198. <name>Site Content Reviewer</name>
    199. </role>
    200. <role>
    201. <role-type>site</role-type>
    202. <name>Site Owner</name>
    203. </role>
    204. </roles>
    205. </assignments>
    206. <transitions>
    207. <transition>
    208. <name>resubmit</name>
    209. <target>FirstApproval</target>
    210. </transition>
    211.  
    212. </transitions>
    213. </task>
    214.  
    215. <!-- SecondApproval -->
    216.  
    217. <task>
    218. <name>SecondApproval</name>
    219. <metadata>
    220. <![CDATA[{"xy":[168,36]}]]>
    221. </metadata>
    222.  
    223. <actions>
    224.  
    225. <notification>
    226. <name>Second Review Notification</name>
    227. <description>Permit Issuer: Second Approval Request</description>
    228. <template>${userName} sent you request for Second review.</template>
    229. <template-language>freemarker</template-language>
    230. <notification-type>email</notification-type>
    231. <notification-type>user-notification</notification-type>
    232. <execution-type>onAssignment</execution-type>
    233. </notification>
    234. <notification>
    235. <name>Second Review Completion Notification</name>
    236. <description>Permit Issuer: Second Approval Completed</description>
    237. <template>
    238. Your submission has been Approved at Second Approver by ${userName} with following comment ${taskComments}.</template>
    239. <template-language>freemarker</template-language>
    240. <notification-type>email</notification-type>
    241. <recipients>
    242. <user />
    243. </recipients>
    244. <execution-type>onExit</execution-type>
    245. </notification>
    246. </actions>
    247. <assignments>
    248. <roles>
    249. <role>
    250. <role-type>organization</role-type>
    251. <name>Organization Administrator</name>
    252. </role>
    253. <role>
    254. <role-type>organization</role-type>
    255. <name>Organization Content Reviewer</name>
    256. </role>
    257. <role>
    258. <role-type>organization</role-type>
    259. <name>Organization Owner</name>
    260. </role>
    261. <role>
    262. <role-type>regular</role-type>
    263. <name>Administrator</name>
    264. </role>
    265. <role>
    266. <role-type>regular</role-type>
    267. <name>Portal Content Reviewer</name>
    268. </role>
    269. <role>
    270. <role-type>site</role-type>
    271. <name>Site Administrator</name>
    272. </role>
    273. <role>
    274. <role-type>site</role-type>
    275. <name>Site Content Reviewer</name>
    276. </role>
    277. <role>
    278. <role-type>site</role-type>
    279. <name>Site Owner</name>
    280. </role>
    281. </roles>
    282. </assignments>
    283. <transitions>
    284. <transition>
    285. <name>approve</name>
    286. <target>approved</target>
    287. </transition>
    288. <transition>
    289. <name>reject</name>
    290. <target>SecondReject</target>
    291. <default>false</default>
    292. </transition>
    293. </transitions>
    294. </task>
    295.  
    296.  
    297.  
    298.  
    299.  
    300. <state>
    301. <name>Firstapproved</name>
    302. <metadata>
    303. <![CDATA[
    304. {"xy":[380,51]}
    305. ]]>
    306. </metadata>
    307. <actions>
    308. <action>
    309. <name>approve</name>
    310. <script>
    311. <![CDATA[
    312. import com.liferay.portal.kernel.workflow.WorkflowStatusManagerUtil;
    313. import com.liferay.portal.kernel.workflow.WorkflowConstants;
    314. WorkflowStatusManagerUtil.updateStatus(WorkflowConstants.toStatus("inactive"), workflowContext);
    315. ]]>
    316. </script>
    317. <script-language>groovy</script-language>
    318. <execution-type>onEntry</execution-type>
    319. </action>
    320. </actions>
    321. <transitions>
    322. <transition>
    323. <name>SecondApproval</name>
    324. <target>SecondApproval</target>
    325. <default>true</default>
    326. </transition>
    327. </transitions>
    328. </state>
    329.  
    330.  
    331.  
    332. <state>
    333. <name>approved</name>
    334. <metadata>
    335. <![CDATA[
    336. {"xy":[380,51]}
    337. ]]>
    338. </metadata>
    339. <actions>
    340. <action>
    341. <name>approve</name>
    342. <script>
    343. <![CDATA[
    344. import com.liferay.portal.kernel.workflow.WorkflowStatusManagerUtil;
    345. import com.liferay.portal.kernel.workflow.WorkflowConstants;
    346. WorkflowStatusManagerUtil.updateStatus(WorkflowConstants.toStatus("approved"), workflowContext);
    347. ]]>
    348. </script>
    349. <script-language>groovy</script-language>
    350. <execution-type>onEntry</execution-type>
    351. </action>
    352. </actions>
    353. </state>
    354. </workflow-definition>

    You can download two level workflow XML from attachment.

    tow level workflow multi level workflow multi approver workflow double approver workflow Liferay 6.2 workflow xml in liferay 6.2
    Comment on it

 5 Comment(s)

  • @Ujjainee
    Recommendations Offline Message

    over 8 years ago

    Hello,

    Can you please clear my one doubt regarding Kaleo workflow.

    Is it neccessary that the Kaleo workflow will always pass through admin and admin will always have the right to assign it to someone else or to self? I'm producing the test cases of what is happening with my workflow and what I actually want:
    I have the following roles:

    1. Admin-Test
    2. First approver-Approver1
    3. Second Approver-Approver2
    4. User-test333



    Now my workflow is passing like this:
    User->Approver1->Approver2(If I do not open Admin with my credentials of TEST)
    Otherwise:
    User->Admin->When Assigned to Approver1->Approver1->Approver2
    ->When Assigned to me->Admin only becomes both Approver1 and Approver2 and is approving or rejecting the same.

    I don't want the second case to happen and it should follow only the first test Case: User->Approver1->Approver2
    Admin should not have the right to approve or reject. Is it possible somehow?

Sign In
Forgot Password?
                           OR                           
Create an account !!
                           OR                           
Register

Sign up using

                           OR                           
Forgot Password
Reset Password
Fill out the form below and reset your password: