Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
ah ok.. so this is no question of workflow-ng integration, but of storing the information. You probably need a module for that, or you might make use of cck fields to store that information, but then you would also need an action to set these...
My idea was to let CCL store this info. I think CCL can already store timestamp (as it is using for the schedule).
Now it will need also a to hold the user that invoked.
hm, this let me thought a lot about scheduling works in workflow-ng. I think there is need for a much more general scheduling support, which I plan to introduce together with a kind of procedures. Then this would be possible :) However, I'm not sure yet whether I implement this for 6.x only or 5.x and 6.x. But for now, it's postponed until the todo list gets smaller...
Comments
Comment #1
fagoCouldn't you use the global's users name? We could also add the current time as global token..
Comment #2
amitaibuCan't use the global user, as it might have been locked by another user.
Comment #3
fagoah ok.. so this is no question of workflow-ng integration, but of storing the information. You probably need a module for that, or you might make use of cck fields to store that information, but then you would also need an action to set these...
Comment #4
amitaibuMy idea was to let CCL store this info. I think CCL can already store timestamp (as it is using for the schedule).
Now it will need also a to hold the user that invoked.
Comment #5
fagohm, this let me thought a lot about scheduling works in workflow-ng. I think there is need for a much more general scheduling support, which I plan to introduce together with a kind of procedures. Then this would be possible :) However, I'm not sure yet whether I implement this for 6.x only or 5.x and 6.x. But for now, it's postponed until the todo list gets smaller...