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

Question

Question

Web Request Rule - Unexpected Token Type Colon, expected: DQuote

Rules Laserfiche Cloud
Updated April 24
asked on April 22 • Show version history

I am getting this message running a new web request rule (only from Workflow) but my only tokens are 2 Text types and 1 File type. DQuote is not a type that is an option right now. Are we speaking the same language here?

If I manually run the rule, it works.

0 0

Answer

SELECTED ANSWER
replied on April 23

One of your token values has a colon in the wrong place. Can you track them on the WF side so we can see them before they're being passed into the rule?

Might be better to take this to Tech Support so you don't post values to a public site.

0 0
replied on April 24

There was colons and removing them solved the problem. It was just the name of the file created by forms which by default includes colon characters for the time stamp.

What is the restrictions on characters used in a text type token?

What is a DQuote? Is that something we use to escape characters? My impression of a text token was that any character is supported. This is the first I have run into not being able to hold colon characters in a token or variable.

0 0
replied on April 24

"double quote". I'll see what we can do about the error message and fact that colons in the token value interferes with the parser.

0 0

Replies

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

Sign in to reply to this post.

Details
Related Posts
Loading ...