Hi,
Yesterday I stumbled into an issue. My custom task outcome of SPD 2013 workflow stopped to function properly. It set to default value regardless of the Task Outcome I set programmaticaly in my custom ASP.NET task form.
My task settings looked as follows:
But when I pressed “Reject” or “Approve” button in my form, my ApprovalOutcome variable set to “Approved”. When I changed Default Outcome to “Rejected” this variable set to “Rejected” regardless of pressed button.
Hi,
Today I stumbled into the following error message while was publishing SPD 2013 workflow:
Errors were found when compiling the workflow. The workflow files were saved but cannot be run. Microsoft.Workflow.Client.WorkflowCommunicationException: The request was aborted: The request was canceled. Client ActivityId : 7a290e9c-0917-7088-afc4-e65fd25c5c0b. ---> System.Net.WebException: The request was aborted: The request was canceled. ---> System.ServiceModel.ServiceActivationException: The requested service, 'net.pipe://localhost/SecurityTokenServiceApplication/appsts.svc' could not be activated. See the server's diagnostic trace logs for more information. Server stack trace:
Another symptom is that workflow cancels on start with the following error message:
Hi,
Several days ago I stumbled into an issue. I could not publish even simple 2013 workflow which contained the only “Start a task process” activity (WF with the only “Log” activity worked well). The check for errors passed well, but I could not publish it. I got the following error message:
Hi!
This is the second post of the series related to SPD 2013 Workflows. In this post I will show you how to implement custom ASP.Net task form and embed it into your workflow. Some parts of this task are straightforward; However, there are several pitfalls and changes from SP2010.
Hi, colleagues!
This is the first post of the series related to SPD 2013 Workflows. During this series we will create and improve a solution based on SPD 2013 Workflows.
As you most likely know, SP2013 has possibility to use the new workflow system (based on Workflow Manager). However, it is impossible to use InfoPath task forms with it. In addition, API which we could use for communication with 2010 Workflows doesn’t work for 2013 ones. In this series of posts I want to show you how to create SP2013 workflow, customize its task forms and implement some typical features like reassigning of the task or Request Changes/Task another person with supplying additional information behaviors.
