Am Montag, 11. September 2006 20:38 schrieb Philipp Bracher:
> Depends on the viewpoint. You can say that if you start a workflow
> you start it with the current page state. This is why we create a
> version of the page at this point. This means if you activate during
> the flow you will activate this state and not the current version the
> users are editing in the admin central.
My mistake, I didn't actually notice that it is the page *version* that is
published.
>
> The new publishing time is then meant to influence the next
> activation. Else you can delay an activation by accident.
>
> However the system is flexible enough so that you can change this
> behavior. You can take the delivered scheduled activation as an
> example and change the way the data is read completely.
How do you see the opportunity for changing how data is read? I thought the
workflow process only has access to the data actually copied into the
workflow item? I could imagine using command participants in my workflow to
automate this process, and make certain fields available later. Is that what
you're hinting at?
> If we store
> the workitems as discussed here this gets even much easier.
If the workitems are stored/unarchived as discussed here, will this mean that
content I add through the standard magnolia api will be available from the
process definition as fields? (something like ${f:address.shipto.street} to
dig into the content node assigned to the address field of the work item?)
For example I open a dialog on the Node at:
/flow/1.x/63/1157640296863/participant/0.0.1
in the Store workspace. Through my dialog, I add three attributes to this
node (invitee, location, date). Will I be able to access this from my
workflow with something like
<if test="${field:location} == berlin">
<command-call-wowereit/>
</if>
Will this execute the 'call-wowerreit' command based on the info I stuffed in
via a normal dialog?
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
