Contents
When you author a workflow in a declarative rules-based, code-free workflow editor, such as Microsoft SharePoint Designer 2010, you are authoring that workflow directly against, and data-binding it to, a specific list or document library in Microsoft SharePoint Foundation 2010.
Below are some of the known issues users can encounter in a tenant where Workflows 2010 is disabled. “User-defined workflows have been disabled by the SharePoint Administrator. User defined workflows will be unable to run. ”
Because workflow authors in SharePoint Designer 2010 cannot create custom activities for use in their workflows, they are limited to the activities and conditions that the developer makes available on the ”safe list” (which should also be approved by a server administrator) that appears in SharePoint Designer 2010.
What happens when workflows 2010 is disabled on a tenant?
When Workflows 2010 is disabled on a tenant, both SharePoint sites and SharePoint Designer will limit operations when trying to create or interact with a workflow based on Workflows 2010. Below are some of the known issues users can encounter in a tenant where Workflows 2010 is disabled.
Which is simpler SharePoint Designer or Visual Studio?
To aid in the rapid design and deployment of workflows, the development process in a declarative rules-based, code-free workflow editor, such as Microsoft SharePoint Designer 2010, is much simpler than those workflows created in Visual Studio.
If you do, SharePoint Designer 2010 uses ASP.NET to automatically generate an initiation form according to your initiation specifications. Similarly, you can create custom Microsoft SharePoint Foundation 2010 tasks for your workflow.
You cannot deploy a workflow authored in SharePoint Designer 2010 to multiple lists. It is only valid for the list for which you created it. Because you are authoring the workflow directly against a list, the workflow is associated with the list at design time.