concept for future magnolia (possibly 3.5) (MAGNOLIA-587)

[MAGNOLIA-811] Workflow Created: 13/Apr/06  Updated: 03/Dec/13  Resolved: 03/Dec/13

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Sub-task Priority: Major
Reporter: Philipp Bärfuss Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-863 workflow: impovements for 3.0 Closed
Template:

 Description   

First steps are done in 3.0.

  • Integration of OpenWFE
  • Flows
  • Inbox
  • eMail
  • Timebased Activation
  • ..

Following some notes for the next steps in 3.1

  • we should use the commands for the most generic topics (currently mainly used for acitvation)
  • a mgnl WorkItem providing more convinience methods
  • a property on the workitem defines the dialog to use (can change in the flow)
  • used to start a flow
  • used to proceed / reject
  • flow designer (currently you must upload the flow definitions using a servlet)


 Comments   
Comment by Philipp Bärfuss [ 03/Dec/13 ]

Hi,

Thanks for reporting and/or commenting on this issue. We are currently reviewing issues that have had no or minimal activity for several years. Magnolia has evolved tremendously since this issue was reported; in order to focus our work, we are closing such issues.

We realize that some of these might still be valid today - and we ask for your cooperation here. In some cases, we will be linking to overarching stories, or simply more up-to-date similar issues. If you believe this issue is still relevant today, please leave a comment below and we will get back to you.

Cheers,

Generated at Mon Feb 12 03:20:53 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.