Can I remove / hide the "Approval" and "Collect Feedback" workflow in the "Start a New Workflow" page?

Mon, 02 Jul 2007 15:19:43 Z

Tks in advance!

Best Regards,

Mar

Can I remove / hide the "Approval" and "Collect Feedback" workflow in the "Start a New Workflow" page?

Mon, 02 Jul 2007 17:55:10 Z

Just go List Settings, Workflows and remove it

Can I remove / hide the "Approval" and "Collect Feedback" workflow in the "Start a New Workflow" page?

Tue, 03 Jul 2007 07:42:14 Z

Tks for your reply, but...

Do you mean the workflow settings of the document library? I do not add any workflow to it. It shows: "There are no workflows currently associated with this list."

However, when I click workflows of a document, I still find "Approval" and "Collect Feedback" in the "Start a New Workflow" area. Pls help! Tks!

Can I remove / hide the "Approval" and "Collect Feedback" workflow in the "Start a New Workflow" page?

Tue, 03 Jul 2007 14:28:06 Z

You're going to need to deactivate the Routing Workflows Features at the site collection level.

-Dave

Can I remove / hide the "Approval" and "Collect Feedback" workflow in the "Start a New Workflow" page?

Fri, 13 Jul 2007 01:36:30 Z

Tks Dave! But is there any way other than deactivate the Routing Workflows Features?

Can I remove / hide the "Approval" and "Collect Feedback" workflow in the "Start a New Workflow" page?

Fri, 13 Jul 2007 05:39:36 Z

Hi Mar s,

There is no way other than what Dave said. This is the feature for Approval and Feedback, If do not want to show up, you should deactivate the feature in site collection feature or by stsadm.exe tool.

thanks
Praveen

Can I remove / hide the "Approval" and "Collect Feedback" workflow in the "Start a New Workflow" page?

Fri, 13 Jul 2007 12:26:56 Z

You can edit the corresponding XML-files (ReviewApproval.xml/ReviewFeedback.xml) in program files\common files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\ReviewWorkflows (make a backup before...)

and set <AssociateOnActivation>true</AssociateOnActivation> to <AssociateOnActivation>true</AssociateOnActivation>.

Then there's no "automatic" association to the "document"-content type. But you can use it if you associate the workflows manually.

Hope that helps,

with kind regards,

Michael

Can I remove / hide the "Approval" and "Collect Feedback" workflow in the "Start a New Workflow" page?

Fri, 10 Aug 2007 00:49:45 Z

MAppinger wrote:

and set <AssociateOnActivation>true</AssociateOnActivation> to <AssociateOnActivation>true</AssociateOnActivation>.

Then there's no "automatic" association to the "document"-content type. But you can use it if you associate the workflows manually.

Hope that helps,

with kind regards,

Michael

I have the same situation as the OP and would like to remove the built in approval workflow from the list of available workflows.

I've edited the ReviewApproval.xml (assuming you intended to change true to false in your instructions). What else would need to be done to make this change take effect? Do we have to de-activate and re-activate a feature? Restart IIS?

Thanks.

Can I remove / hide the "Approval" and "Collect Feedback" workflow in the "Start a New Workflow" page?

Thu, 02 Jul 2009 18:35:58 Z

Just go to:
Shared Services Administration> Site Settings > Site Content Type Gallery > Site Content Type
select "Document" or that content type where you want to remove "Approval" or "Collect Feedback" OOB workflow
click "Workflow settings" and hear you can remove the "Approval" and "Collect Feedback"

enjoy.

Can I remove / hide the "Approval" and "Collect Feedback" workflow in the "Start a New Workflow" page?

Thu, 17 Sep 2009 11:16:18 Z

Just go to:
Shared Services Administration> Site Settings > Site Content Type Gallery > Site Content Type
select "Document" or that content type where you want to remove "Approval" or "Collect Feedback" OOB workflow
click "Workflow settings" and hear you can remove the "Approval" and "Collect Feedback"

enjoy.

Yes this way you can remove/hide OOB workflows from "Start a New Workflow" page but it is recommended to created your own Site Content Type to do this. Otherwise your setting will effect to all document libraries or that all libraries which are using this content type.

Maanu