workflow

Hi

I am a recent entrant in to the world of Drupal and have so far been very impressed indeed.
I am having problems understanding how to implement workflow in version 5.1x of drupal.
The workflow I want to do is:

1.author creates content and sends for approval
2. notiification email sent to admin
3. admin publishes content
4. content visible live on site

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.

Any pointers would be greatly appreciated.

Hi

I am a recent entrant in to the world of Drupal and have so far been very impressed indeed.
I am having problems understanding how to implement workflow in version 5.1x of drupal.
The workflow I want to do is:

1.author creates content and sends for approval
2. notiification email sent to admin
3. admin publishes content
4. content visible live on site

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.

Any pointers would be greatly appreciated.

I'm happy to announce the 1.0 beta1 release of workflow-ng.

Workflow-ng allows one to customize drupal's built in workflows in a very flexible way.
In short, it's a rule-based event driven action evaluation system. Read the introduction to see how it works.

It is useful for

• sending customized mails notifying your users about important changes
• building flexible content publishing workflows
• creating custom redirections
• and a lot more....

After some hard work, the workflow-ng API is ready.

It features

• actions, which may be configurable
• conditions, which may also be configurable
• support for multiple arguments, for actions as well as for conditions
• condition evaluation with logical operations like OR, AND and NOR
• events, for which conditions and actions can be configured. They may be contributed by modules.
• dynamic loading of needed arguments
• ordered conditions and actions - they are evaluated like they are ordered
• form API style configuration and processing of conditions and actions

So workflow-ng works event based. (And no, I'm not talking of calendars ;)
E.g. workflow-ng defines some basic events for drupal core, like 'node update, 'node insert', 'user update' and so on. So this are the events you can react on by defining conditions and actions for them.
What makes workflow-ng powerful is, is it'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.. :)

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.

Read more at http://more.zites.net/workflow-ng-api-ready

Hi

Could anybody, please, tell if workflow module can be used for doing/checking things periodically and making a state transition basing on the check results?

I really want to make use of the workflow module just released for 5.x but must have the capability of triggering a state change based on some simple field matching criteria.

On Cron Run:
* foreach (condition) { if (condition.true) { execute state change; break; } }

I noticed a small _cron() method that is already doing state transitions based on pure schedule. I guess my main question here is what is the best way to approach this? Is someone working on something similar that I could help out with? Should I just code it up and submit it to the group for review?

One feature of Wikipedia that I find attractive is the ability to restrict edits on a certain page to editors/administrators, particularly in the case of vandalism or high traffic. I was looking around at the best way to implement this feature in drupal, and found that a combination of workflows, na_arbitrator (integrated in Drupal 5 core), and workflows_access (not ready for Drupal 5 yet but seems to be on the short-term roadmap) will offer that functionality. Just posting for others' info just in case they were looking for this feature as well.

Hello,

I've created this new Trading group. My goals are similar to those of the Stock group, so I'm posting this to you guys as well.

I'm a trader/programmer who has set up a private site meant to eventually manage a little fund for my friends and family. My current setup allows me to input and browse trades I make, so that I'll later be able to track my progress. Here's what I'm currently using (I have done no custom programming yet):

taxonomy: I currently have "market" and "system" categories. These are heirarchical, so I could have a market called "GBPUSD" with parent "Forex". A system could be a particular setup or signal within a larger system, for example "spinning top" within "chart patterns". I'll be using these taxonomies to browse my trades and judge which trading systems work with which markets, etc. I want to eventually be able to do all kinds of statistical analysis based on these categories.

I'm considering to start rewriting the workflow module.
You may ask: But why?

• to make programmatically supplying a workflow easier
• to make it more modular and so more extensible
• to allow multiple workflows per content type
• to make it more efficent and to have it cleaned up

So how do I imagine the new improved workflow module?

I am thinking of dividing it into three modules, that can be bundled in one archive/drupal project.

• workflow module (the engine)
• workflow UI
• worklfow permissions

The workflow module would be an API only module. It allows other modules to define workflows and to execute their transitions. It doesn't provide any access checks, as this is needed rarely for programmatically supplied workflows. So this modules task is to make programmatically supplied workflows possible.

One of the major VotingAPI improvements that's been in the pipeline for a while is an overhaul of integration with the Actions module. At present, the voting_actions module is used to set up specific vote results that will trigger things like promoting a node to the front page, or unpublishing it. There are some problems with the approach, though. First, there was no way for module authors to provide 'built-in' voting actions. Everything had to be set up by users. Second, there was no way to make decisions about action execution based on the content rather than the vote. In other words, polls need 10 votes to be promoted, but stories need 15. Third, there's really no reason that the functionality should be in a separate module -- actions integration should be exposed as an API for module writers, and should be tweakable by users who want more customization. It's a bit like the Views module philosophy: modules can expose default bviews, but users can make their own or override the defaults. To that end, the new VotingAPI actions system has been re-written. All the core code IS present, though the end-user UI for creating and overriding actions is still being written.