Skip to content
This repository has been archived by the owner on Aug 13, 2022. It is now read-only.

Advanced workflow integration #58

Open
espaan opened this issue Aug 18, 2011 · 1 comment
Open

Advanced workflow integration #58

espaan opened this issue Aug 18, 2011 · 1 comment

Comments

@espaan
Copy link
Member

espaan commented Aug 18, 2011

--orig 178 by pnfilip

It seems that Content needs the implementation of the Zikula workflow system.

reason¶
In order to delegate the page creation and also provide a good quality of content, several persons are involved in the process of creating/updating a page. That's why for an easier document management (avoid e-mailing word documents, record changes, ...) states of creation could be associated to each pages.

recommendation¶
•3 basic states should be considered at first: created, revised, approved.
•By default, the page is not online and can only be previewed if you have edit rights minimum.
•Each step could have a color associated in order for the revisers or the approvers to clearly identify the documents in the list.
Attachments

Change History
comment:1 Changed 10 months ago by espaan
■Milestone changed from unassigned to 3.2.1
comment:2 Changed 8 months ago by espaan
■Milestone changed from 3.2.1 to 4.1.0

@espaan espaan modified the milestones: 4.5.0, 4.2.0 Jul 17, 2014
@Guite Guite modified the milestones: 4.5.0, Future, 5.0.0 Jan 8, 2018
@Guite
Copy link
Member

Guite commented Jan 8, 2018

5.0.0 will be based on MOST and therewith support the Symfony workflow system. But we are not going to utilise any workflow including approval systems yet in the first step.

@Guite Guite added the Postponed label Jan 8, 2018
@Guite Guite changed the title Zikula workflow integration Advanced workflow integration Jan 8, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants