Hi Fago,

I didn't noticed your effort to add node creation to workflow_ng. That's why I created node factory module. It's in dev version still, but i was about to build 'edit_node' next week. And a workflow_ng action #213866: implement workflow_ng action to create node serie . I have some cck integration done #213869: cckfield fieldlist not populated but need more pointers to solve ie imagefield.

What are your thought about using this module instead? I think this module has value of itself (people used it ie batch importing images #217081: image fields) but it would be a waste of time and resource to build the node create/edit functionality twice.

Let me know your thought :-)

Regards,
Clemens

Comments

fago’s picture

your module is really interesting :)

I've just enhanced the existing workflow-ng action a bit. Now, it uses workflow-ng to save the newly added node: this has one major benefit: We can use other actions to alter the node before it gets saved! -> check out the latest 2.x dev snapshot.

E.g. use "(Un)Publish content" with it.

I think it would be awesome if you could build actions for your API functions, so that they are even easier to use.
I won't add more node creation features for workflow-ng, as this isn't my main interest. But as nice side effect the solution will grow with every action that alters node data :)

clemens.tolboom’s picture

I'll try to create actions.

I'm not sure how to implement token though. I can imagine a scenario like
- action: create node as an action with a dropdown of available node types
- action: set title to "[user:name] [date:now]"

And how to maintain context between these two actions.

Any suggestions?

fago’s picture

workflow-ng takes care of that. just write the actions for a $node, then one can configure them for every node, also for the newly created one.

clemens.tolboom’s picture

Status: Active » Closed (won't fix)