Item10289: WORKFLOWFORK does not honor AUTOINC nor allow STATE to be specified

Quick wish list:

• WORKFLOWFORK should allow newnames to be specified using the AUTOINC capability of creating new topics
• WORKFLOWFORK should allow the state of the new topic to be specified

Reason: The WORKFLOW plugin is terribly handy. In my particular case, we are using it to approve copy that gets used in publications. To save time and effort, there are situations where the finalized locked version of a topic could be copied to create a new one. The user would tweak some items and send it off for approval.

Currently, as far as I can tell forking now maintains the current STATE status, which would mean that the copy would not be editable by the person typically doing the copying.

-- KiltBear - 26 Jan 2011

AUTOINC is supported in 1.17. SPecifying the state in the forked topic will never be supported - it would be an implicit transition, which would go against the whole concept of a trackable workflow.

-- Main.CrawfordCurrie - 01 Aug 2017 - 15:12

Commenting is disabled while not logged in