Friday, June 3, 2011

Disadvantanges of SharePoint Designer workflows?

In this post we will discuss about Disadvantanges of SharePoint Designer workflows. Also you can check out:

- Steps in workflow in SharePoint designer

- Customization of quick launch with flyout in sharepoint 2010

- Create an event handler to prevent items from deleting item from SharePoint list using Visual Studio 2010

- You can not loop through items in a list or lists in a site.

- Designer Workflows will not allow to access content on other sites or site collections or anything at farm level or web application.

- You can not call a remote web service from a SharePoint Designer 2010 workflow.

- SPD workflows actions run under the identity and with the permissions of the current user. Impersonation Steps restricts workflow actions from running under the identity and with the permissions of a more privileged user.
SharePoint designer 2010 workflows do not have much control on your process.

- If you find that the business requirements for the workflows that you must build are beyond what SharePoint

- Designer 2010 can provide on its own, you have two different strategies for integrating Visual Studio 2010. The first strategy involves using Visual Studio 2010 to develop custom actions that can be consumed by users creating custom workflows in SharePoint Designer 2010. The second strategy involves using Visual Studio 2010 to develop custom workflow templates.

1 comment:

  1. Ok, I have seen total 3 methods of implementing workflows in SharePoint as you described above.

    So If I get requirement to develop workflows, should I choose the Visual Studio only as suggested method??

    Thanks,
    Naimish

    ReplyDelete