Criando um Worflow personalizado através de um gerenciador de conteúdo web para um grupo de usuários, por meio do Alfresco 3

"Workflow is an automation of a business process, during which documents are passed from one participant to another for action, according to a set of procedural rules. Every content management system implementation will have workflow requirements. Workflow provides ownership and control on the content and processes. 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. WCM Workflows can be configured for each form or for any arbitrary set of non-form assets.

In this article by Amita Bhandari, co-author of the book Alfresco 3 Web Content Management, we will take a look at the creation of a custom WCM workflow for a group.

(For more resources on Alfresco 3, see here.)

You can define and deploy your own task-oriented workflows in the Alfresco repository. However, you need to follow a particular format to define your workflow and a particular process to deploy it in Alfresco. Workflows can be deployed manually (which requires a restart of the server) and dynamically (without starting the server). For now we will deploy the workflow manually. These customizations are typically deployed via the alfresco/extension folder and require the Alfresco server to be restarted to take effect. In the later examples, we will deploy using the dynamic approach.

As an example, we will configure one workflow. The use case scenario is as follows.

There is a section of Blogs and News on the Cignex website, which needs to be updated monthly. The blog has to be published regularly. In order to publish, one needs to follow some process that can be defined in a workflow. The blog has to be reviewed by three different groups. Each group has different roles. Groups approve the blog one at a time and in order. When the blog is submitted, it will go to the first group. All the users belonging to that group will receive a notification via a task in the My Pooled Tasks dashlet. Any one of the users can take ownership and approve or reject the task. If rejected, it will go to the initiator. On approval it will go to next group and the process will continue for all three groups. Once the process is complete, a notification will be sent to the initiator. Also the blog would be submitted to the Staging box."

Leia o artigo completo em

2 comentários:

  1. Muito útil o blog. Falar em arquivologia sem vínculo direto às possibilidades que a tecnologia oferece é impensável atualmente. Vi a indicação desse blog no e aprovei!!!