Ticket #1964 (new defect)

Opened 10 years ago

Last modified 10 years ago

Pending documents content portlets in folderish cases

Reported by: gracinet Owned by: jmorliaguet
Priority: P2 Milestone: CPS 3.5.7
Component: CPSPortlets Version: TRUNK
Severity: normal Keywords: pending folderish workflow
Cc:

Description

In case a folderish document is submitted for publication, all its children land in "pending" workflow state, and get therefore displayed in pending documents portlets. This confuses the users a lot, especially since

  • it turns out that accepting the children prevents later acceptance of the parent;
  • in case the portlet's number of docs is limited, it's possible not to see the parent in it.

Two approaches:

  • fix at the level of CPSPortlets that would check for this configuration;
  • somehow use a different state for submitted children.

The latter would require some work at the CPSWorkflow level, where the submission recurses to add the possibility to use a different initial transition for the children and in CPSDefault profiles, but no work at all in CPSPortlets.

The former is much simpler and somewhat dirtier. After all there's a true difference between a user initiated submission and an automatic process.

Change History

comment:1 Changed 10 years ago by madarche

  • Milestone changed from CPS 3.4.8 to CPS 3.4.9

comment:2 Changed 10 years ago by gracinet

  • Milestone changed from CPS 3.4.9 to CPS 3.5.2

My preference is for the separate state (think aptitude vs apt-get :). Therefore, scheduling for the 3.5 branch (not right now though)

Note: See TracTickets for help on using tickets.