Quản lý cấu hình web - part 22 ppt

WCM Workows [ 192 ] 8. Click on Finish. 9. Log in as user Mark. Submit the Blog to the Staging box. We will also see how the launch date functions. Click on OK. 10. On submit, the Submit Items wizard will open as shown in the following screenshot. You can select the launch date as shown in the screenshot. If you want to make changes in the conguration of a workow you can click on Congure Workow as well. Click on OK: Download from Wow! eBook <www.wowebook.com> Chapter 5 [ 193 ] 11. Log in as a user of group Technical Reviewer. Consider we have logged in as Jennifer Bruce. Congure the My Pooled Tasks dashlet. This dashlet is required for group workows. Repeat the same steps for Kristie Dawid. For now, both the users will be able to see the task in their dashlet. No other group can see the task, as this workow is for serial ow. A group will see the task in the order they are assigned. 12. Any one of the users of the group has to take ownership. Click on Take Ownership. Download from Wow! eBook <www.wowebook.com> WCM Workows [ 194 ] 13. You will notice that the task now appears in the My Task To Do dashlet. 14. Open the Manage Task dialog. You are also given the facility to leave the ownership. Click on Return To Pool. Download from Wow! eBook <www.wowebook.com> Chapter 5 [ 195 ] 15. You will nd again that the task appears in My Pooled Task. This gives the advantage for both the users to take the ownership and approve the task. 16. Consider that Jeniffer Bruce has taken the ownership and approved the task. As soon as ownership is taken, the task disappears from the other two users. 17. Once approved by users of the Technical Reviewer group, log in as user LeRoy Fuess of the Editorial group and approve the items. Download from Wow! eBook <www.wowebook.com> WCM Workows [ 196 ] 18. Once approved by LeRoy Fuess of the Editorial group, log in as Michael Alison of the Publisher group and approve the items (you can log in with any user of the group, take ownership, and approve the task). 19. After being approved by all the groups, the task appears in the My Task To Do dashlet of Mark, who has initiated the process for submitting the content. The content is not submitted yet, as the Launch date is 12 December 2009 15:54. 20. You will nd the content in the Staging Sandbox in Content Awaiting Launch item. The content will be automatically submitted on 12 December 2009 15:54. 21. Open the Manage Task dialog. You can either Abort Submission or Submit Now. If you click on Submit Now, it will submit the content to the Staging box. On clicking Abort Submission, the content will not be submitted. Download from Wow! eBook <www.wowebook.com> Chapter 5 [ 197 ] 22. On clicking Abort Submission, you will notice the task in My Task To Do. Download from Wow! eBook <www.wowebook.com> WCM Workows [ 198 ] 23. Open the task and click on Task Done. After that you can see the les again in the Modied Items section. 24. If you have to submit a Blog, start the process again. Expiring content in WCM For any changes promoted to the site, specic expiration dates can be set on a global or asset-by-asset basis. Expiration is the only indication that the content is expired. The content is not disabled or hidden in the Staging Sandbox. Upon expiration, end users are automatically assigned the asset as a task so that they can determine whether the asset should be updated or removed from the site. The repository checks periodically for expired items. When any expired items are found they are added to a workow and sent to the user that last modied the asset. If multiple items are destined for the same user, they are batched up into a workow for each website the asset belongs to. Clicking on the task will launch the Manage Task dialog that lists all of the expired items, from here the assigned user can perform the relevant action on each item. These changes occur in isolation from the user's sandbox, thus not affecting any work that they may currently be doing in their sandbox. The workow, however, is layered over the user's sandbox so any changes that they have made in their sandbox will be visible. Conguration Conguration for content expiration is in one le—scheduled-jobs-context.xml. You'll nd the le in the Alfresco package, that is tomcat-home/webapps/alfresco/ WEB-INF/classes/alfresco /scheduled-jobs-context.xml . It contains the conguration for the frequency of expired item checks. By default it is set to check once a day at 3:30 a.m. as can be seen in the following cron expression: Download from Wow! eBook <www.wowebook.com> Chapter 5 [ 199 ] <bean id="avmExpiredContentTrigger" class="org.alfresco.util. CronTriggerBean"> <property name="jobDetail"> <bean id="avmExpiredContentJobDetail" class="org.springframework.scheduling.quartz.JobDetailBean"> <property name="jobClass"> <value>org.alfresco.repo.avm.AVMExpiredContentJob</value> </property> <property name="jobDataAsMap"> <map> <entry key="expiredContentProcessor"> <ref bean="avmExpiredContentProcessor" /> </entry> </map> </property> </bean> </property> <property name="scheduler"> <ref bean="schedulerFactory" /> </property> <! trigger at 3:30am each day > <property name="cronExpression"> <value>0 30 3 * * ?</value> </property> </bean> You can make the changes for cron expression and check the expiration date functionality. Changes can be also made directly to these les, but better practice would suggest to make changes in content-expiration-debug-context.xml.sample located at <install-alfresco>/tomcat/shared/classes/alfresco/extension/. Rename the le to content-expiration-debug-context.xml. Paste the previous code with changes in cron expression as suggested in the following: <property name="cronExpression"> <value>0 3 * * * ?</value> </property> This will run the scheduler in every three minutes and will check for the expired item. Download from Wow! eBook <www.wowebook.com> WCM Workows [ 200 ] Submit any item and apply expiration date as mentioned in the following screenshot: Process the workow as explained in the previous sections. After 14 December 2009 15:45, you will nd a task in the My Task To Do dashlet as shown in the following screenshot: Download from Wow! eBook <www.wowebook.com> Chapter 5 [ 201 ] Open the Manage Task dialog. The dialog displays two buttons as shown in the following screenshot. Both signal that all changes have been made and will therefore apply the changes to the user's sandbox. The bottom button, Task Done & Re- Submit All, will immediately launch the Submit dialog so that the users can submit their changes. Whereas the Task Done button will just apply the changes and users can then pick and choose when and which items to submit. Summary Workows are an important aspect in Alfresco WCM. Alfresco web project uses workows to support any set of changes, either automated or user-driven steps, in a business process before nal commit to the Staging Sandbox. In this chapter we have learned the following points: • Alfresco includes two ows of workows out of the box. One is serial oriented and the other one is the parallel workow. • Auto review of date for submission can be made using launch and expiry date. • Workow can be congured for a web form and web project. • Whenever content is submitted, a snapshot is automatically taken of staging to provide an archive of the current version of the site. Download from Wow! eBook <www.wowebook.com> . is in one le—scheduled-jobs-context.xml. You'll nd the le in the Alfresco package, that is tomcat-home/webapps/alfresco/ WEB- INF/classes/alfresco /scheduled-jobs-context.xml . It contains. changes in content-expiration-debug-context.xml.sample located at <install-alfresco>/tomcat/shared/classes/alfresco/extension/. Rename the le to content-expiration-debug-context.xml. Paste. from Wow! eBook <www.wowebook.com> Chapter 5 [ 197 ] 22. On clicking Abort Submission, you will notice the task in My Task To Do. Download from Wow! eBook <www.wowebook.com> WCM Workows [