
|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
Windows XP, Confluence Standalone 2.7.2 (zip version) (both Plugin and Confluence with Evaluation key)
|
|
When I began working with the Approval Plugin I thought I'd just use the approvals on workflows too (using a workflow), so that for instance the Administrator of the space, where workflows can be defined, can control which workflows will be used (only published ones, since my so-called Moderators could also create workflows on this space, but those would need to be approved by the Space Admin in order for them to use them). However that is not how workflows work at all. The effects of publishing a workflow:
- Only the workflow in Edit (View) is used (and is always immediately applied).
- Deleting the workflow in Edit (View) destroys the published workflow (creates errors messages in the published tab)
- The workflow is a space-workflow on the space where the workflow is implemented in and the workflow has already been published using the workflow, then deleting the workflow in Edit (View) creates {approval} corpses, which cannot be deleted like normal (see
APRV-130). The only way to delete the workflow completely is then to delete the approval history (deletes the corpses and removes the Published Tab).
|
|
Description
|
When I began working with the Approval Plugin I thought I'd just use the approvals on workflows too (using a workflow), so that for instance the Administrator of the space, where workflows can be defined, can control which workflows will be used (only published ones, since my so-called Moderators could also create workflows on this space, but those would need to be approved by the Space Admin in order for them to use them). However that is not how workflows work at all. The effects of publishing a workflow:
- Only the workflow in Edit (View) is used (and is always immediately applied).
- Deleting the workflow in Edit (View) destroys the published workflow (creates errors messages in the published tab)
- The workflow is a space-workflow on the space where the workflow is implemented in and the workflow has already been published using the workflow, then deleting the workflow in Edit (View) creates {approval} corpses, which cannot be deleted like normal (see
APRV-130). The only way to delete the workflow completely is then to delete the approval history (deletes the corpses and removes the Published Tab).
|
Show » |
|
I changed the title and made it a suggestion.
The workflows are not meant to work on worklows, as far as published versions is concerned.
Could you elaborate on why would you allow Moderators to create workflows? Workflow creating is not trivial and allowing too many people creating them could be a maintenance nightmare...