Posts

Showing posts with the label SharePoint 2013

SharePoint Designer 2013 Workflow changes

Image
Already, there are so many articles published about the new features and changes in SharePoint Designer 2013 that it’s a little late to write about this. But I think this would be useful. There are many new functionalities and enhancements added into SharePoint designer 2013. Added features allow designers to do more with workflows without requiring a developer to write custom code. If you select SharePoint 2013 option while creating workflow, you will get the following list of new features 1. Stages With 2013, concept of stage is introduced. It acts as containers in workflow, which allows one to structure the workflow from one stage to the other. Stages can be added to a workflow by clicking on Stage icon. Key points for Stages: All actions in the workflow must be contained in a stage A stage can hold one or more workflow actions, and will also have only one  Transition to stage  area.  The  Transition to stage  area defi

Workflow gets canceled automatically with (500) Internal Server Error.

Workflow is getting cancel with the HTTP 500 error.  Problem: RequestorId: 9dea9a29-bb82-214a-0000-000000000000. Details: RequestorId: 9dea9a29-bb82-214a-0000-000000000000. Details: An unhandled exception occurred during the execution of the workflow instance. Exception details: System.ApplicationException: HTTP 500 {"Transfer-Encoding":["chunked"],"X-SharePointHealthScore":["0"],"SPClientServiceRequestDuration":["30"],"SPRequestGuid":["9dea9a29-bb82-214a-92f0-943af4411ac2"],"request-id":["9dea9a29-bb82-214a-92f0-943af4411ac2"],"X-FRAME-OPTIONS":["SAMEORIGIN"],"MicrosoftSharePointTeamServices":["15.0.0.4420"],"X-Content-Type-Options":["nosniff"],"X-MS-InvokeApp":["1; RequireReadOnly"],"Cache-Control":["max-age=0, private"],"Date":["Fri, 31 Jan 2014 20:19:03 GMT"

SharePoint 2013 Workflow error : Custom outcome column returns default option as a task result

Image
I was facing weird issue in SharePoint 2013 Designer workflow. Scenario was, I wanted to create one list workflow where custom list was created programmatically and having my custom workflow task list created through code as well custom content type and outcome columns also created programmatically. Now in workflow stage having an Assign task action and in Outcome options using the above created content type and site columns, see the figure below: Issue here I was facing, Task result was always showing "TaskOutcome:0" i.e the default Outcome in task inspite of I selected any another option. example in above figure result was always coming "Action Plan Created". Tried different approaches to make it work: -While debugging tried various options to make it work, like installed update http://support.microsoft.com/kb/2767999 where it mentioned that "Assume that you use non-ASCII characters to name a task outcome field in a task in a custom workflow.

Errors were found when compiling the workflow. The workflow files were saved but cannot run. - SharePoint 2013

Image
Today while trying to publish the workflow, came across the weird error "Errors were found when compiling the workflow. The workflow files were saved but cannot run." After digging into it, came to the solution that need to    Re-register service into my site using   following commands: Register-SPWorkflowService -SPSite 'https://my-host/mysite' -WorkflowHostUri 'https://workflowhost' -AllowOAuthHttp -Force I reopened SharePoint Designer again and problem disappeared. Hope this will save your time.

SharePoint 2013 Workflow gets canceled automatically

Hi, I was struck with the error of Workflow gets canceled automatically. Scenario was : A new SP 2013 installation, one server with SP, WF, etc and the other is simply SQL Server. Went through the installation steps for Workflow including the powershell bits. In designer, I am able to create a simple workflow and select 2013 as the type. When the workflow is run, is shows internal status is canceled and has the following error text below. RequestorId: 55c6990b-c4a6-352c-4a5b-449fc1aecac4. Details: System.ApplicationException: HTTP 401 {"x-ms-diagnostics":["3001000;reason=\"There has been an error authenticating the request.\";category=\"invalid_client\""],"SPRequestGuid":["55c6990b-c4a6-352c-4a5b-449fc1aecac4"],"request-id":["55c6990b-c4a6-352c-4a5b-449fc1aecac4"],"X-FRAME-OPTIONS":["SAMEORIGIN"],"SPRequestDuration":["61"],"SPIisLatency":["1&