Item8306: Workflow fork should allow multiple child topics, then set original topic as unedittable

pencil
Priority: Enhancement
Current State: Closed
Released In:
Target Release:
Applies To: Extension
Component: WorkflowPlugin
Branches:
Reported By: Foswiki:Main.DeanSpicer
Waiting For:
Last Change By: CrawfordCurrie
I'd like the WorkflowPlugin fork feature to do the following:

TopicA forks TopicA1 and TopicA2 (history of both should point to TopicA)

TopicA history should point to both TopicA1 and TopicA2, and then TopicA then should be "locked" or unedittable.

-- DeanSpicer - 09 Oct 2009

Added "newnames" and "lockdown" parameters, and re-ordered the parameters to make them compatible with the other macros.

Dean, I mailed you a zip; can you acceptance test, please, and if it's OK we can release?

-- CrawfordCurrie - 19 Oct 2009

Acceptance test done. Works as expected except for the linking of parent to child in the WORKFLOWHISTORY. The two child topics didn't link automatically. Child topics were named RMA000027A and RMA000027B.

-- DeanSpicer - 19 Nov 2009

Fixed that.

-- CrawfordCurrie - 22 Jan 2010

 

ItemTemplate edit

Summary Workflow fork should allow multiple child topics, then set original topic as unedittable
ReportedBy Foswiki:Main.DeanSpicer
Codebase
SVN Range Foswiki-1.0.7, Sun, 20 Sep 2009, build 5061
AppliesTo Extension
Component WorkflowPlugin
Priority Enhancement
CurrentState Closed
WaitingFor
Checkins WorkflowPlugin:9b577b3b30a4 distro:94376738a83e WorkflowPlugin:45a19cc3a22f
ReleasedIn
Topic revision: r7 - 22 Jan 2010, CrawfordCurrie - This page was cached on 16 Sep 2021 - 17:13.

The copyright of the content on this website is held by the contributing authors, except where stated elsewhere. See Copyright Statement. Creative Commons License    Legal Imprint    Privacy Policy