Re: allowing content rules to be launched by other rules

Nathan Van Gheem <[email protected]>
Newsgroups gmane.comp.web.zope.plone.devel
Message-ID <CAL8hw9GtiStQ4ar0B7n-mhktzdDGar2D_2mgMHAJPhwB+7Dm5w@mail.gmail.com>
+1


On Sun, Jul 7, 2013 at 3:11 PM, thomas desvenain <[email protected]
> wrote:

> Hi
>
> Today, a content rule can't be launched by an event triggered during the
> execution of an other rule.
> This avoids behavior unexpected for user an probably many errors.
> the 'rule_filter' ensures that.
>
> But I think that it could be useful that sometimes, a rule can be
> triggered from an other rule.
>
> for example : a rule that automatically 'publish' a content when it is
> added should trigger a rule that sends an email when a content is published.
>
> What do you think about an option on the rule, unselected by default, to
> allow the rule to be launched during an other rule ?
>
> I would be pleased to implement it, but I'd like to know about your
> opinion.
>
> Thanks
>
> Thomas
>
> --
> Thomas Desvenain
>
> Téléphone : 09 51 37 35 18
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Plone-developers mailing list
> Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/plone-developers
>
>


-- 
Nathan Van Gheem
Solutions Architect
Wildcard Corp

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev

_______________________________________________
Plone-developers mailing list
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.