Question

Launching client through workflow

Workflow SDK

Updated April 9, 2014

asked on April 8, 2014

I am using ClientAutomation through workflow. When I run the script that I have independently it is able to launch the client and have it do what I need it to. Though when I have the workflow automated it gives me a warning, "Timeout waiting for client startup". Has anyone ran into this issue?

0 1

Answer

SELECTED ANSWER

replied on April 9, 2014

The Client Automation Tool (CAT) is not supported in this type of configuration. As Chad stated above, the Workflow runs as a service and has no way of displaying a GUI application. This means that it has no way to respond to errors and/or popup/dialog windows for user interaction generated by the GUI application.

CAT is designed and intended to be used with the client application by users who can see and interact with the client desktop. As you found, without the client interaction ability, you can find your integration unable to proceed and in effect, break or stall your workflow or service application.

1 0

Replies

replied on April 8, 2014

Your calling the client installed on the workflow server from an SDK script in workflow? Workflow runs from a service account, when that account opens a session in Windows there is no user interface to display graphical applications. It might help to provide some details on what your trying to do.

3 0

replied on April 8, 2014

It turns out I had a previous session running in the background that was conflicting.

0 0

You are not allowed to follow up in this post.

Question

Question

Launching client through workflow

Answer

Replies

Sign in to reply to this post.