You are viewing limited content. For full access, please sign in.

Question

Question

StartWorkflowDirectly not in SDK Documentation

asked on August 13, 2015

We have a scenario where we can't trigger worklfow using StartWorkflow function BUT we can trigger a workflow using StartWorkflowDirectly function.

We can't find StartWorkflowDirectly in SDK Documentation as well as I got 0 hits when I search here at Answers portal.

 

DOESN'T Work:

workflow.StartWorkflow(string.Empty, new StartingEntry(), new Initiator(), new WorkflowCreationOptions(), parameters);

 

DOES Work:

                    workflow.StartWorkflowDirectly(string.Empty, new StartingEntry(), new Initiator(), new WorkflowCreationOptions(), parameters);

 

0 0

Answer

SELECTED ANSWER
replied on August 13, 2015

In general, we'd prefer if you used the Workflow Web Service to start workflows. See https://answers.laserfiche.com/questions/70701/REST-API--Workflow-Web-Service for more information. 

As for the WFSO functions, they both start a workflow, the difference is in the transport mechanisms they use. 

StartWorkflow is a function that makes use of the lfwf_creation Message Queue. Odds are you don't have permission to enqueue the message remotely. 

StartWorkflowDirectly bypasses the queue and starts the workflow directly with the server and was added to support the 'Run Workflow' button in the Workflow Designer. 

For StartWorkflow, you will want to look in the Computer Management console and check the message queueing section. In particular, both the Outgoing Queues and the Transactional dead-letter messages in the System Queues. You'll either see connection issues in the outgoing queues or access denied messages in the dead letter queue. This article briefly touches on the subject https://www.laserfiche.com/support/webhelp/workflow/8.3/en-US/Content/Server%20and%20Subscriber%20Installation%20Configuration.htm  . 

 

 

 

 

 

 

2 0
replied on August 13, 2015

Thanks for all the useful information Ed. It does clears alot of confusion.

Also, as you have suggested, I will look into using Workflow Web Service to trigger our workflows.

Thanks

0 0

Replies

You are not allowed to reply in this post.
You are not allowed to follow up in this post.

Sign in to reply to this post.