They don't have any effect whatsoever, all form data is recorded and an entry is made and if you have a redirect, the form will continue to the redirect.
Sorry for kicking this, but I ran into this post today and wondered for a while already why the WorkFlowExecutionStatus has no influence on the workflow being executed.
I would expect that
Cancelled would mean that the current workflow needs to cancelled, resulting in that all the subsequent workflow tasks are not executed.
Failed would mean that the current workflow task has failed, but all subsequent tasks are being executed.
Is that correct? And is this missing in the workflow implementation?
WorkflowExecutionStatus.Failed has no effect
If you do;
public override WorkflowExecutionStatus Execute(Record record, RecordEventArgs e) {return WorkflowExecutionStatus.Failed;
}
Or
public override WorkflowExecutionStatus Execute(Record record, RecordEventArgs e) {return WorkflowExecutionStatus.Cancelled;
}
They don't have any effect whatsoever, all form data is recorded and an entry is made and if you have a redirect, the form will continue to the redirect.
I noticed that this question was asked sometime ago, however it does not have an answer (except for using session).
How do I stop the workflow entirely?
Sorry for kicking this, but I ran into this post today and wondered for a while already why the WorkFlowExecutionStatus has no influence on the workflow being executed.
I would expect that Cancelled would mean that the current workflow needs to cancelled, resulting in that all the subsequent workflow tasks are not executed. Failed would mean that the current workflow task has failed, but all subsequent tasks are being executed.
Is that correct? And is this missing in the workflow implementation?
I ran into the same issue. Does anyone have the answers? Thanks.
is working on a reply...