Ticket #225 (new enhancement)

Opened 16 years ago

Last modified 14 years ago

Need better sub-workflow support

Reported by: fguillaume Owned by: fguillaume
Priority: P2 Milestone: CPS 3.5.7
Component: CPSWorkflow Version: TRUNK
Severity: normal Keywords:

Description (last modified by fguillaume) (diff)

Need better sub-workflow support.

There is a need for a better way to deal with subworkflows.

Today the way subworkflows are used is:

  • use a proxy folderish document,
  • whenever this proxy follows a transition, the workflow tool applies the same

transition to all subobjects. This means that the subobjects must have a "compatible" workflow which is a pain if they are standard object types (it would mean creating a .cps_workflow_configuration locally for each folderish document object).

We need to find a way to govern what workflows are followed by subobjects simply at by configuring the enclosing workflow. So there is probably a need for additionnal parameters to a workflow, for instance:

  • subobjects of objects in this workflow follow a special workflow
    • the same as this one
    • or another specific one, depending on their types.

But this has to be refined.

Change History

comment:1 Changed 16 years ago by fguillaume

  • Cc edegoute@… added

comment:2 Changed 16 years ago by fguillaume

  • Keywords workflow added

comment:3 Changed 16 years ago by madarche

Having an "assign inert workflow onto subobjects" option would also be very practical.

inert workflow = a workflow that does nothing exept following transitions

comment:4 Changed 15 years ago by fguillaume

  • Keywords workflow removed
  • Component changed from CPSCore to CPSWorkflow

comment:5 Changed 14 years ago by fguillaume

  • Severity changed from normal to enhancement
  • Description modified (diff)

comment:6 Changed 14 years ago by janguenot

  • Version changed from unspecified to TRUNK
  • Milestone changed from unspecified to CPS 3.5.0

Let's say 3.5.0 release although I hope the workflow engine will be replaced by ecm.workflow at this time. But definitely this won't show up in 3.4.0.

Note: See TracTickets for help on using tickets.