This, or some version of it, may have been asked in the past, but I didn't
find a thread addressing this exact situation.
We're using a PLP to edit content items (CI's) because the CI's require a
multi-step process. I need to control the PLP -- or at least would like to
do notifications about it -- using a workflow.
For example, suppose an Editor finishes editing the CI (using the PLP). I
now want a workflow to send notification to the Publisher that she needs to
review and okay/not okay publication.
The Publisher, when she receives notification that the CI is ready to be
reviewed will kick off her task which will invoke the edit CI PLP (because
she has access to edit it too). When the Publisher runs the PLP, it will
display an additional button, not available to editors, that allows the
Publisher to publish the CI.
The Publisher may 'not okay' the CI in which case notification should be
sent back to the Editor. Given that scenario, it seems that the first step
of the above (the Editor editing the CI) should also be driven by a step of
a workflow.
In that case, that seems to argue for the creation of a workflow when the
Editor says he wants to edit a CI. When the workflow starts, the first step
would NOT send a notification (since the Editor obvious knows he wants to
edit something:-) ) but would invoke the PLP.
Then, when the Publisher sends the CI back to the Editor to do more edits,
the first step will need to send notification. It will also need to invoke
the PLP again when the Editor starts the task.
What this seems to require is the ability to kick off a PLP from within a
workflow task step. I'm not sure the best way to do this since the only
action a task can take is to invoke a method on an object -- and there is no
obvious object here. We have the object that is being edited, but it seems
odd to invoke a method on that object as the only action would be to invoke
the PLP. That seems potentially confusing.
Another approach might be to use an 'artifactless' workflow and just write
specialized code that kicks off the PLP when the individual tasks start.
When the PLP ends, then the PLP would need to send a message back to code
that would end the task and refresh the workflow.
Hopefully, the above makes sense. Anyone have experience with this kind of
thing and, if so, any suggestions on best practices?
Thanks!
David
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
