The Activation workflow works around the separation of the workflow
item and
its page. Specific fields like path, start date, and end date are
explicitly
copied into the workflow from the nodes meta data, so that the
engine has
access to those values, and doesn't reference directly the ones
stored in the
page. Under that model, you'd update the page to publish, and
expect that
the workflow item was updated.
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.
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. If we store
the workitems as discussed here this gets even much easier.
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
