<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://groups.drupal.org" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Workflow</title>
 <link>http://groups.drupal.org/workflow</link>
 <description>Improving the workflow and actions modules!</description>
 <language>en</language>
<item>
 <title>Workflow problem saving node</title>
 <link>http://groups.drupal.org/node/15714</link>
 <description>&lt;p&gt;Hey, I&#039;m testing the workflow module on my site, and I&#039;m having a problem with it that I hope one of you can help me with.&lt;/p&gt;
&lt;p&gt;I&#039;m using Drupal 5.6 , Workflow 5.x-2.3, Workflow access 5.x-2.3, Actions 5.x-2.6, Trigger Unlock 6.x-1.0 (which can supposedly work with Drupal 5).&lt;/p&gt;
&lt;p&gt;I set up five workflow states for one of my content types, called &quot;Press Releases&quot;. The assigned actions for each transition is to change the workflow state, and to publish or unpublish the node.&lt;/p&gt;
&lt;p&gt;When I try to create a new Press Release, it hangs after I hit Submit. If I go look at the content menu, I see that it&#039;s created the node, but only the title is there. The rest of the content is missing. If I try to update that node, I get the same problem when I hit Submit. When I try to delete that incomplete node, it&#039;ll allow me to delete, but I get the following error message:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;user warning: Out of range value adjusted for column &#039;sid&#039; at row 1 query: _workflow_write_history INSERT INTO workflow_node_history (nid, old_sid, sid, uid, comment, stamp) VALUES (17074, 11, -1, 8, &#039;Node deleted&#039;, 0) in F:\Program Files\Apache Software Foundation\Apache2.2\htdocs\includes\database.mysql.inc on line 172.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;This problem didn&#039;t exist before I set up the workflow, and it doesn&#039;t exist for any other content type. I disabled and uninstalled Workflow, Workflow Access, Actions, and Trigger Unlock, yet I&#039;m still unable to create any Press Release content.&lt;/p&gt;
&lt;p&gt;I would appreciate any help you can provide.&lt;/p&gt;
&lt;p&gt;Thanks&lt;br /&gt;
David&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/15714#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/6755">action</category>
 <category domain="http://groups.drupal.org/taxonomy/term/6756">save node</category>
 <category domain="http://groups.drupal.org/taxonomy/term/6131">triggers</category>
 <category domain="http://groups.drupal.org/taxonomy/term/178">workflow</category>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Wed, 08 Oct 2008 20:39:28 +0000</pubDate>
 <dc:creator>dwhite10701</dc:creator>
 <guid isPermaLink="false">15714 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Workflow and cron (Drupal 5)</title>
 <link>http://groups.drupal.org/node/14895</link>
 <description>&lt;p&gt;I&#039;m searching a way to set multiple cron events for a workflow. A simple example for a node:&lt;br /&gt;
A publisher create a content:&lt;br /&gt;
[Created --&amp;gt; Wait for review]&lt;br /&gt;
An auditor then approve the content:&lt;br /&gt;
[Wait for review --&amp;gt; Approved]&lt;br /&gt;
Now i want to set two scheduled task to make this node first &quot;Published&quot; (i.e. in a week), then &quot;Archived&quot; (i.e. in two week), in order to make content available to all users for an entire week (without using the core function publish/unpublish content which needs &#039;administer nodes&#039; permission that is not too flexible for my needs).&lt;br /&gt;
With the module workflow-5.x-2.3 i can set up only a scheduled task at a time.&lt;br /&gt;
I try to develop a &quot;patch&quot; to make this possible: it&#039;s only a first approach to question, and indeed needs more work.&lt;br /&gt;
If there&#039;s someone interested, i&#039;ll be happy to develop and discuss together a better solution.&lt;br /&gt;
I will upload the modified module (with some comments) and the database patch as soon as possible.&lt;br /&gt;
P.S. Sorry for my english!&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/14895#comments</comments>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Mon, 15 Sep 2008 16:00:49 +0000</pubDate>
 <dc:creator>blackice78</dc:creator>
 <guid isPermaLink="false">14895 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Rules beta 1 released :)</title>
 <link>http://groups.drupal.org/node/14327</link>
 <description>&lt;p&gt;Check out &lt;a href=&quot;http://more.zites.net/rules/rules-beta-1-drupalcon&quot; title=&quot;http://more.zites.net/rules/rules-beta-1-drupalcon&quot;&gt;http://more.zites.net/rules/rules-beta-1-drupalcon&lt;/a&gt;!&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/14327#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/5750">rules</category>
 <group domain="http://groups.drupal.org/actions">Actions</group>
 <group domain="http://groups.drupal.org/austria">Austria</group>
 <group domain="http://groups.drupal.org/rules">Rules</group>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Wed, 27 Aug 2008 21:54:06 +0000</pubDate>
 <dc:creator>fago@drupal.org</dc:creator>
 <guid isPermaLink="false">14327 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Workflow States as Taxonomy?</title>
 <link>http://groups.drupal.org/node/14175</link>
 <description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I am building a site that has a complex workflow.  What I want to be able to do, is use my workflow states as a taxonomy in a way, and be able to show users a block on the sidebar, where they can see the different workflow states (and hopefully a count of how many nodes are in that state), and if they select one, see all of the nodes currently assigned to that state.&lt;/p&gt;
&lt;p&gt;How can this be achieved?&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/14175#comments</comments>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Fri, 22 Aug 2008 02:39:46 +0000</pubDate>
 <dc:creator>Iceman90</dc:creator>
 <guid isPermaLink="false">14175 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Workflow for Drupal 6 - How to trigger Actions?</title>
 <link>http://groups.drupal.org/node/14174</link>
 <description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I have installed Workflow for Drupal 6, and have it all set up, along with setting up many actions.  My question now, is how can I associate actions with the various stages and transitions in my workflow?  I can&#039;t seem to find any way to do this.&lt;/p&gt;
&lt;p&gt;Any help would be appreciated.&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/14174#comments</comments>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Fri, 22 Aug 2008 01:37:37 +0000</pubDate>
 <dc:creator>Iceman90</dc:creator>
 <guid isPermaLink="false">14174 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Examples of &quot;Execute custom PHP code&quot;?</title>
 <link>http://groups.drupal.org/node/13729</link>
 <description>&lt;p&gt;Hi All,&lt;/p&gt;
&lt;p&gt;Are there any &#039;execute custom php code&#039; examples available for workflow-ng v 2.1? I am trying to set &#039;alt_login&#039; username upon user creation:&lt;br /&gt;
&lt;div class=&quot;codeblock&quot;&gt;&lt;code&gt;$alt_login = $account;&lt;br /&gt;return array(&amp;quot;alt_login&amp;quot; =&amp;gt; $account);&lt;/code&gt;&lt;/div&gt;&lt;br /&gt;
but I guess that&#039;s too simplistic. Should I actually do it with SQL statements, etc? If so, are there any limitations on PHP execution via workflow-ng? Any code samples, etc?&lt;/p&gt;
&lt;p&gt;Thanks in advance,&lt;br /&gt;
Alex&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/13729#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/2895">examples</category>
 <category domain="http://groups.drupal.org/taxonomy/term/5968">workflow_ng</category>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Tue, 05 Aug 2008 12:07:41 +0000</pubDate>
 <dc:creator>Alexander Ufimtsev@drupal.org</dc:creator>
 <guid isPermaLink="false">13729 at http://groups.drupal.org</guid>
</item>
<item>
 <title>using workflow to create roles when an organic group is created</title>
 <link>http://groups.drupal.org/node/13209</link>
 <description>&lt;p&gt;a rather custom request i suppose, but could anyone give me some direction on how to create a workflow that does the following:&lt;/p&gt;
&lt;p&gt;create content type (organic group node)&lt;br /&gt;
create standard role using the title of the node created&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/13209#comments</comments>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Wed, 16 Jul 2008 03:52:08 +0000</pubDate>
 <dc:creator>krisbfunk</dc:creator>
 <guid isPermaLink="false">13209 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Rules 6.x-1.0 ALPHA1 is out!</title>
 <link>http://groups.drupal.org/node/13176</link>
 <description>&lt;p&gt;I&#039;ve just released ALPHA1.&lt;/p&gt;
&lt;p&gt;As you can see in the &lt;a href=&quot;http://groups.drupal.org/node/12476&quot;&gt;development status&lt;/a&gt;, there are still some important features missing. But the main UI (and the API) is already working - so check it out and give me feedback!&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/13176#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/5750">rules</category>
 <group domain="http://groups.drupal.org/rules">Rules</group>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Tue, 15 Jul 2008 08:26:32 +0000</pubDate>
 <dc:creator>fago@drupal.org</dc:creator>
 <guid isPermaLink="false">13176 at http://groups.drupal.org</guid>
</item>
<item>
 <title>UI of CCK, Panel and Workflow</title>
 <link>http://groups.drupal.org/node/13031</link>
 <description>&lt;p&gt;Just wanted to point out this link : &lt;a href=&quot;http://www.serena.com/mashups/sPR_06112008.html&quot; title=&quot;http://www.serena.com/mashups/sPR_06112008.html&quot;&gt;http://www.serena.com/mashups/sPR_06112008.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Because I have seen a demo yersteday and I found some functionnalities very similar to what CCK, Panel and workflow can do.&lt;/p&gt;
&lt;p&gt;You can watch the video and even dowload the tool for free to try to play with it.&lt;/p&gt;
&lt;p&gt;Maybe it can give you some good ideas for the next versions of CCK Panel and workflow modules.&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/13031#comments</comments>
 <group domain="http://groups.drupal.org/content-construction-kit-cck">Content Construction Kit (CCK)</group>
 <group domain="http://groups.drupal.org/panels">Panels</group>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Wed, 09 Jul 2008 10:18:14 +0000</pubDate>
 <dc:creator>Julien Marboutin</dc:creator>
 <guid isPermaLink="false">13031 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Workflow and passage of time</title>
 <link>http://groups.drupal.org/node/12910</link>
 <description>&lt;p&gt;A common requirement is to execute actions based on passage of time. Can I have some input on how you slick Drupal people out there have attacked this issue?&lt;/p&gt;
&lt;p&gt;An example. Let&#039;s say you have the stereotypical workflow of create -&amp;gt; approve -&amp;gt; publish. If the approver doesn&#039;t approve or disapprove within 1 week of node creation, an email reminder is to be sent to the approver.&lt;/p&gt;
&lt;p&gt;What&#039;s the most elegant way to trigger the email?&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/12910#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/5639">passage of time</category>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Fri, 04 Jul 2008 03:06:48 +0000</pubDate>
 <dc:creator>caign@drupal.org</dc:creator>
 <guid isPermaLink="false">12910 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Rules development status</title>
 <link>http://groups.drupal.org/node/12476</link>
 <description>&lt;p&gt;This page will be updated, so you can track the development status here.&lt;/p&gt;
&lt;h3&gt;Improvements in comparison to workflow-ng:&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Data Types:&lt;/strong&gt;&lt;br /&gt;
Arguments had an &quot;entity type&quot; in workflow-ng. This has been changed to data types, so that it fits also for primitive data types like strings and numbers. So rules contains support for the usual data types like node and user, but in contrast to workflow-ng it also treats strings as data types.&lt;br /&gt;
Also a lot of internal code has been restructured and improved - now rules is keeping an internal array of variables.&lt;br /&gt;
Status: implemented&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Writing conditions / actions:&lt;/strong&gt;&lt;br /&gt;
Writing conditions and actions has become even easier. Thanks to input evaluation system (see below) you don&#039;t have to care about token or php evaluation yourself. Furthermore you don&#039;t need to specify the to be saved settings like before in workflow-ng anymore, as rules will generate  useful default settings for you, which can be altered if desired.&lt;br /&gt;
As now data types like &quot;string&quot; are also supported one can also add needed strings to the argument list. For such primitive data types rules will provide a form for entering the data, which can be overridden and customized by the action. You need not do this, but in some cases it can be useful, e.g. for integrating with existing systems already specifying these arguments like the services module.&lt;br /&gt;
Also providing new variables has been simplified and works more straight forward.&lt;br /&gt;
Status: implemented&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Evaluated input:&lt;/strong&gt;&lt;br /&gt;
For the token integration rules will come with an input evaluation API and implementations for token and PHP input evaluation. So you can also do some simple php calculation in the input fields. Strings (and possible other data types) will be automatically evaluated so you don&#039;t have to care about this when writing actions.&lt;br /&gt;
Status: implemented. For token integration see &lt;a href=&quot;http://drupal.org/node/286803&quot;&gt;this issue&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Rule Sets&lt;/strong&gt;&lt;br /&gt;
The whole API has been overhauled to also work with rule sets - this are set of rules that work independent from events. So they are like a subroutine, which can be customized or also added by the UI.&lt;br /&gt;
Status: implemented&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Performance&lt;/strong&gt;&lt;br /&gt;
Rules supports an improved file inclusions system, which only includes the module integration files if necessary. Furthermore the internal caching system has been improved.&lt;br /&gt;
Status: Implemented, needs documentation.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Scheduling:&lt;/strong&gt;&lt;br /&gt;
Rules supports scheduled rule evaluation - so you&#039;ll be able to schedule everything.&lt;br /&gt;
Status: implemented, views integration is missing&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Label callbacks:&lt;/strong&gt;&lt;br /&gt;
Now label callbacks are supported for conditions, actions and new variables. So one can specify a better suiting label for configured conditions/actions, e.g. the &quot;content is type&quot; condition set to &quot;page&quot; will get the label &quot;content is page&quot;. Of course one can still customize the labels per UI too.&lt;br /&gt;
Status: implemented&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Drupal 6.x Actions support&lt;/strong&gt;&lt;br /&gt;
Status: implemented&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Logging&lt;/strong&gt;&lt;br /&gt;
The previously just for developers logging of rule execution has been improved to look better and provide a better overview. There will be a setting for enable this logging, so this assists one during the creation of rules.&lt;br /&gt;
Status: implemented&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Simple Tests&lt;/strong&gt;&lt;br /&gt;
Rules comes with a small module, which comes with some simple tests - which test the API to work correctly.&lt;br /&gt;
Status: implemented&lt;/p&gt;
&lt;h3&gt;Port from workflow-ng status&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Evaluation Engine [done]&lt;/li&gt;
&lt;li&gt;Basic UI [done]&lt;/li&gt;
&lt;li&gt;Port the whole module integration [done]&lt;/li&gt;
&lt;li&gt;States [TODO]&lt;/li&gt;
&lt;li&gt;CClinks [TODO]&lt;/li&gt;
&lt;li&gt;Per Entity Logs [TODO]&lt;/li&gt;
&lt;li&gt;Upgrade procedure [done]&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Modules shouldn&#039;t start porting their integration not before the first BETA release is there.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Todo list before a first BETA release:&lt;/strong&gt;&lt;br /&gt;
 * write developer documentation [in &lt;a href=&quot;http://drupal.org/node/298476&quot;&gt;done&lt;/a&gt;]&lt;br /&gt;
 * implement scheduling [done]&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Module integration status:&lt;/strong&gt;&lt;br /&gt;
 Node: ported&lt;br /&gt;
 User: ported&lt;br /&gt;
 System: ported&lt;br /&gt;
 Comment: ported&lt;br /&gt;
 Path: ported&lt;br /&gt;
 CCK: TODO&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/12476#comments</comments>
 <group domain="http://groups.drupal.org/rules">Rules</group>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Mon, 16 Jun 2008 16:00:06 +0000</pubDate>
 <dc:creator>fago@drupal.org</dc:creator>
 <guid isPermaLink="false">12476 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Workflow for Drupal 6.2</title>
 <link>http://groups.drupal.org/node/12463</link>
 <description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Im creating a site using Drupal 6.2.&lt;br /&gt;
I need to integrate the workflow module with this.&lt;/p&gt;
&lt;p&gt;the funtionalities i need are&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;users will submit cases (page with details along with attachments (video, pdf, doc etc))&lt;/li&gt;
&lt;li&gt;this will go to the reviewer, who reviews this,&lt;br /&gt;
 if rejected to notify the submitter with reasons&lt;/li&gt;
&lt;li&gt;If accepted, it should go to approvers, after accepting the case gets submitted.  &lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Do we any inbuilt module in Drupal to do this functions (like workflow in Drupal 5) in Drupal 6 or is there any other way of doing this in Drupal 6.2&lt;/p&gt;
&lt;p&gt;Thanks&lt;br /&gt;
Sumesh&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/12463#comments</comments>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Mon, 16 Jun 2008 08:15:48 +0000</pubDate>
 <dc:creator>sumachaa</dc:creator>
 <guid isPermaLink="false">12463 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Having an Event return a String</title>
 <link>http://groups.drupal.org/node/12064</link>
 <description>&lt;p&gt;I&#039;ve added a new event to a module that I&#039;m working on, but I would like to also be able to return a string.  Is there a entity type that would allow me to do this.  Ideally I would like to pass a string as an argument to the workflow_ng_invoke_event function and access the string&#039;s value as a token.&lt;/p&gt;
&lt;p&gt;If this doesn&#039;t exists, any pointers on how I might write the code to do this.&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/12064#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/1660">workflow-ng</category>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Fri, 06 Jun 2008 18:35:56 +0000</pubDate>
 <dc:creator>muenzer@drupal.org</dc:creator>
 <guid isPermaLink="false">12064 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Workflow actions</title>
 <link>http://groups.drupal.org/node/11393</link>
 <description>&lt;p&gt;I posted this over the the support area of workflow, but I also wanted to post this over here too.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://drupal.org/node/257258&quot; title=&quot;http://drupal.org/node/257258&quot;&gt;http://drupal.org/node/257258&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I don&#039;t know if I am missing something or what, but when had version 5x-1.x installed, the actions to publish and unpublish nodes as well as a group of others were listed as actions in the actions area of workflow. I wanted to automatically publish/unpublish nodes when it changed workflow states. Everything is there, and works correctly. But on 5.x-2 they are not an option.&lt;/p&gt;
&lt;p&gt;The Node action items of publish node, and unpublish node are not options in the actions (now Triggers area) pop-up even though they are listed on the actions page. What step am I missing here? Is this possible, to do or do I have to stick with 5.x-1.x to have this. Again, I must be missing a step here but any help would be appreciated.&lt;/p&gt;
&lt;p&gt;See the attached to see what is listed as workflow actions and what are the actions in the system.&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/11393#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/178">workflow</category>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Sun, 11 May 2008 21:11:36 +0000</pubDate>
 <dc:creator>myersca</dc:creator>
 <guid isPermaLink="false">11393 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Workflow + Workflow_ng + workflow_owner = Advanced workflows for drupal</title>
 <link>http://groups.drupal.org/node/11013</link>
 <description>&lt;p&gt;Hey folks.&lt;/p&gt;
&lt;p&gt;Here is a custom solution we developed for Amnesty International which is now released to contrib!&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://pajamadesign.com/2008/04/24/advanced-workflow-configuration-for-drupal/&quot;&gt; Advanced workflow for drupal&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The standard workflow module allows for the definition of arbitrary states and logging, however it does not provide any ownership of those states. In a small website with three or four moderators, this is fine. Stories placed in the “review” state will end up in a queue via views/workflow integration, and moderators will pick through them, moving their states as needed. In our case, each node may have a different fact checker, editor, Sr. editor and translation coordinator who will be responsible for pushing it through the process.&lt;/p&gt;
&lt;p&gt;In addition:&lt;/p&gt;
&lt;p&gt;this doesn’t solve the problem of notifying owners when they become responsible. Not everyone is tied to their computer refreshing this page, so we had to develop a solution for this. We contacted Fago soon after workflow_ng was released in beta, and we decided to gamble on this  excellent, nay inspired module.&lt;/p&gt;
&lt;p&gt;See the post for more information on how we put together this package.  I&#039;d love it if others could test it out and get it working for them.&lt;/p&gt;
&lt;p&gt;Best,&lt;br /&gt;
Jacob&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/11013#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/4978">worfklow</category>
 <category domain="http://groups.drupal.org/taxonomy/term/4979">worfklow_ng</category>
 <category domain="http://groups.drupal.org/taxonomy/term/4980">workflow_owner</category>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Fri, 25 Apr 2008 20:41:30 +0000</pubDate>
 <dc:creator>JacobSingh@drupal.org</dc:creator>
 <guid isPermaLink="false">11013 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Documentation?!?!</title>
 <link>http://groups.drupal.org/node/10863</link>
 <description>&lt;p&gt;Hi I have installed workflow-ng on drupal 5.7 and I can&#039;t figure out how to allow users to change a state. I have created a state machine with 2 states and connected them with a specific content type. when I either edit or view that content type I cant see any way to change the state of the content? I have read the documentation but it doesnt talk about the state machine.&lt;/p&gt;
&lt;p&gt;Once I get the state machine working I will fire an email if the state is changed to a certain &quot;finished&quot; state so that I can then view the node.&lt;/p&gt;
&lt;p&gt;Any help would be greatly appreciated.&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/10863#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/4916">states machine</category>
 <category domain="http://groups.drupal.org/taxonomy/term/1660">workflow-ng</category>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Mon, 21 Apr 2008 10:08:56 +0000</pubDate>
 <dc:creator>craigntammy@drupal.org</dc:creator>
 <guid isPermaLink="false">10863 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Workflow-ng with Token substitution/replacement fails on Fresh Drupal Install</title>
 <link>http://groups.drupal.org/node/10803</link>
 <description>&lt;p&gt;Hi folks&lt;/p&gt;
&lt;p&gt;I&#039;m a newbie to this module and need a little help please :)&lt;/p&gt;
&lt;p&gt;After a fresh install of Drupal 5.7, I added and enabled the latest Token and Workflow-ng modules only. The token substitutions fail right &quot;out of the box&quot;. For example, if I activate the sample rule called &lt;em&gt;Print the content title of pages and stories and at the top of nodes&lt;/em&gt;, it prints:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Workflow-ng example: The title of this post is [node:title].&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;If I create ANY rules with token replacement, they aren&#039;t replaced. I&#039;ve tried:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Changing the weight of Token in the system table.&lt;/li&gt;
&lt;li&gt;Doing a fresh install on an entirely different system running PHP/MySQL version 4.x.&lt;/li&gt;
&lt;li&gt;Disabling/Re-enabling the modules.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The only way I&#039;ve got token substitution to work is with version 5.x-1.3 - and even then not all fields were substituted! Versions 5.x-1.4 and above fail in this respect.&lt;/p&gt;
&lt;p&gt;Any ideas anyone? I can&#039;t believe anyone else hasn&#039;t discovered this! Everything else about this module seems really great, I&#039;d love to use it :)&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;
&lt;p&gt;Russ.&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/10803#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/4893">token replacement</category>
 <category domain="http://groups.drupal.org/taxonomy/term/4892">token substitution</category>
 <category domain="http://groups.drupal.org/taxonomy/term/1660">workflow-ng</category>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Thu, 17 Apr 2008 19:45:37 +0000</pubDate>
 <dc:creator>Russtavo</dc:creator>
 <guid isPermaLink="false">10803 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Problem with workflow_ng + nodeprofile, please help! </title>
 <link>http://groups.drupal.org/node/9977</link>
 <description>&lt;p&gt;I have a nodeprofile field type that can be for example &quot;group 1&quot;, &quot;group 2&quot;, or &quot;group 3&quot;.&lt;br /&gt;
Every time a new user registers, I want different emails to be sent to different users based on this type field.&lt;br /&gt;
I add a new rule configuration and I choose the &quot;User has registered&quot; event.&lt;br /&gt;
The problem is that when I try to add a condition, the only relative thing I can choose from there is&lt;br /&gt;
&quot;User has nodeprofile&quot;. How can I access my type nodeprofile field???&lt;br /&gt;
I have tried the  &quot;Textual comparison&quot; too but I had no luck.&lt;br /&gt;
What should I do?&lt;br /&gt;
Help! I really need to finish this!&lt;br /&gt;
Any advice is welcome.&lt;br /&gt;
Thank you&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/9977#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/635">nodeprofile</category>
 <category domain="http://groups.drupal.org/taxonomy/term/1660">workflow-ng</category>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Thu, 20 Mar 2008 18:25:42 +0000</pubDate>
 <dc:creator>pirandelo</dc:creator>
 <guid isPermaLink="false">9977 at http://groups.drupal.org</guid>
</item>
<item>
 <title>triggering other CCK fields with Workflow</title>
 <link>http://groups.drupal.org/node/9947</link>
 <description>&lt;p&gt;So I have a CCK form for a &quot;problem submission&quot; form. The authenticated user pulls up the form, fills out the fields displayed (field permissions hides fields that the office fills out) and hits submit. Then the office can go in and make changes, add information and update the &quot;progress&quot; (workflow) of the problem. Anytime the status changes (&#039;submitted&#039;, in progress&#039;, &#039;oh hold&#039;, &#039;completed&#039; etc.) I have the Actions module send an email to the author. Everything is working fine, but I would like to extend it in one way, and this is what I need help with:&lt;/p&gt;
&lt;p&gt;1.) I&#039;d like to have a date stamp placed in a field of the form when the &quot;progress&quot; (workflow status) changes to completed. This way I can search sort the cck fields by &quot;date completed&quot;.&lt;/p&gt;
&lt;p&gt;I&#039;m open for creative suggestions on this! :o)&lt;/p&gt;
&lt;p&gt;Thanks in advance.&lt;br /&gt;
Nate&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/9947#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/108">CCK</category>
 <category domain="http://groups.drupal.org/taxonomy/term/178">workflow</category>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Wed, 19 Mar 2008 18:31:47 +0000</pubDate>
 <dc:creator>miller.nw</dc:creator>
 <guid isPermaLink="false">9947 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Problem with modify the work flow map</title>
 <link>http://groups.drupal.org/node/9331</link>
 <description>&lt;p&gt;In my website i have 2 flow flow already, when i create a new work flow and sign the node type into the new work flow, all the old content page of this type show errors in the work flow part. It seems like that the old content still link to the old work flow and the new work flow can only work well in the new content. I don&#039;t want to delete all the related content in work flow transfer and create the new ones, does any one could help me?&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/9331#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/4255">work flow</category>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Mon, 03 Mar 2008 08:28:04 +0000</pubDate>
 <dc:creator>raymanda</dc:creator>
 <guid isPermaLink="false">9331 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Workflow fields on node creation...help!</title>
 <link>http://groups.drupal.org/node/9008</link>
 <description>&lt;p&gt;Hi group....I&#039;ve run out of ideas to search for, so I&#039;m hoping any of you might be able to help.&lt;/p&gt;
&lt;p&gt;I have set up a workflow for a CCK node type with only two states: &quot;Requested&quot; and &quot;Read&quot;. Workflow NG provides email notifications beautifully. I am trying to hide one of the CCK fields in the node creation step using the Workflow_fields module.&lt;/p&gt;
&lt;p&gt;I have set up the permissions on the Workflow_fields module to show the field in question only during the &quot;Read&quot; state, but not on the &quot;Requested&quot; state.&lt;/p&gt;
&lt;p&gt;My problem is that until the node is actually submitted, it does not change from the default &quot;(create)&quot; step to the &quot;Requested&quot; state, and thus the Workflow_fields module has no effect when I need it.&lt;/p&gt;
&lt;p&gt;Since Workflow_fields does not allow to set permissions on the (create) state, is there a way to make a node &quot;skip&quot; the (create) state (I.E. be &quot;born&quot; in the &quot;Requested&quot; state)? If not, can any one point me in the right direction as to an alternative way to do this?&lt;/p&gt;
&lt;p&gt;Many Thanks!&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/9008#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/178">workflow</category>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Tue, 19 Feb 2008 03:39:12 +0000</pubDate>
 <dc:creator>simonmd</dc:creator>
 <guid isPermaLink="false">9008 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Best way extend workflow</title>
 <link>http://groups.drupal.org/node/8985</link>
 <description>&lt;p&gt;Hey guys,&lt;/p&gt;
&lt;p&gt;So I need to extend workflow slightly, I&#039;ve got to create a field which will give the estimated amount of time that a content type should stay in a particular state. Is the best way to do this to patch workflow or create another module?&lt;/p&gt;
&lt;p&gt;--&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/8985#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/178">workflow</category>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Mon, 18 Feb 2008 14:23:52 +0000</pubDate>
 <dc:creator>xsyn</dc:creator>
 <guid isPermaLink="false">8985 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Multi-level workflow?</title>
 <link>http://groups.drupal.org/node/7990</link>
 <description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I am currently working on a project where the same workflow is involved at several levels. More specifically, there are two interrelated roles: Authors and Validators. The trick is that a Validator at level N can also be an Author at level N+1. The number of levels is undefined (typically between 2 and 10).&lt;/p&gt;
&lt;p&gt;Using the &#039;classic&#039; (not ng) workflow module, I created the workflow matrix for level N with no problem. Now, if I declare a user X with both Author (for level N) and Validator (for level N+1) roles, on cases where some transitions are allowed for Authors and some others for Validators, the workflow tab for a node created by X will include the union of all these transitions, which is obviously not what I want.&lt;/p&gt;
&lt;p&gt;So basically the question is how to deal with that? I don&#039;t want to create a whole bunch of roles and workflows and user roles. Maybe would it do the trick, but in a rather heavy, error prone and pretty unmanageable way.&lt;/p&gt;
&lt;p&gt;Any suggestions?&lt;/p&gt;
&lt;p&gt;Some raw ideas I got so far:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Include a &quot;level&quot; parameter in the workflow, which can be checked against the level of the user.&lt;/li&gt;
&lt;li&gt;Set the appropriate hooks to allow delegation of the conflict resolution to a module.&lt;/li&gt;
&lt;li&gt;Define &quot;even&quot; and &quot;odd&quot; roles, so that a user can be Author_ODD and Validator_EVEN, and duplicate the workflow: one for odd levels, one for even ones.&lt;/li&gt;
&lt;li&gt;Extend the workflow matrix to include a &quot;non-author&quot; pseudo-role.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;-- Denis.&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/7990#comments</comments>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Sat, 05 Jan 2008 17:25:57 +0000</pubDate>
 <dc:creator>ablivio@drupal.org</dc:creator>
 <guid isPermaLink="false">7990 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Ideas for Workflow &amp; States with Casetracker</title>
 <link>http://groups.drupal.org/node/7977</link>
 <description>&lt;p&gt;Hello everyone,&lt;/p&gt;
&lt;p&gt;The system we currently use at our office is currently built upon the &lt;a href=&quot;http://drupal.org/project/casetracker&quot;&gt;casetracker&lt;/a&gt; module.  However, the challenge we are encountering is enforcing a &quot;workflow&quot; on those nodes in our system.  It would be great to be able to integrate casetracker with workflow so that changes are detected and that changes to the those fields are acted upon and processed.&lt;/p&gt;
&lt;p&gt;Since &lt;a href=&quot;http://drupal.org/project/casetracker &quot;&gt;casetracker&lt;/a&gt; already has a &quot;status&quot; field to use with cases, it should be be possible to use the &lt;a href=&quot;http://drupal.org/node/202648&quot;&gt;States API&lt;/a&gt; to expose those states to the state machine, right?  And then from there have workflow-ng detect when a comment is posted that changes the state of the case and can execute actions.  The only thing that really doesn&#039;t make sense is where states come into play in workflow-ng... they only seem to play a role in the workflow module.  Having states would also be nice so that we can give users control of what states/statuses they can changes their cases to... i.e. so they can&#039;t change it from &quot;processing&quot; to &quot;new&quot; again.&lt;/p&gt;
&lt;p&gt;Once this capability is done, it would be possible to handle events like case reassignments, status changes, priority changes, etc and move a lot of the action code into UI-configurable actions that do not require code changes to change.&lt;/p&gt;
&lt;p&gt;So, to workflow-ng would the act of posting the comment (with the condition of changing the status field) be the event that would trigger the workflow?  Or would it be better to define a new event that detects just the status change of the case?  I&#039;m a little confused on this part.&lt;/p&gt;
&lt;p&gt;This will really require some changes in the casetracker module, but it would be worth it to allow cases to take advantage of the state engine.  Does this make sense, or should I be going in a different direction?&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/7977#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/62">casetracker</category>
 <category domain="http://groups.drupal.org/taxonomy/term/178">workflow</category>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Fri, 04 Jan 2008 21:42:38 +0000</pubDate>
 <dc:creator>nvahalik@drupal.org</dc:creator>
 <guid isPermaLink="false">7977 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Does workflow-ng support node states?</title>
 <link>http://groups.drupal.org/node/7851</link>
 <description>&lt;p&gt;I&#039;m trying to use Workflow-ng to set up the following scenario:&lt;/p&gt;
&lt;p&gt;A node can have one of three states:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Draft&lt;/li&gt;
&lt;li&gt;Needs Review&lt;/li&gt;
&lt;li&gt;Published&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;There are two types of authenticated users:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Editor&lt;/li&gt;
&lt;li&gt;Publisher&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The Editor role can create nodes and also edit nodes. The Editor can change the state of a node from Draft to Needs Review but cannot set it to Published. The Editor can no longer edit the node once it has been set to the Needs Review state.&lt;/p&gt;
&lt;p&gt;The Publisher role can create, edit and set the node state to published. Once the node is set to Published the Editor role can no longer edit the node. The Publisher can also set the node state back to Needs Review or Draft.&lt;/p&gt;
&lt;p&gt;As far as I can tell the only way to implement this in Workflow-ng is to create a text field for the node type called &#039;state&#039; and add the three states as options. I don&#039;t understand how to limit access to one or other states depending on roles with this method.&lt;/p&gt;
&lt;p&gt;I also can&#039;t figure out how to make a Workflow-ng action change the state from one to another, for instance to create a link that sets the node to the Published state.&lt;/p&gt;
&lt;p&gt;Does anyone have a solution they can help me out with?&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/7851#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/1660">workflow-ng</category>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Thu, 27 Dec 2007 04:50:53 +0000</pubDate>
 <dc:creator>tanc</dc:creator>
 <guid isPermaLink="false">7851 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Workflow-ng integration for ACL</title>
 <link>http://groups.drupal.org/node/7840</link>
 <description>&lt;p&gt;Putting it here, for people to comments and review.&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;
&amp;gt; Hi,&lt;br /&gt;
&amp;gt; Please review this tutorial, I hope it&#039;s better, implementation-wise, then&lt;br /&gt;
&amp;gt; last one :)&lt;br /&gt;
&amp;gt; &lt;a href=&quot;http://drupal.org/node/203377&quot; title=&quot;http://drupal.org/node/203377&quot;&gt;http://drupal.org/node/203377&lt;/a&gt;
&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Yep, that sounds like a cool use case.&lt;/p&gt;
&lt;p&gt;I&#039;d suggest that we write the tutorial, so that the nodes always keep&lt;br /&gt;
visible for everyone. For that we need content access and set it to&lt;br /&gt;
allow anonymous + authenticated users to allow view access.&lt;/p&gt;
&lt;p&gt;-&amp;gt; Probably you have that already, but I can&#039;t find your figure 1?&lt;/p&gt;
&lt;p&gt;Then you are adding all user to the ACL at user login - this is not&lt;br /&gt;
optimal. I think, we should improve that. However, this won&#039;t be&lt;br /&gt;
simple :(&lt;/p&gt;
&lt;p&gt;I think what we need for hat would be&lt;br /&gt;
 * content access workflow-ng integration including priority, so that&lt;br /&gt;
one can set content access per node access control (role based!)&lt;br /&gt;
 * acl node access priority support&lt;/p&gt;
&lt;p&gt;This all node access stuff isn&#039;t that simple :( I should have another&lt;br /&gt;
look at simplifying content access + acl collaboration.&lt;/p&gt;
&lt;p&gt;So this should be the goal, however upgrading the configuration from the&lt;br /&gt;
old one won&#039;t be easy I think.&lt;/p&gt;
&lt;p&gt;regards,&lt;br /&gt;
fago&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/7840#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/102">access</category>
 <category domain="http://groups.drupal.org/taxonomy/term/178">workflow</category>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Tue, 25 Dec 2007 17:47:33 +0000</pubDate>
 <dc:creator>amitaibu</dc:creator>
 <guid isPermaLink="false">7840 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Scheduling more than one change of state?</title>
 <link>http://groups.drupal.org/node/7830</link>
 <description>&lt;p&gt;I don&#039;t seem to be able to schedule more than one change of state in a workflow for a node -- or at least, as there&#039;s no list of thee change I&#039;ve scheduled, I have no way of knowing if adding a second scheduled change works or overrides the first one.&lt;br /&gt;
Is this possible?&lt;/p&gt;
&lt;p&gt;What I&#039;m trying to do is create a news story list on the front page of my site using a node queue. I have three states in my workflow: Pending, Current, and Expired. When in the Current state, the node is in the queue and removed when it goes to Expired.&lt;br /&gt;
I&#039;d like editors to be able to schedule both when the node goes to Current (so you can post news items about things you know will happen, but shouldn&#039;t be shown to the public yet) and also when it expires. So ideally, the whole process of a single node&#039;s lifecycle is set up when it&#039;s first created.&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/7830#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/178">workflow</category>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Sun, 23 Dec 2007 17:55:10 +0000</pubDate>
 <dc:creator>joachim</dc:creator>
 <guid isPermaLink="false">7830 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Problem with Workflow Edit Permissions</title>
 <link>http://groups.drupal.org/node/7323</link>
 <description>&lt;p&gt;I&#039;ve been using Drupal for a few months now, but have only recently tested the workflow module on one of my sites (for submitting creative writing).  I started with workflow-ng, and loved the functionality, but prefer the simplicity of the linear workflow in the &quot;workflow&quot; module.&lt;/p&gt;
&lt;p&gt;I&#039;ve been building a workflow one step at a time (to get used to the module).  Basically, I created a new content type &quot;short story&quot;, and have assigned the workflow to this content type.  I have also created two user groups, being &quot;writer&quot; and &quot;content moderator&quot; (more groups will be added once I get the first steps sorted out).  Basically, the problem is that the workflow edit and view permissions are overruled by the generic group permissions, but also don&#039;t provide groups with a minimum permission.&lt;/p&gt;
&lt;p&gt;I have had no problem creating a new short story as the writer (who is permitted to create, edit own, view revisions, and access the workflow tabs available - generic group permissions).  However, these permissions permit the writer (who will naturally be the author) to edit the content even when the state changes from &quot;draft&quot; to &quot;submitted to content moderator&quot; - when the edit option has been unchecked in the workflow options.&lt;/p&gt;
&lt;p&gt;Additionally, the content moderator is unable to edit or even view the content when the state has been changed to &quot;submitted to content moderator&quot;.  In the workflow, the content moderator is able to view and edit the short story, and the content moderator is permitted to access content, edit content and view revisions in the generic permissions options.  The only way the content moderator is able to view this content is if the generic permission &quot;administer nodes&quot; is enabled, but this far exceeds the permissions that should be given to this group level.&lt;/p&gt;
&lt;p&gt;I haven&#039;t added the actions module yet (although I can&#039;t see how this might influence this problem).&lt;/p&gt;
&lt;p&gt;I&#039;m guessing there is an obvious conflict that I&#039;ve overlooked, but I cannot find it.&lt;/p&gt;
&lt;p&gt;Thanks in advance for your help.&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/7323#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/178">workflow</category>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Tue, 27 Nov 2007 17:00:34 +0000</pubDate>
 <dc:creator>Online247Solutions</dc:creator>
 <guid isPermaLink="false">7323 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Changing user&#039;s role when node is created?</title>
 <link>http://groups.drupal.org/node/6984</link>
 <description>&lt;p&gt;Hello, I am wondering if Workflow-ng can do this:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A user creates a node&lt;/li&gt;
&lt;li&gt;Upon node creation, the user&#039;s role is changed&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Stated differently, &lt;em&gt;can Workflow-ng change the role of a user after they create a node?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;I&#039;m guessing it&#039;s possible, but I&#039;m not sure how.&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Jim&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/6984#comments</comments>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Wed, 07 Nov 2007 18:39:26 +0000</pubDate>
 <dc:creator>JmB</dc:creator>
 <guid isPermaLink="false">6984 at http://groups.drupal.org</guid>
</item>
<item>
 <title>SMS action</title>
 <link>http://groups.drupal.org/node/6818</link>
 <description>&lt;p&gt;Hello everyone. I have been playing around with the SMS framework and email gateway and I think its great! I&#039;d like to throw a bounty out for someone to create an action that send an SMS to a user i.e the author if they have entered their sms information on their account profile.&lt;/p&gt;
&lt;p&gt;I don&#039;t have much, but I&#039;d love to see this module go SMS via actions! : )&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/6818#comments</comments>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Mon, 29 Oct 2007 22:38:18 +0000</pubDate>
 <dc:creator>CorpX</dc:creator>
 <guid isPermaLink="false">6818 at http://groups.drupal.org</guid>
</item>
<item>
 <title>A not-so-ordinary Workflow scenario</title>
 <link>http://groups.drupal.org/node/6693</link>
 <description>&lt;p&gt;The scenario: the project calls for 30 individual reports generated by different writers (some of the writers will generate only one report whilst others will be responsible for more than one). These reports are to be uploaded to the site from where they will be downloaded by a handful of reviewers, each reviewer being responsible for a specific set of reports. Reviews will be uploaded as documents which will in turn be downloaded by the writer and so on and so forth.&lt;/p&gt;
&lt;p&gt;The twist/s: each item uploaded needs to be uploaded as a separate/new node until, finally, one of the drafts submitted is marked as &quot;approved&quot; (as opposed to reviews and revised reports being contained within one node). So, a View which displays the history of on report would consist of a number of draft report nodes and review nodes, all in sequence. Furthermore, each time a report or a review is uploaded, the relevant writer and reviewer need to be alerted via e-mail.&lt;/p&gt;
&lt;p&gt;I have avoided using OG for this as I feel this is overkill and far too messy for something that I&#039;m hoping can be handled by workflow or workflow-ng. I have, however, been working with both modules but have not been able to find a solution to the problem presented by the fact that action e-mails need to be sent only to the writer and reviewer in charge of a particular report. For example, if a reviewer uploads a review for report # 26, how will the system know that the action e-mail needs to be sent to the writer of the original report #26?&lt;/p&gt;
&lt;p&gt;Any pointers would be greatly appreciated. Many thanks in advance.&lt;/p&gt;
&lt;p&gt;p.s. the reasoning behind having all submissions as separate nodes are that I need to show a very clear history/overview of the entire review process. This needs to be EXTREMELY simple as most of the people relying on this system have very little computer knowledge beyond using Word and sending e-mail.&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/6693#comments</comments>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Mon, 22 Oct 2007 22:53:17 +0000</pubDate>
 <dc:creator>stormer</dc:creator>
 <guid isPermaLink="false">6693 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Parallel Paths in Workflow</title>
 <link>http://groups.drupal.org/node/6663</link>
 <description>&lt;p&gt;I&#039;m looking for some feedback.  I&#039;m using the workflow module and generally find it very good.  Very easy to setup and can be extended to do quite a bit.  The only thing it seems to be lacking that I keep finding myself needing and having to work around, is parallel paths.  Does any one have any ideas on how to accomplish this?  I am a fairly adept programmer and may be able to devote a little bit of time to this, but looking for some input to see if anyone else out there has this need or has any ideas on how to accomplish this?&lt;/p&gt;
&lt;p&gt;My initial thought is that the setup of workflow_ng may be more suited for this use case, however I currently find their user interface much less user friendly.  Any ideas?&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/6663#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/3279">parallel tasks</category>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Fri, 19 Oct 2007 16:22:33 +0000</pubDate>
 <dc:creator>chewblocka</dc:creator>
 <guid isPermaLink="false">6663 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Actions for File Uploads</title>
 <link>http://groups.drupal.org/node/6451</link>
 <description>&lt;p&gt;I&#039;m looking to create a site where an administrator can post a file with a list of questions (Actually a file with protein/ligand smiles strings for you chemistry geeks out there). Then I&#039;m looking to let a user post a file of answers (Again for the chemistry geeks: pose prediction, affinity estimation, etc). When they post their answers, it&#039;ll give them access to yet another questions file with which they can post their answers file.&lt;/p&gt;
&lt;p&gt;Once they post an answers file, the questions file should be marked as answered and there may be one or more question files unlocked as a result.&lt;/p&gt;
&lt;p&gt;Is it possible to do this with workflow-ng? It seems like it would be a nice application of it. I just want to make sure I&#039;m not misguided here in trying to use this module. Thanks for your time. Any input or ideas on how to implement this are much appreciated.&lt;/p&gt;
&lt;p&gt;-JB&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/6451#comments</comments>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Fri, 05 Oct 2007 17:37:32 +0000</pubDate>
 <dc:creator>fintler</dc:creator>
 <guid isPermaLink="false">6451 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Question about different workflows per user</title>
 <link>http://groups.drupal.org/node/6410</link>
 <description>&lt;p&gt;I have two states in my workflow: Submitted and Published.&lt;/p&gt;
&lt;p&gt;I want to restrict anonymous user to submitting to the Submitted state.  (done.)&lt;/p&gt;
&lt;p&gt;I want logged-in users to automatically post to the Published state.  (almost there)&lt;/p&gt;
&lt;p&gt;In the creation section of the workflow grid, I&#039;ve set:&lt;br /&gt;
 - Submitted: Author, anonymous user&lt;br /&gt;
 - Published: authenticated user, Content Admin, Site Admin&lt;/p&gt;
&lt;p&gt;There is no overlap between user roles in that workflow setup.  However, when an authenticated user creates some new content, he is given the choice of Submitted or Published.&lt;/p&gt;
&lt;p&gt;I don&#039;t even have to get rid of the &quot;Submitted&quot; option, if I can set the &quot;Published&quot; option to be selected by default for authenticated users.&lt;/p&gt;
&lt;p&gt;any tips?&lt;/p&gt;
&lt;p&gt;thanks in advance!
&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/6410#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/2893">multiple workflows</category>
 <category domain="http://groups.drupal.org/taxonomy/term/178">workflow</category>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Tue, 02 Oct 2007 01:47:39 +0000</pubDate>
 <dc:creator>nadavoid</dc:creator>
 <guid isPermaLink="false">6410 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Automatically removing blog entry from front page when a newer item is created</title>
 <link>http://groups.drupal.org/node/6403</link>
 <description>&lt;p&gt;Hello, we&#039;re working on a site at &lt;a href=&quot;http://www.mngreenroofs.org/&quot; title=&quot;http://www.mngreenroofs.org/&quot;&gt;http://www.mngreenroofs.org/&lt;/a&gt; and they are looking for a certain feature for their blog:&lt;/p&gt;
&lt;p&gt;They want something that automatically publishes the latest blog entry to their front page, &lt;em&gt;and&lt;/em&gt; unpublishes the previous latest entry from the front page (but it still stays published in the blogs area).&lt;/p&gt;
&lt;p&gt;I&#039;m guessing the basic answer would be something like:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Preliminary setup: blog content that&#039;s created is by default promoted to the front page in Content Types&lt;/li&gt;
&lt;li&gt;When a new blog entry is submitted, any blog content with the status &quot;Published to front page&quot; is triggered to remove the front page promotion.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If this is the way to go about it, I&#039;m not sure how to implement.  I&#039;m hoping there is a way with Workflow-ng to do this!  Thanks for your help,&lt;/p&gt;
&lt;p&gt;Jim&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/6403#comments</comments>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Mon, 01 Oct 2007 22:17:34 +0000</pubDate>
 <dc:creator>JmB</dc:creator>
 <guid isPermaLink="false">6403 at http://groups.drupal.org</guid>
</item>
<item>
 <title>unpublish content types automatically</title>
 <link>http://groups.drupal.org/node/6382</link>
 <description>&lt;p&gt;I have content types provided, that automatically eight weeks after publishing should be deleted or unpublished. Is that possible with the workflow ng module? Or have you any other solution for me?&lt;/p&gt;
&lt;p&gt;kind regards&lt;br /&gt;
drew29&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/6382#comments</comments>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Sun, 30 Sep 2007 10:34:52 +0000</pubDate>
 <dc:creator>drew29@drupal.org</dc:creator>
 <guid isPermaLink="false">6382 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Are you storing your Drupal sites or configs in a version control system? If so, which?</title>
 <link>http://groups.drupal.org/node/6172</link>
 <description>&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/6172#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/3071">config</category>
 <category domain="http://groups.drupal.org/taxonomy/term/2853">configuration</category>
 <category domain="http://groups.drupal.org/taxonomy/term/218">cvs</category>
 <category domain="http://groups.drupal.org/taxonomy/term/1781">deployment</category>
 <category domain="http://groups.drupal.org/taxonomy/term/166">files</category>
 <category domain="http://groups.drupal.org/taxonomy/term/12">maintenance</category>
 <category domain="http://groups.drupal.org/taxonomy/term/2221">revision control</category>
 <category domain="http://groups.drupal.org/taxonomy/term/3070">sites</category>
 <category domain="http://groups.drupal.org/taxonomy/term/3069">source safe</category>
 <category domain="http://groups.drupal.org/taxonomy/term/2331">subversion</category>
 <category domain="http://groups.drupal.org/taxonomy/term/219">svn</category>
 <category domain="http://groups.drupal.org/taxonomy/term/3072">version control</category>
 <category domain="http://groups.drupal.org/taxonomy/term/178">workflow</category>
 <group domain="http://groups.drupal.org/issue-tracking-and-software-releases">Issue tracking and software releases</group>
 <group domain="http://groups.drupal.org/testing-qa">Testing and Quality Assurance</group>
 <group domain="http://groups.drupal.org/benchmarking-drupal">Benchmarking Drupal</group>
 <group domain="http://groups.drupal.org/distributions">Distribution profiles</group>
 <group domain="http://groups.drupal.org/drupal-dojo">Drupal Dojo</group>
 <group domain="http://groups.drupal.org/high-performance">High performance</group>
 <group domain="http://groups.drupal.org/language-learning-communities">Language Learning Communities</group>
 <group domain="http://groups.drupal.org/quality-assurance">Quality Assurance</group>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Mon, 17 Sep 2007 21:12:02 +0000</pubDate>
 <dc:creator>Chris Charlton</dc:creator>
 <guid isPermaLink="false">6172 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Workflow-ng 1.0 released!</title>
 <link>http://groups.drupal.org/node/6161</link>
 <description>&lt;p&gt;Finally the first stable release of workflow-ng is out!&lt;/p&gt;
&lt;p&gt;The module is already stable for a long time and all important features are implemented, so I decided it&#039;s time to release. So I&#039;m happy to have a stable 1.0 release out of the door close before the drupalcon in barcelona. If you are going to barcelona, don&#039;t miss the &lt;a href=&quot;http://barcelona2007.drupalcon.org/node/456&quot;&gt;session about workflow-ng&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Links:&lt;br /&gt;
&lt;a href=&quot;http://drupal.org/project/workflow_ng&quot;&gt;project page&lt;/a&gt;&lt;br /&gt;
&lt;a href=&quot;http://drupal.org/node/156282&quot;&gt;documentation&lt;/a&gt;&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/6161#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/178">workflow</category>
 <group domain="http://groups.drupal.org/actions">Actions</group>
 <group domain="http://groups.drupal.org/austria">Austria</group>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Mon, 17 Sep 2007 06:46:07 +0000</pubDate>
 <dc:creator>fago@drupal.org</dc:creator>
 <guid isPermaLink="false">6161 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Changing states through links. </title>
 <link>http://groups.drupal.org/node/6121</link>
 <description>&lt;p&gt;I am attempting to set up a node type that has 4 workflow states associated to it.   What I would like to do is include links or linked images images and via the link, can be clicked on to change that node to that state.  The idea is to keep users from having to click workflow and then change the state.  These states will not change, so I don&#039;t mind hardcoding links into the node template and using node id as a dynamic variable in the url.  Is this possible?  I think that this would be a great usability enhancement to Workflows aswell.    thanks in advance.    Jimmy&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/6121#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/177">actions</category>
 <category domain="http://groups.drupal.org/taxonomy/term/3051">transitions</category>
 <category domain="http://groups.drupal.org/taxonomy/term/178">workflow</category>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Wed, 12 Sep 2007 19:51:37 +0000</pubDate>
 <dc:creator>CorpX</dc:creator>
 <guid isPermaLink="false">6121 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Multiple workflows for same content type - status and implementation</title>
 <link>http://groups.drupal.org/node/5770</link>
 <description>&lt;p&gt;Hi,&lt;br /&gt;
I&#039;m looking for a way to add multiple workflows on the same node type. Its for some CRM system (among the rest) that has a few logical workflows within, all on &lt;em&gt;users&lt;/em&gt; of the system. We contemplated on using node profile as the node type with multiple workflows defined on it, but, that&#039;s not possible as in the current workflow module implementation each content type can be associated with one workflow . Any suggestions?&lt;/p&gt;
&lt;p&gt;I know this issue has been brought up in the past. Seen it &lt;a href=&quot;http://drupal.org/node/80703&quot;&gt;here&lt;/a&gt; and also as future plans for workflow (workflow-ng actually). I guess that this is not functional yet and I wanted to ask here what&#039;s the best suggestion to bypass this limitation. What I thought of is the following, in a nutshell (also because I&#039;m still learning Drupal):&lt;br /&gt;
When a user account is being created, aside from its node profile being created (using &quot;node profile&quot; module) a set of several child-nodes will be opened for the parent &quot;node profile&quot; node, using &quot;node family&quot; module. We&#039;ll have a new node type for each workflow, and each will be filled with copies of the needed user data. Then, each workflow will actually work on its content type and programatically, i&#039;ll need to sync between all nodes if the user data changes (the other changes are the user states in the various workflows and that&#039;s ok, of course).&lt;br /&gt;
I&#039;d appreciate comments... .&lt;br /&gt;
Thanks,&lt;br /&gt;
Boaz.&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/5770#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/2893">multiple workflows</category>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Wed, 22 Aug 2007 19:31:36 +0000</pubDate>
 <dc:creator>boaz_r</dc:creator>
 <guid isPermaLink="false">5770 at http://groups.drupal.org</guid>
</item>
<item>
 <title>incorrect logic from state to the same state</title>
 <link>http://groups.drupal.org/node/5710</link>
 <description>&lt;p&gt;I&#039;m following the &quot;classic&quot; example here with 3 states:&lt;br /&gt;
- Draft&lt;br /&gt;
- Review&lt;br /&gt;
- Publish&lt;/p&gt;
&lt;p&gt;Only the editor/moderator can publish a node. So, user only has access to Draft and Review states.&lt;br /&gt;
When the content is approved and published by the moderator, user goes back and edits the content again. The transition from Published to Draft as well as Published to Review are available, but user now can see three workflow states and the &quot;Publish&quot; is currently active.  Now, if user manually switched states from Publish to Draft or Review - the node will get unpublished by the action module, but if user make his/her changes to the content without changing the current state (Publish) - the content gets re-published without moderation. So, there is a problem... the &quot;From/to&quot; workflow is set the way that user can not publish content, so the &quot;Publish&quot; state should never be visible to the user in any case. If user goes back to edit already approved/published content - it should give him only those states that are available to him by the workflow setup... in my case Draft and Review.&lt;/p&gt;
&lt;p&gt;Any ideas on how this problem can be avoided?&lt;/p&gt;
&lt;p&gt;Thank you!&lt;/p&gt;
&lt;p&gt;P.S. I found some info here &lt;a href=&quot;http://drupal.org/node/86451&quot; title=&quot;http://drupal.org/node/86451&quot;&gt;http://drupal.org/node/86451&lt;/a&gt; - I&#039;ll try the patches.&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/5710#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/178">workflow</category>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Sun, 19 Aug 2007 21:52:01 +0000</pubDate>
 <dc:creator>gemini@drupal.org</dc:creator>
 <guid isPermaLink="false">5710 at http://groups.drupal.org</guid>
</item>
<item>
 <title>New user to drupal and workflow (very confused)</title>
 <link>http://groups.drupal.org/node/5572</link>
 <description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;I am a recent entrant in to the world of Drupal and have so far been very impressed indeed.&lt;br /&gt;
I am having problems understanding how to implement workflow in version 5.1x of drupal.&lt;br /&gt;
The workflow I want to do is:&lt;/p&gt;
&lt;p&gt;1.author creates content and sends for approval&lt;br /&gt;
2. notiification email sent to admin&lt;br /&gt;
3. admin publishes content&lt;br /&gt;
4. content visible live on site&lt;/p&gt;
&lt;p&gt;I have read various postings and have watched the lullabot workflow video but am coming up against a very big brick wall at the minute in terms of me grasping how this is done.&lt;/p&gt;
&lt;p&gt;Any pointers would be greatly appreciated.&lt;/p&gt;
&lt;p&gt;Many thanks&lt;/p&gt;
&lt;p&gt;Adam&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/5572#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/178">workflow</category>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Mon, 13 Aug 2007 15:37:04 +0000</pubDate>
 <dc:creator>amccune</dc:creator>
 <guid isPermaLink="false">5572 at http://groups.drupal.org</guid>
</item>
<item>
 <title>New user to drupal and workflow (very confused)</title>
 <link>http://groups.drupal.org/node/5571</link>
 <description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;I am a recent entrant in to the world of Drupal and have so far been very impressed indeed.&lt;br /&gt;
I am having problems understanding how to implement workflow in version 5.1x of drupal.&lt;br /&gt;
The workflow I want to do is:&lt;/p&gt;
&lt;p&gt;1.author creates content and sends for approval&lt;br /&gt;
2. notiification email sent to admin&lt;br /&gt;
3. admin publishes content&lt;br /&gt;
4. content visible live on site&lt;/p&gt;
&lt;p&gt;I have read various postings and have watched the lullabot workflow video but am coming up against a very big brick wall at the minute in terms of me grasping how this is done.&lt;/p&gt;
&lt;p&gt;Any pointers would be greatly appreciated.&lt;/p&gt;
&lt;p&gt;Many thanks&lt;/p&gt;
&lt;p&gt;Adam&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/5571#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/178">workflow</category>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Mon, 13 Aug 2007 15:36:36 +0000</pubDate>
 <dc:creator>amccune</dc:creator>
 <guid isPermaLink="false">5571 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Create forum topic after content creation</title>
 <link>http://groups.drupal.org/node/5424</link>
 <description>&lt;p&gt;I&#039;m actually creating a special content type with the cck module. Th problem thereby is that I want to have the discussion to the content not in form of comments but in form of a forum topic. This should be generated for every content of this type by default.&lt;/p&gt;
&lt;p&gt;I thought an action maybe in combination with a workflow could help solving this problem fast. I&#039;m not good at php so I&#039;m asking here if this is possible and on how to create such an action.&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/5424#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/2735">action workflow</category>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Thu, 02 Aug 2007 23:46:12 +0000</pubDate>
 <dc:creator>bloomaniac@drupal.org</dc:creator>
 <guid isPermaLink="false">5424 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Action triggered upon submitting</title>
 <link>http://groups.drupal.org/node/5310</link>
 <description>&lt;p&gt;We are attempting to set up a workflow action for people to apply for a directory listing on a website.  Editors should be notified that a submission has been received, so they will be able to review it.  The eventual process will hopefully be something like this:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;An anonymous user fills out the CCK fields set up for Directory Listing content.&lt;/li&gt;
&lt;li&gt;Upon clicking &quot;submit&quot;, an e-mail is sent out to site editor(s).&lt;/li&gt;
&lt;li&gt;The content goes into an unpublished &quot;For Review&quot; state.&lt;/li&gt;
&lt;li&gt;Editors review it and go from there....&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;I watched the &quot;Actions and Workflow&quot; videocast at Lullabot and set it up as far as I could. The first problem I&#039;m discovering, though, is that it appears that a content node must already be created &lt;em&gt;before&lt;/em&gt; an action can take place.  Is there any way the action can be triggered &lt;strong&gt;when&lt;/strong&gt; the content is submitted??  Any other pointers or tips on setting this up will also be appreciated :)&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Jim&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/5310#comments</comments>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Wed, 25 Jul 2007 18:01:59 +0000</pubDate>
 <dc:creator>JmB</dc:creator>
 <guid isPermaLink="false">5310 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Workflow Graph released</title>
 <link>http://groups.drupal.org/node/5254</link>
 <description>&lt;p&gt;This little module produces graph diagrams out of workflows, useful for documentation purposes.&lt;/p&gt;
&lt;p&gt;It currently generates two distinct kinds of graphs:&lt;br /&gt;
* One for the workflow definition, showing all workflow states, the&lt;br /&gt;
transitions linking them, and the roles allowed to perform those&lt;br /&gt;
transitions.&lt;br /&gt;
* One for a workflow &lt;em&gt;instance history&lt;/em&gt;, i.e. the path that a workflow&lt;br /&gt;
took for a specific node. Here, the graph shows all state transitions&lt;br /&gt;
that occurred on the node, including the timestamp and the users who&lt;br /&gt;
performed those transitions.&lt;/p&gt;
&lt;p&gt;It&#039;s pretty raw for the time being, especially when it comes to controlling the generated graph. Enthusiasts are welcome!&lt;/p&gt;
&lt;p&gt;Check it out: &lt;a href=&quot;http://drupal.org/project/workflow_graph&quot; title=&quot;http://drupal.org/project/workflow_graph&quot;&gt;http://drupal.org/project/workflow_graph&lt;/a&gt;
&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/5254#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/433">graphviz</category>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Sat, 21 Jul 2007 08:54:11 +0000</pubDate>
 <dc:creator>kratib@drupal.org</dc:creator>
 <guid isPermaLink="false">5254 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Change node from private to publici</title>
 <link>http://groups.drupal.org/node/5159</link>
 <description>&lt;p&gt;I&#039;d like to be able to submit a post, have members vote on it, and then if the score is high enough, it gets published publicly. Is that possible? Perhaps if I posted a private group post, it could be changed to public with og_audience?. Should I be looking at the action module instead?&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/5159#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/2587">change</category>
 <category domain="http://groups.drupal.org/taxonomy/term/199">node</category>
 <category domain="http://groups.drupal.org/taxonomy/term/815">private</category>
 <category domain="http://groups.drupal.org/taxonomy/term/2588">public</category>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Tue, 17 Jul 2007 01:20:14 +0000</pubDate>
 <dc:creator>Meg Lee Chin</dc:creator>
 <guid isPermaLink="false">5159 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Workflow-ng 5.x-1.0 beta1 released!</title>
 <link>http://groups.drupal.org/node/4969</link>
 <description>&lt;p&gt;I&#039;m happy to announce the 1.0 beta1 release of workflow-ng.&lt;/p&gt;
&lt;p&gt;Workflow-ng allows one to customize drupal&#039;s built in workflows in a very flexible way.&lt;br /&gt;
In short, it&#039;s a rule-based event driven action evaluation system. Read the &lt;a href=&quot;http://drupal.org/node/156288&quot;&gt;introduction&lt;/a&gt; to see how it works.&lt;/p&gt;
&lt;p&gt;It is useful for&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;sending customized mails notifying your users about important changes&lt;/li&gt;
&lt;li&gt;building flexible content publishing workflows&lt;/li&gt;
&lt;li&gt;creating custom redirections&lt;/li&gt;
&lt;li&gt;and a lot more....&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
It builds on the powerful &lt;a href=&quot;http://more.zites.net/workflow-ng-api-ready&quot;&gt;workflow-ng API&lt;/a&gt;, which allows contributed modules not only to expose configuration defaults, but also to add additional events, conditions and actions.&lt;br /&gt;
Users can share their configurations by using the built-in import/export tool. This enables users to easily &lt;a href=&quot;http://drupal.org/node/156294&quot;&gt;share&lt;/a&gt; their configurations.&lt;br /&gt;
I&#039;ve already wrote some &lt;a href=&quot;http://drupal.org/node/156282&quot;&gt;documentation&lt;/a&gt; including two tutorials, but the developer documentation is still TODO. It&#039;ll be completed during the next days...&lt;/p&gt;
&lt;p&gt;Watch out for updates or other related news on my blog: &lt;a href=&quot;http://more.zites.net/workflow-ng&quot; title=&quot;http://more.zites.net/workflow-ng&quot;&gt;http://more.zites.net/workflow-ng&lt;/a&gt;&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/4969#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/178">workflow</category>
 <group domain="http://groups.drupal.org/actions">Actions</group>
 <group domain="http://groups.drupal.org/austria">Austria</group>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Tue, 03 Jul 2007 19:12:04 +0000</pubDate>
 <dc:creator>fago@drupal.org</dc:creator>
 <guid isPermaLink="false">4969 at http://groups.drupal.org</guid>
</item>
<item>
 <title>How to customise Drupal Site</title>
 <link>http://groups.drupal.org/node/4307</link>
 <description>&lt;p&gt;Hi&lt;br /&gt;
I am new to Drupal and have to customise the site&lt;/p&gt;
&lt;p&gt;Need to know:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;when a user replies or post new node, how is his/her picture is reflected in the replies/comments etc....&lt;br /&gt;
    I have to do this customisation.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Please do reply back, How do i customise this?&lt;/p&gt;
&lt;p&gt;Regds&lt;br /&gt;
Vinod&lt;/p&gt;
&lt;p&gt;Vinod,&lt;br /&gt;
try enabling pictures in user settings (admin/user/settings) then enable pictures in your theme (admin/build/themes/settings/bluemarine).&lt;br /&gt;
I hope this helps&lt;br /&gt;
William&lt;br /&gt;
&lt;a href=&quot;/user/7640&quot;&gt;wpoehner&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Hi Vinod,&lt;/p&gt;
&lt;p&gt;As William said enable pictures in user settings then enable pictures in your theme (make sure the theme you choose to use supports display if avtars in posts and comments). I think bluemarine does it. Also install image module.&lt;/p&gt;
&lt;p&gt;Vikram&lt;br /&gt;
De-centralizing the central issues&lt;br /&gt;
&lt;a href=&quot;http://hpk.co.in&quot;&gt;hpk.co.in&lt;/a&gt;&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <group domain="http://groups.drupal.org/bangalore">Bangalore</group>
 <group domain="http://groups.drupal.org/hyderabad">Hyderabad</group>
 <group domain="http://groups.drupal.org/india">India</group>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Thu, 31 May 2007 11:23:41 +0000</pubDate>
 <dc:creator>vinod</dc:creator>
 <guid isPermaLink="false">4307 at http://groups.drupal.org</guid>
</item>
<item>
 <title>Workflow-ng API ready...</title>
 <link>http://groups.drupal.org/node/4298</link>
 <description>&lt;p&gt;After some hard work, the &lt;a href=&quot;http://more.zites.net/node/3030&quot;&gt;workflow-ng&lt;/a&gt; API is ready.&lt;/p&gt;
&lt;p&gt;It features&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;actions, which may be configurable&lt;/li&gt;
&lt;li&gt;conditions, which may also be configurable&lt;/li&gt;
&lt;li&gt;support for multiple arguments, for actions as well as for conditions&lt;/li&gt;
&lt;li&gt;condition evaluation with logical operations like OR, AND and NOR&lt;/li&gt;
&lt;li&gt;events, for which conditions and actions can be configured. They may be contributed by modules.&lt;/li&gt;
&lt;li&gt;dynamic loading of needed arguments&lt;/li&gt;
&lt;li&gt;ordered conditions and actions - they are evaluated like they are ordered&lt;/li&gt;
&lt;li&gt;form API style configuration and processing of conditions and actions&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;So workflow-ng works event based. (And no, I&#039;m not talking of calendars ;)&lt;br /&gt;
E.g. workflow-ng defines some basic events for drupal core, like &#039;node update, &#039;node insert&#039;, &#039;user update&#039; and so on. So this are the events you can react on by defining conditions and actions for them.&lt;br /&gt;
What makes workflow-ng powerful is, is it&#039;s flexible handling of arguments. Each of these events has to define a list of available arguments. Then any conditions and actions, that can work with these arguments, can be configured for this event. So an action can be used in any situation, where the suitable arguments are available. There is no need for the action, to be coded aware of every event.. :)&lt;/p&gt;
&lt;p&gt;As modules may define further events, this enables module authors, to easily allow site administrators to customize the behavior by just defining some further events.&lt;/p&gt;
&lt;p&gt;Read more at &lt;a href=&quot;http://more.zites.net/workflow-ng-api-ready&quot; title=&quot;http://more.zites.net/workflow-ng-api-ready&quot;&gt;http://more.zites.net/workflow-ng-api-ready&lt;/a&gt;
&lt;/p&gt;
&lt;div class=&quot;og_rss_groups&quot;&gt;&lt;a href=&quot;/workflow&quot;&gt;Workflow&lt;/a&gt;&lt;/div&gt;</description>
 <comments>http://groups.drupal.org/node/4298#comments</comments>
 <category domain="http://groups.drupal.org/taxonomy/term/178">workflow</category>
 <group domain="http://groups.drupal.org/actions">Actions</group>
 <group domain="http://groups.drupal.org/austria">Austria</group>
 <group domain="http://groups.drupal.org/workflow">Workflow</group>
 <pubDate>Wed, 30 May 2007 20:40:52 +0000</pubDate>
 <dc:creator>fago@drupal.org</dc:creator>
 <guid isPermaLink="false">4298 at http://groups.drupal.org</guid>
</item>
</channel>
</rss>
