Ticket #49 (Clôturé Amélioration: Résolu)
Develop a mechanism for implementing variability in workflows
| Reported by: | gdelannay | Owned by: | gdelannay |
|---|---|---|---|
| Priority: | Haute | Milestone: | PloneMeeting 1.0 and 1.1 |
| Component: | Produit PloneMeeting | Severity: | Non bloquant |
| Keywords: | workflow, interfaces, adapters | Cc: |
Description
Create a mechanism, based on Zope3 interfaces and adapters, that allows to create specific, different workflows with each specific product using PloneMeeting?, but that share commonalities, like conditions or workflow scripts.
Change History
comment:2 Changed 3 years ago by gdelannay
- Status changed from Nouveau to Clôturé
- Resolution set to Résolu
Now it is possible to define, in a sub-product, an interface "IMeetingItemXXXWorkflowable" and an adapter "MeetingItemXXXWorkflowable" that adapts a meeting item to the previous interface. This way, one can put meeting item-specific behavior that is specific to workflow in the adapter. Because the adapter may inherit from an adapter defined at the PloneMeeting? level, it may only redefine necessary conditions and/or actions. This mechanism is not only vailable for meeting items, but also for every content type (meeting, report).
Maybe in the future we will need more interfaces and adapters than just one for each content type/workflow, both in PloneMeeting? and in sub-products. If necessary, we will open a new ticket in order to implement this change.
This mechanism has een implemented in the Egw sub-product.
