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

Question

Question

Workflow - Access file from Download Electronic Document activity in script

asked on August 7, 2014

Download Electronic Document has a "token" called "Result File"

From the documentation it is my understanding that this is the actual file or at least a reference to it.

 

The string output is 84:<some file path>

 

Is this an actual path that i can utilize within a SDK Script within workflow? Or is there a stream I can access?

 

2 0

Answer

SELECTED ANSWER
replied on August 7, 2014

Figured this out. the Result File is a temporary path that workflow generates. It is located in the workflow server's configured File system path.

 

Just combine the File system path with the Result File string(be sure to remove the colon) to get the full path.

 

You can then do a File.ReadAllLines(...);  in c# or any other manipulation that can be done on a file.

2 0

Replies

replied on September 3, 2014

I cannot seem to find the temporary path that workflow generates. Here is the output that I get when I call the result file:

 

62:\3a893f54-d159-4d83-aaea-28b650b794c8\DownloadElectronicDocument\29a4d3a2-6aa6-45c5-8588-78b8ea915069.pdf

 

I've searched the entire hard drive for a folder called 3a8...

 

Any ideas?

0 0
replied on September 3, 2014

As David said previously, this will be located in the Workflow Server Folder, which was chosen when the server was configured. By default the path is C:\ProgramData\Laserfiche\WF\ServerData. For the above file you would see a folder named 62 which then contained the file in that location.

 

However, as David also said this is a temporary location, so it will deleted as soon as the Workflow is over. So, if you want to examine it set up a sample workflow which downloads an electronic document then waits.

3 0
replied on September 4, 2014

Thanks for the response. I was in this area but there was no file to be found so that makes sense as to why it was gone. Though it is temp, I didn't realize that it would go away after the workflow was completed (though that makes perfect sense). I will use your suggestion of putting a wait in. Thanks!

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

Sign in to reply to this post.