As there is no activity to get account details (domain\login) of the user who initiated a workflow created using SharePoint Designer, the article explains how to use the “Modified by” field of a separate list item modified by the workflow. As the worklfow runs as the user who initiated it, when the list item is modified, the “Modified By” field will contain the user who initiated the workflow.

Hope this helps.

With a sufficient amount of BA and planning, a form template can be designed to incorporate company branding, as well as using conditional formatting and orther OOB features that allow the form to change dynamically.

Multiple SharePoint lists can easily be updated when a form is submitted, allowing more complex systems and workflow(s) to be configured in SharePoint. Using the OOB browser form for a SharePoint list only allows one item to be edited by a user at a time.

Different (Submit) Data Connections can be executed depending on the data that has been entered into the form, allowing data to be submitted to various areas in a SharePoint site collection based on form Data.

OOB SharePoint Workflows (using SharePoint Designer) don’t allow list items to be updated on a list from a separate site to where the workflows are running. InfoPath forms can be used to initiate various workflows from different SharePoint sites using related form data.

The use of Infopath form in SharePoint will be beneficial in many scenarios, but may not be effective if not planned, developed, tested and implemented in an appropriate manner. Consulting end-users of the system / forms in SharePoint is essential to maximise it’s chance of success and effectiveness within an organisation. To increase the chance of a successful implementation, it is often key to ensure that SharePoint projects are executed as a Business Project, not an I.T. Project.