Yes It Can: Leverage Workflow in Plone to Bring Business Process Online

1. Yes It Can! Learning to Leverage Plone’s Workﬂow to Bring Business Practices Online Cris Ewing UW Radiology Web Services PSE2010

2. Plone’s Greatest Strength

3. Often Overlooked

4. • Permissions & Roles

5. • Permissions & Roles • Inheritance of Rights

6. • Permissions & Roles • Inheritance of Rights • Workﬂow: States & Transitions

7. • Permissions & Roles • Inheritance of Rights • Workﬂow: States & Transitions • Advanced Techniques

9. Image Credit: femaletrumpet02 http://www.ﬂickr.com/photos/femaletrumpet02/3862031267/

10. Image Credit: ul_Marga http://www.ﬂickr.com/photos/ul_marga/755378645/

11. Image Credit: gossamerpromise http://www.ﬂickr.com/photos/gossamerpromise/432902183/

12. what do they open?

13. what do they open? how can I ﬁnd the right one?

15. lots of permissions

16. CMFEditions: Save new version CMFEditions: Access previous versions CMFEditions: Apply version control Content rules: Manage rules View Management Screens Request review List portal members FTP Access set own properties iterate: check out content Use external editor Review portal content Allow sendto List undoable changes lots of permissions Delete Objects Portlets: manage portlets Modify view template List folder contentsManage properties Undo changes iterate: check in content Add portal member Set own password CMFEditions: Checkout to location CMFEditions: Revert to previous versions Add portal folders Add portal content View Groups Reply to item Portlets: manage own portlets

17. (and that’s a good thing)

18. (and that’s a good thing) ((take my word for it))

19. not so well documented Image Credit: The empty Book (http://www.ﬂickr.com/photos/hirok/4404405566), a Creative Commons Attribution (2.0) image from hirok's photostream

20. Use The Source

21. Use The Source Products.CMFCore.permissions AccessControl.permissions Products.Five / permissions.zcml zope.security / permissions.zcml

22. help the doc team Image Credit: http://www.ﬂickr.com/photos/soldiersmediacenter/2570460662/, a Creative Commons Attribution (2.0) image from soldiersmediacenter's photostream

23. Permissions Manual

24. Permissions Manual http://plone.293351.n2.nabble.com/plone-permissions-manual-td3666469.html

25. Permissions Manual http://plone.293351.n2.nabble.com/plone-permissions-manual-td3666469.html http://www.coactivate.org/projects/plone-documentation/permissions-manual

27. Roles

28. Image Credit: ul_Marga http://www.ﬂickr.com/photos/ul_marga/755378645/

29. built-in roles from Plone

30. • Manager

31. • Manager - Like Superman, can do anything

32. • Manager - Like Superman, can do anything • Owner

33. • Manager - Like Superman, can do anything • Owner - All content management rights

34. • Manager - Like Superman, can do anything • Owner - All content management rights • Editor

35. • Manager - Like Superman, can do anything • Owner - All content management rights • Editor - Can change existing, but not create new

36. • Manager - Like Superman, can do anything • Owner - All content management rights • Editor - Can change existing, but not create new • Reviewer

37. • Manager - Like Superman, can do anything • Owner - All content management rights • Editor - Can change existing, but not create new • Reviewer - Can change workﬂow state

38. • Contributor

39. • Contributor - Can add new content, but not edit existing

40. • Contributor - Can add new content, but not edit existing • Reader

41. • Contributor - Can add new content, but not edit existing • Reader - Can view an object, but not manage it in any way

42. • Contributor - Can add new content, but not edit existing • Reader - Can view an object, but not manage it in any way • Member

43. • Contributor - Can add new content, but not edit existing • Reader - Can view an object, but not manage it in any way • Member - No signiﬁcant special rights

44. • Contributor - Can add new content, but not edit existing • Reader - Can view an object, but not manage it in any way • Member - No signiﬁcant special rights • Authenticated

45. • Contributor - Can add new content, but not edit existing • Reader - Can view an object, but not manage it in any way • Member - No signiﬁcant special rights • Authenticated • Anonymous

46. • Contributor - Can add new content, but not edit existing • Reader - Can view an object, but not manage it in any way • Member - No signiﬁcant special rights • Authenticated distinguish folks who are logged in from folks who are not • Anonymous

47. you can create new ones

48. you can create new ones but be cautious . . .

49. • Too many roles can be confusing

50. • Too many roles can be confusing • Too many roles clutter the user interface

51. Image Credit: yin yang (http://www.ﬂickr.com/photos/csb13/4577840509/), a Creative Commons by-nc-nd (2.0) image from csb13's photostream

53. Roles can be ‘global’ or ‘local’

54. Global Roles

55. Local Roles

56. so what’s the difference?

57. Plone Site Folder 1 Folder 2 Folder 1.1 Folder 2.1 Folder 1.2 Folder 2.2 X X

58. Assign a Local Role on a Folder Plone Site Folder 1 Folder 2 Folder 1.1 Folder 2.1 Folder 1.2 Folder 2.2 X X

59. Inheritance can be blocked Plone Site Folder 1 Folder 2 Folder 1.1 Folder 2.1 Folder 1.2 Folder 2.2 X X

60. Plone Site Grant A Global Role (say ‘Editor’) Folder 1 Folder 2 Folder 1.1 Folder 2.1 Folder 1.2 Folder 2.2 X X

61. Global Roles CANNOT Be Blocked!!! Plone Site Folder 1 Folder 2 Folder 1.1 Folder 2.1 Folder 1.2 Folder 2.2 X X

62. so what do we do?

63. Assign a ‘Global’ Local Role (use sharing) Plone Site Folder 1 Folder 2 Folder 1.1 Folder 2.1 Folder 1.2 Folder 2.2 X X

64. Inheritance Blocking is Respected Plone Site Folder 1 Folder 2 Folder 1.1 Folder 2.1 Folder 1.2 Folder 2.2 X X

66. states

67. Image Credit: Visits to Taiwan 2005 (http://www.ﬂickr.com/photos/midpath/300465658/, a Creative Commons by-nc-nd (2.0) image from midpath's photostream

68. states can:

69. states can: • Assign permissions to roles

70. states can: • Assign permissions to roles • Control available transitions

71. states can: • Assign permissions to roles • Control available transitions • and, less well known:

72. assign roles to groups!

73. transitions

74. Image Credit: A walk into the bamboo paths (http://www.ﬂickr.com/photos/fotopakismo/2390882485/) a Creative Commons by-nc-nd (2.0) image from fotopakismo's photostream

75. transitions control:

76. transitions control: • Where you end up

77. transitions control: • Where you end up • How you start the journey

78. transitions control: • Where you end up • How you start the journey • user-initiated or automatic

79. transitions control: • Where you end up • How you start the journey • user-initiated or automatic • Who can make the trip

80. transitions control: • Where you end up • How you start the journey • user-initiated or automatic • Who can make the trip • permission(s), role(s) or membership in group(s)

81. the rubber meets the road Image Credit: Transformers (http://www.ﬂickr.com/photos/hoffarth/4506050669/), a Creative Commons by-nc-nd (2.0) image from hoffarth's photostream

82. A simple workﬂow app

83. A simple workﬂow app • User submits a request for travel expenses

84. A simple workﬂow app • User submits a request for travel expenses • Approver approves or denies the request

85. A simple workﬂow app • User submits a request for travel expenses • Approver approves or denies the request • If denied, the user can edit and re-submit

86. A simple workﬂow app • User submits a request for travel expenses • Approver approves or denies the request • If denied, the user can edit and re-submit • Accountant issues a reimbursement check

87. A simple workﬂow app • User submits a request for travel expenses • Approver approves or denies the request • If denied, the user can edit and re-submit • Accountant issues a reimbursement check • Request is closed

88. What do we need?

89. What do we need? • A Simple Content Type

90. What do we need? • A Simple Content Type • Title, Description, Amount and Receipt

91. What do we need? • A Simple Content Type • Title, Description, Amount and Receipt • A Workﬂow

92. What do we need? • A Simple Content Type • Title, Description, Amount and Receipt • A Workﬂow • New Request, Awaiting Approval, Approved, Denied, Closed

93. What do we need? • A Simple Content Type • Title, Description, Amount and Receipt • A Workﬂow • New Request, Awaiting Approval, Approved, Denied, Closed • A Pair of Roles

94. What do we need? • A Simple Content Type • Title, Description, Amount and Receipt • A Workﬂow • New Request, Awaiting Approval, Approved, Denied, Closed • A Pair of Roles • Approver, Accountant

95. What do we need? • A Simple Content Type • Title, Description, Amount and Receipt • A Workﬂow • New Request, Awaiting Approval, Approved, Denied, Closed • A Pair of Roles • Approver, Accountant • or do we?

96. What Tools to Use?

97. What Tools to Use? For the Content Type: ZopeSkel?? AGX??

98. What Tools to Use? For the Content Type: ZopeSkel?? AGX?? For the Workﬂow: collective.wtf ?? ZMI & portal_setup???

99. or, perhaps . . .

100. dexterity & uwosh.northstar

101. start with a buildout

102. start with a buildout

103. start up instance

104. fresh plone site

105. fresh plone site

106. (it works in plone 3, too)

107. you’ll install two products

108. you’ll install two products

109. they’ll install dependencies

110. they’ll install dependencies

111. new control panels

112. new control panels

113. we need a simple content type

114. make a content type

115. make a content type

116. set up type basics

117. add ﬁelds

118. add ﬁelds

119. add ﬁelds

120. add ﬁelds

121. amount ﬁeld (ﬂoat)

122. receipt ﬁeld (ﬁle)

123. add behaviors (basic capabilities)

124. we also need a workﬂow

125. create new workﬂow

128. edit existing states

132. add new state(s)

133. add transition(s)

141. assign workﬂow to type

142. assign workﬂow to type

143. and that’s it!

144. a quick live demo

145. • Permissions & Roles • Inheritance of Rights • Workﬂow: States and Transitions • Advanced Techniques

146. content rules

147. content rules no programming needed

148. per-ﬁeld permissions

149. • Show different aspects of a type to different users

150. • Show different aspects of a type to different users • Show different aspects of a type to the same user in different states

151. • Show different aspects of a type to different users • Show different aspects of a type to the same user in different states • Allow users to edit only certain ﬁelds

152. • Show different aspects of a type to different users • Show different aspects of a type to the same user in different states • Allow users to edit only certain ﬁelds • Change which ﬁelds can be edited by state

153. • Show different aspects of a type to different users • Show different aspects of a type to the same user in different states • Allow users to edit only certain ﬁelds • Change which ﬁelds can be edited by state • and so on . . .

154. Image Credit: Mona Lisa (http://www.ﬂickr.com/photos/caribb/2355878576/"), a Creative Commons by-nc-nd (2.0) image from caribb's photostream

155. Image Credit: Les Demoiselles d'Avignon(http://www.ﬂickr.com/photos/webtweakers/2511681891/), a Creative Commons by-nc-nd (2.0) image from webtweakers's photostream

156. transition actions script (before) script (after)

157. ﬁlesystem python scripts

158. ﬁlesystem python scripts cannot be overridden

159. workﬂow events IBeforeTransitionEvent IAfterTransitionEvent

160. • which workﬂow was used

161. • which workﬂow was used • old and new workﬂow states

162. • which workﬂow was used • old and new workﬂow states • which transition is happening (has happened)

163. • which workﬂow was used • old and new workﬂow states • which transition is happening (has happened) • status of the object

164. • which workﬂow was used • old and new workﬂow states • which transition is happening (has happened) • status of the object • the object itself

165. imagine the possibilities Image Credit: I'm So Excited (http://www.ﬂickr.com/photos/expo86/1907930897/), a Creative Commons Attribution Non-Commercial No-Derivative-Works (2.0) image from expo86's photostream

166. Thanks to:

167. WebLion

168. the Penn State University

169. cewing@uw.edu

Yes It Can: Leverage Workflow in Plone to Bring Business Process Online

You are reading a preview.

Check these out next

Yes It Can: Leverage Workflow in Plone to Bring Business Process Online

More Related Content

Similar to Yes It Can: Leverage Workflow in Plone to Bring Business Process Online (20)

More from Cristopher Ewing (8)

Recently uploaded (20)