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

On submit, the Submit Items wizard will open as shown in the following screenshot.. You will notice that the task now appears in the My Task To Do dashlet.. Once approved by users of th

Trang 1

[ 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 configuration of a workflow you can click on

Configure Workflow as well Click on OK:

Download from Wow! eBook <www.wowebook.com>

Trang 2

[ 193 ]

11 Log in as a user of group Technical Reviewer Consider we have logged in

as Jennifer Bruce Configure the My Pooled Tasks dashlet This dashlet is required for group workflows 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 workflow is for serial flow 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.

Trang 3

[ 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.

Trang 4

[ 195 ]

15 You will find 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.

Trang 5

[ 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 find 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.

Trang 6

[ 197 ]

22 On clicking Abort Submission, you will notice the task in My Task To Do.

Trang 7

[ 198 ]

23 Open the task and click on Task Done After that you can see the files again

in the Modified 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, specific 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 workflow and sent to the user that last modified the asset

If multiple items are destined for the same user, they are batched up into a workflow 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 workflow, however, is layered over the user's sandbox so any changes that they have made in their sandbox will be visible

Configuration

Configuration for content expiration is in one file—scheduled-jobs-context.xml You'll find the file in the Alfresco package, that is tomcat-home/webapps/alfresco/ WEB-INF/classes/alfresco /scheduled-jobs-context.xml It contains the configuration 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:

Trang 8

[ 199 ]

<bean id="avmExpiredContentTrigger" class="org.alfresco.util.

CronTriggerBean">

<bean id="avmExpiredContentJobDetail"

class="org.springframework.scheduling.quartz.JobDetailBean"> <property name="jobClass">

<value>org.alfresco.repo.avm.AVMExpiredContentJob</value>

</property>

<map>

</entry>

</map>

</property>

</bean>

</property>

</property>

<! trigger at 3:30am each day >

<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 files, 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 file to content-expiration-debug-context.xml

Paste the previous code with changes in cron expression as suggested in

the following:

<value>0 3 * * * ?</value>

</property>

This will run the scheduler in every three minutes and will check for the

expired item

Trang 9

[ 200 ]

Submit any item and apply expiration date as mentioned in the following screenshot:

Process the workflow as explained in the previous sections

After 14 December 2009 15:45, you will find a task in the My Task To Do dashlet as

shown in the following screenshot:

Trang 10

[ 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 Re-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

Workflows are an important aspect in Alfresco WCM Alfresco web project uses workflows to support any set of changes, either automated or user-driven steps, in a business process before final commit to the Staging Sandbox In this chapter we have learned the following points:

• Alfresco includes two flows of workflows out of the box One is serial

oriented and the other one is the parallel workflow

• Auto review of date for submission can be made using launch and

expiry date

• Workflow can be configured 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

Định dạng
Số trang	10
Dung lượng	6,12 MB