[Neos] Thought about implementing workflows

[Dominique Feyer]

Really nice idea, how this kind of workflow are configured in Drupal ?

I think that we can work with a Worklow.yaml to define:

1. Trigger
2. Action
3. Receipe

A lots of inspiration can be found in service like
https://ifttt.com/wtfbut with the possibility to nest the receipe.

With the power of EEL the configuration can look like this:
https://gist.github.com/dfeyer/8562868

The actions "type" are based on available Signal in Neos or CR

In a second step we can work on a backend module to view the current
Workflow, and maybe event check where the current node in in the worflow
process.

Sounds like we have a new challenge ;)

Dominique

ttree sarl
Dominique Feyer
TYPO3 Addict
Rue du Valentin 34 et demi
CH - 1004 Lausanne
Téléphone +41 21 312 36 35
www.ttree.ch | twitter <http://twitter.com/ttreeagency> |
linkedin<http://www.linkedin.com/company/ttree/>
Plan d'accès: http://g.co/maps/4yu6t


2014/1/22 Michael Schams <typo3ml at schams.net>

> On 22/01/14 23:16, Søren Malling wrote:
>
>  A newsmedia distribution of TYPO3 Neos, can have a, and multiple, "rules"
>> saying
>> "When this nodetype, Newsletter, is published, sent it to the following
>> distribution lists"
>>
>
> I assume, this "rules" concept would also supports cascading rules?
>
> E.g.: editor (A) -> proofreader (B) -> manager (C) -> publisher (D)
>
> "This node, edited by a user from group A must be proof-read by a user
> from group B, before someone of group C can review/approve it, and then a
> publisher (group D) can review/publish it"
>
>
> Cheers
> Michael
>
>
> _______________________________________________
> Neos mailing list
> Neos at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/neos
>