This wiki does not contain official documentation and is currently deprecated and read only. Please try reading the documentation on the Liferay Developer Network, the new site dedicated to Liferay documentation. DISCOVER Build your web site, collaborate with your colleagues, manage your content, and more. DEVELOP Build applications that run inside Liferay, extend the features provided out of the box with Liferay's APIs. DISTRIBUTE Let the world know about your app by publishing it in Liferay's marketplace. PARTICIPATE Become a part of Liferay's community, meet other Liferay users, and get involved in the open source project.

Wiki

Workflow Configuration

Detalles Imprimir
Etiquetas: workflow liferay 6.0 workflow 6

The Workflow Configuration portlet allows the community administrator to configure which workflow definition will apply to each community's entity.

In this portlet by default there are the following entities that can be assigned a workflow definition:

  1. Wiki Page
  2. Web Content
  3. Document Library Document (moved to portlet in 6.1+)
  4. Blogs Entry
  5. Comments
  6. Message Boards Message

More custom developed entities can be added here.

Note: The default behaviour is workflow being disabled

1 Adjunto
39524 Accesos
Promedio (4 Votos)
La valoración media es de 1.75 estrellas de 5.
Comentarios
Respuestas anidadas Autor Fecha
I find this interface very intuitive. I whould... Matthieu Levesque 5 de octubre de 2010 8:05
How to add another entity "Announcements" to be... Satoru Funai 6 de febrero de 2012 21:44
I have a custom portlet for a Ticket asset. I... Nathan Harrell 28 de enero de 2014 13:21

Matthieu Levesque
I find this interface very intuitive. I whould like to have an example of a Workflow definiting instead.
Publicado el día 5/10/10 8:05.
Satoru Funai
How to add another entity "Announcements" to be assigned a workflow definition?
Satoru Funai
Publicado el día 6/02/12 21:44.
Nathan Harrell
I have a custom portlet for a Ticket asset. I need a workflow that will start on the click of a 'request to open' button, not when the entity is saved to the DB; the final state would be approved, as in 'approved to open'. I need another workflow to start with the click of a 'request to close' button; again with final state to be approved, as in 'approved to close'. If I create to workflow definitions (ex., request_to_open.xml and request_to_close.xml) is it possible to select more than one definition from the entities configuration drop down. Has anyone been able to use Kaleo in this way? Any advice/suggestions/examples are GREATLY appreciated!!

Nathan Harrell
Publicado el día 28/01/14 13:21.