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

Question

Question

Bug Substitution Quick Fields Scanning

Laserfiche Quick Fields Scanning
Updated August 29, 2017
asked on August 29, 2017

Hi all,

 

Under Quick Fields, I'm using "Substitution" in my process and everything is ok.

 

I published this session on the server.

Using Quick Fields Scanning, it looks like the "substitution" doesn't work.

Using Quick Fields Scanning, all fields using "Substitution" dont have the value. Others are ok.

Did I make a mistake?

0 0

Replies

replied on August 29, 2017

It might a problem with the configuration of your substitutions because it seems to be taking the literal string value of what you entered and instead of retrieving the token value.

0 0
replied on August 29, 2017

I'm agree with you Jason, but I don't understand why under Quick Fields it retrieving the token value and under Quick Fields Scanning it taking the string.

 

0 0
replied on August 29, 2017

Okay, I misunderstood. If it is working in Quick Fields and not in Quick Fields Scanning, then I'm doubtful the substitution set up would be the cause.

0 0
replied on August 29, 2017

Can you look in the Messages pane of Quick Fields Scanning to check if the Zone OCR tokens that get substituted are resolved? The problem could be that the Zone OCR fails and so the Substitution runs on the unresolved token names

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

Sign in to reply to this post.

Details
Related Posts
Loading ...