https://connect.hyland.com/t5/alfresco-archive/why-does-startworkflowwizard-restrict-nodes-to-content/m-p/80492#M53726 <HTML><HEAD></HEAD><BODY><SPAN>The workflow service itself does not prevent the use of folders in workflows. </SPAN><BR /><BR /><SPAN>The UI, as you have pointed out, does. This was purely down to a resource/time/effort decision when the UI was being built.</SPAN></BODY></HTML> Wed, 25 Apr 2007 06:30:29 GMT gavinc 2007-04-25T06:30:29Z https://connect.hyland.com/t5/alfresco-archive/why-does-startworkflowwizard-restrict-nodes-to-content/m-p/80491#M53725 Folders and their sub-types need to be routeable by advanced workflows. But the StartWorkflowWizard seems to restrict nodes to content and its sub-types (see init method below). Why is this? Shouldn't advanced workflow be able to handle any type of node?&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // add the item the workflow wizard was Fri, 13 Apr 2007 16:19:43 GMT https://connect.hyland.com/t5/alfresco-archive/why-does-startworkflowwizard-restrict-nodes-to-content/m-p/80491#M53725 jpotts 2007-04-13T16:19:43Z https://connect.hyland.com/t5/alfresco-archive/why-does-startworkflowwizard-restrict-nodes-to-content/m-p/80492#M53726 <HTML><HEAD></HEAD><BODY><SPAN>The workflow service itself does not prevent the use of folders in workflows. </SPAN><BR /><BR /><SPAN>The UI, as you have pointed out, does. This was purely down to a resource/time/effort decision when the UI was being built.</SPAN></BODY></HTML> Wed, 25 Apr 2007 06:30:29 GMT https://connect.hyland.com/t5/alfresco-archive/why-does-startworkflowwizard-restrict-nodes-to-content/m-p/80492#M53726 gavinc 2007-04-25T06:30:29Z