Question

Quickfields - programmatic syntax in metadata

Quick Fields

Updated July 23, 2014

asked on May 29, 2014

When using syntax in QF to reference token values. For example, %(Vendor Name), what configuration would allow for the literal syntax to be used to populate the final metadata (fields, file location, document name).

In other words, how do we end up with documents in our repository named "%(Vendor Name)"?

In my experience you can either put the value, null, or the original input only, not any syntax.

0 1

Answer

APPROVED ANSWER

replied on May 30, 2014 • Show version history

If I read this right, you're asking what would cause Quick Fields to not replace the tokens? Not how to get it to leave the tokens as literals?

If a process does not run, (for ex, if the previous process runs into an error), the token never gets generated, so Quick Fields has no value to replace it.

1 0

View 2 previous replies

replied on May 30, 2014

I've messed up my Quick Fields sessions plenty, but I've never had the token literal leave Quick Fields. It seems like even if it's a bad token, it will at least get replaced with a blank.

0 0

replied on May 30, 2014

Exactly, this is not the case when a token is not populated, then it is blank. The other option is to have a pattern matching token use the original value. But no way to know how the literal syntax gets into the metadata.

0 0

replied on May 30, 2014

Right, if the process runs and the token is created, but has no value, it would be replaced with blank. This would only happen when the token does not exist. It's either a sign of an orphaned token (from the process being deleted) or something went wrong during processing.

1 0

replied on May 30, 2014

I think I am going to have to contact support. I can not explain to a customer why they are seeing %(Vendor Name) in their folder named and document names. We have not configured the session to do this.

0 1

replied on May 30, 2014

If you do end up creating a support case for this matter, please provide a copy of the Quick Fields session (*.qfx) along with a Laserfiche Briefcase that contains sample documents and the template that's being used.

0 0

Replies

replied on May 29, 2014

Are you talking about something like this, but the token syntax never being replaced with the token value?

0 0

View 1 previous reply

replied on May 29, 2014

Can you share the end goal? I don't think it's possible to get Quick Fields to ignore tokens like that, but maybe there's another way to get to what you need.

0 0

replied on May 29, 2014

I just can't understand or explain to customers why this ever happens. It is coding syntax, customers should never see it. It is as if though I wrote a batch file with the syntax

echo Hi %username%!

and the text that appears on their screen was

Hi %username%!

0 0

replied on May 30, 2014

Oh, here I am thinking that you want Quick Fields to do that. I'm sorry.

1 0

replied on June 9, 2014

Here is an example of a couple sitting in the revision pane ready to store. This is not from a currently running session, this is a completed session. No one has seen this?

0 0

replied on June 9, 2014

Yes, I have seen that. I don't know that there's much you can do about it aside from tightening up your pattern matching logic. Are those from required field conditions not being met?

Normally, if I just can't dial the session in tight enough, I'll do stuff like relax the requirements in the template and move validation into a workflow that catches strays. You could also have a staging template that's built for the session and will allow these problem documents to make it through the workflow. Then convert it to your production template. It's a pain, but sometimes a multilayer defense is the only option.

From what I've heard, the new Quick Fields server architecture that is based around repository-type storage (if I'm remembering right) should help alleviate the problem of documents getting stuck in sessions like that.

0 0

replied on June 9, 2014 • Show version history

I just meant that they are ready to store with syntax in the name of the file but no where have I configured a token to populate with syntax if no match is found.

0 0

replied on July 23, 2014

If you opened a support case, and they were able to fix your issue, will you post the conclusion here and click "This answered my question" to let us know?

0 0

You are not allowed to follow up in this post.

Question

Question

Quickfields - programmatic syntax in metadata

Answer

Replies

Sign in to reply to this post.