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

Question

Question

Workflow v9.1.1.365, Login to Laserfiche pop-up box

Workflow Laserfiche Version 9 Search and Retrieval
Updated May 2, 2014
asked on April 29, 2014

To all,

 

I am designing a workflow that logs into Laserfiche and queries a SQL server.  I have two server connections, both use local credentials.  Under "Manage referenced objects" both connections test fine.

 

I publish the workflow, and run the workflow.  Upon checking the Entries tab in the workflow, I receive a pop up "Login to Laserfiche".  By default the dot is at Windows Authentication.  I switch to Laserfiche Authentication.  I enter the local user account and the process runs.  I have checked everything I can think of.  Why does the workflow revert to Windows Authentication?

 

Prior to needing a SQL query the process ran correctly.  Both Database connections "test" fine.

 

 

 

LF_Workflow_Prompt.jpg
LF_Workflow_Prompt.jpg (54.62 KB)
Download
0 0

Answer

SELECTED ANSWER
replied on May 1, 2014

I'm not quite sure what you're trying to do because your post talks about both designing/running workflows and instance details as well as  different activities, but I'll go through it in order and try to clear out the confusion about connections between various parts.

 

Workflow activities that connect to Laserfiche use the Laserfiche connection profile specified for the workflow definition. This uses LFSO (in versions before 9.1) or Laserfiche.RepositoryAccess to connect to the Laserfiche Server. No ODBC drivers are involed, no Windows authentication is supported. This connection profile is used while designing workflows and, on the Workflow Server, when running workflows.

 

Data activities (Query Data, Insert Data, Update Data, Custom Query) connect to 3rd party data sources using ODBC or OLE drivers. The driver type and connection information is specified in the data source setup. If Windows Authentication is specified, then the connection is made using the service user for the Workflow Server service. This has nothing to do with the authentication information on the Entries tab in the instance details.

 

When looking at the instance details, on the Entries tab, we require the user to log in. This was done for security purposes as some users may be allowed to see how the workflow went, but not where the document currently is. The user can specify a LF user or Windows Authentication (no ODBC is involved). The user can specify the same information as the connection profile, but they are not expected to. This information is not saved and, as mentioned above, this connection to LF will time out and disconnect itself if not used for a bit. In your case, since you're also designing workflows, you already know the password for the connection profile, so that's probably why it feels somewhat weird to be asked for authentication again. The feature was designed with users who may have less rights to WF/LF in mind too. This connection defaults to Windows Authentication since that is the more common way of logging into Laserfiche as a regular user. Being prompted for authentication in the Entries tab in the instance details is the expected behavior and not an indication of any connection issues between WF and Laserfiche or between WF and 3rd party data sources.

 

"Connection to the Workflow Server 'localhost' could not be created." means the WFServer cannot be contacted. If you're seeing this on the Designer on the WFServer, it usually means that the WFServer is not running.

1 0

Replies

replied on April 29, 2014

Are you using client automation? I would get that log in pop up when I did. 

0 0
replied on April 29, 2014

I am not sure what that does.  I have not enabled it.

0 0
replied on April 29, 2014

The instance details do not save the authentication nor do they use the profile connection. So you have to log into access the entry information. The connection goes idle and times out if not used for about 2 minutes.

0 0
replied on April 30, 2014

My workflow is uploaded.  I open up workflow fresh.  I immediately run the workflow and I have the same result.  This does not appear to be a time out issue.

 

What is the point of storing Authentication if the server/workflow doesn't use it??

0 0
replied on April 30, 2014

It sounds like there's a little confusion here. The Entries tab in the workflow instance details merely displays a list of what entries have been involved in your workflow, logging in to the Entries tab has NO impact on whether or not your workflow will run.

 

If your workflow was running successfully before you added the activities to query SQL, it sounds like those database lookup activities might be causing the problem. While testing the connection under "Managed referenced objects"/Workflow Data Source Administrator will tell you if the connection to the database is generally successful, it doesn't guarantee that you're pulling the correct information from the data source using your activity.

 

To test the specific query of your Query Data activity, you can use the "Test Query" button from the activity's properties:

 

 

If your query is returning the correct results and your workflow still isn't producing the desired results, I would recommend looking at the workflow instance details (the same place where you were accessing the Entries tab) but focus on the Workflow tab and the Messages tab which will show information regarding what steps happened during the workflow and any error/status messages that came up.

0 0
View 1 previous reply
replied on April 30, 2014

Aaron,

thank you for a well thought out reply.  Unfortunately, I have checked and rechecked this connection.  It is working as intended.  When I click the drop-down box the tables columns all populate.  When I click "Test Query" and remove the token to use an actual value; 1 record is returned.

 

The problem with this issue is my connections test fine any and every way I test them.

 

Originally I was watching a UNC path.  My workflow started with "For Each File" of Type "Windows File Directory".  I then added the correct UNC path.  This worked just fine.

 

After adding Document Importer. I have to watch a folder inside of Laserfiche.  This seems to be the only change between working and login issue plagued workflow.  I now use "Find Entries" as the start of my workflow.  "For Each Entry" uses the Find Entries output.

 

I have workflow validation turned on.  I just started receiving this error.

 

Connection to the Workflow Server 'localhost' could not be created.

 

The Laserfiche connection is ODBC.  When I retraced the steps, it was defaulted to Windows Authentication.  I changed the setting back to Server Authentication.  Again, this link tests fine.  

 

While waiting for a response.  I am going to try to test other connection types.  ODBC seems to want Windows Authentication.

0 0
SELECTED ANSWER
replied on May 1, 2014

I'm not quite sure what you're trying to do because your post talks about both designing/running workflows and instance details as well as  different activities, but I'll go through it in order and try to clear out the confusion about connections between various parts.

 

Workflow activities that connect to Laserfiche use the Laserfiche connection profile specified for the workflow definition. This uses LFSO (in versions before 9.1) or Laserfiche.RepositoryAccess to connect to the Laserfiche Server. No ODBC drivers are involed, no Windows authentication is supported. This connection profile is used while designing workflows and, on the Workflow Server, when running workflows.

 

Data activities (Query Data, Insert Data, Update Data, Custom Query) connect to 3rd party data sources using ODBC or OLE drivers. The driver type and connection information is specified in the data source setup. If Windows Authentication is specified, then the connection is made using the service user for the Workflow Server service. This has nothing to do with the authentication information on the Entries tab in the instance details.

 

When looking at the instance details, on the Entries tab, we require the user to log in. This was done for security purposes as some users may be allowed to see how the workflow went, but not where the document currently is. The user can specify a LF user or Windows Authentication (no ODBC is involved). The user can specify the same information as the connection profile, but they are not expected to. This information is not saved and, as mentioned above, this connection to LF will time out and disconnect itself if not used for a bit. In your case, since you're also designing workflows, you already know the password for the connection profile, so that's probably why it feels somewhat weird to be asked for authentication again. The feature was designed with users who may have less rights to WF/LF in mind too. This connection defaults to Windows Authentication since that is the more common way of logging into Laserfiche as a regular user. Being prompted for authentication in the Entries tab in the instance details is the expected behavior and not an indication of any connection issues between WF and Laserfiche or between WF and 3rd party data sources.

 

"Connection to the Workflow Server 'localhost' could not be created." means the WFServer cannot be contacted. If you're seeing this on the Designer on the WFServer, it usually means that the WFServer is not running.

1 0
replied on May 2, 2014

Thank you for the information on the Entries tab.  The other day, I was constantly being prompted for the username and password.  Today everything seemed to be running smoothly.  The "localhost" error was gone.  I only logged into the Entries tab the one time today.

 

Now that distractions were under control, I was able to wrap up the workflow.  When the workflow runs, Query Data never completes, but all records are processed correctly. (annoying).

 

 

 

 

0 0
replied on May 2, 2014

Does the workflow instance complete or is it stuck running?
 

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

Sign in to reply to this post.

Details
Attachments
Related Posts
Loading ...