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

Question

Question

Retrieve Forms Content tokens not working with Search Repository Activity

asked on August 15, 2014 Show version history

Hi,

 

I just ran into a situation where the client was using the tokens generated in a Retrieve Forms Content activity.  They later had these tokens as values in the Search Repository activity.  When I tried to test the search activity with a value(11111) it returned zero results.  However, when I replaced the token in the syntax with the same 11111 I just searched for, it returned the 1 result it should have.

 

I added an Assign Metadata activity and pushed all the info into a template, then used the Retrieve Field Values activity to generate tokens.  Then I used the tokens from the RFV activity in the search syntax and tested it again with the 11111 value.  It returned the 1 that was intended.

 

After doing this, I tested the entire process start to finish and it worked as intended.

 

Any thoughts on this?  Is this a bug in workflow or forms?

 

Thanks!

0 0

Replies

replied on August 15, 2014

have you changed the property of the workflow to include it being started from a laserfiche form? That is how you make those tokens available if you are starting the workflow from Forms. 

 

If you are starting it from a document in the repository, then you will already have those values as a token, so why use a different token that obviously are not working out for you. 

 

Have you tried tracking tokens in the workflow when it is running in its configured version that was giving you trouble? What are the token values coming in as? 

 

 

0 0
replied on August 15, 2014

When I track the tokens, the values for the Retrieve Forms Content show up.  I didn't check to see how the workflow was starting initially, but I find it odd that the track tokens shows values for the Retrieve Forms Content, but will not use them.

 

I thought it was especially odd that, when testing the search with the RFC token in there, when it prompts for a value for the token and I added "11111" to it, it found nothing.  But if I replaced it with a different token and entered the same value, it worked.

0 0
replied on August 15, 2014

 

Click "View Workflow properties" and report back

 

Can you provide use with the the order of events leading up to the retrieve Laserfiche Forms Content activity? I understand if you cannot post a screenshot, but understanding what is happening before to see if those tokens should even exist is important. 

 

I also do not understand why the search activity is not working, but I am instead focusing on what I am familiar with since I do not have any clear answer or help I can provide in that instance. 

0 0
replied on August 15, 2014 Show version history

Ah, I see what you mean.  It is not set to be started by LF Forms.  This workflow starts when a document is created in the \LF Forms\Wellness Notification\ folder.

 

 

Here's the information for the activity from the Track Tokens:

 

Here is a screenshot of the entire workflow.  The only thing not shown is the Track Tokens at the bottom:

 

Here is the RLFC Activity:

 

What the search is intended to do is use the "Badge Number" to search for the employee's folder.  The employee folder has a template on it that corresponds to that value.  Then the move entry activities at the bottom use the output full path to file the Form into the appropriate folder.

 

Let me know if you need any other info!

 

Edit: The values from the RLFC Activity seem to be available for the assign field values activity, though.  

0 0
replied on August 15, 2014

can you post the search syntax? or at lest confirm what the token is? ( I assume it's 'Bagde Number')

 

Also, have you tried setting a token to the value of the search syntax and tracking that token to see what it returned? This will help you verify the token is populating properly. You should be able to use the tracked value in the advanced search area of the LF Client and returned 0 if it returns 0 in the workflow when running

0 0
replied on August 15, 2014

The original search syntax has changed since I got the workflow running again.  All I changed was the Badge Number token from the RLFC activity to the new Retrieve Field Values "Employee ID" token I assigned it to.

0 0
replied on August 15, 2014

so is this now considered resolved? I see the token is bagde number and you keep saying badge number, are you sure maybe the token being mispelt wasnt the issue? Also, the track tokens activity return ..._badge as the token name, so yet another variation from the intended.

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

Sign in to reply to this post.