list of available workflows

[lucille_arkenst]

When the 'Start Advanced Workflow' action is selected, you are presented with the option to choose from a list of available workflows. 

I changed the name of the process definition (scwfublishWhitepaper), so now I am presented with:
Available workflows:
* Adhoc Task (Assign task to colleague)
* Faculty EEO Review (Review & approval of package)
* Review & Approve (Review & approval of content)
* scwfublishWhitepaper (scwfublishWhitepaper)

How do I get rid of scwfublishWhitepaper?

Thanks!

[lucille_arkenst]

Re-indexing did not work.  I could just hard-code the available workflows in choose-workflow.jsp, but… does anybody know where the "WizardManager" stores its information so I can just delete it from wherever that may be?

[lucille_arkenst]

This page looked promising:
https://issues.alfresco.com/jira/browse/ALFCOM-2811?page=com.atlassian.jira.plugin.system.issuetabpa...

So I used:
undeploy definition name [blah]

And it still didn't work.

[mrogers]

The workflow definitions are parsed and added to the JBPM workflow tables.    So a re-building the full text indexes will have no effect whatsoever.    Workflow definitions are also versioned so any in-flight workflows can continue to completion with the definition that applied when the workflow started.

I would have expected the "undeploy" to work through the workflow admin console.   However its a long time since I last used it.

The fix I put in for the old invitation workflows was a UI fix for Alfresco Explorer.   Somewhere there's a list of workflows to show and not show.

[lucille_arkenst]

Hi Mark,

Thanks for the reply.  If you were me, how would you narrow down the search to find the list of workflows to show and not show?  Is it animal, vegetable or mineral?  aka Javascript, XML, or properties file?  (There are 275 files with the word "workflow" in it!)
Also, I am using Alfresco Explorer… would you happen to remember which piece of code was modified for the fix?

Thanks!

[lucille_arkenst]

Does not work: "undeploy definition name <name>"
I had to "undeploy definition <code>" for every single one of them in order to fix the problem.