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

Question

Question

Why are we having end arrow in the field? can they be removed?

asked on June 18

Why are we having end arrow in the field? can they be removed?

0 0

Replies

replied on June 20

Big vote to be configurable. See this example. Because of the token selectors, having coding in a table is not feasible and we have to lump them together or display them vertically. I also have no need for them in probably 80% of my templates. 

2 0
replied on July 1

Thanks for the example! We're leaning towards a per-template option, but also considering a table-specific option. As someone where tokens are sometimes used, which best fits your use case?

0 0
replied on July 1

Hi Brianna,

Per template would be fantastic. Like I said, most of my setups do not use these features, but when needed they are invaluable. 

0 0
replied on June 18

Those are token selectors. It is a feature of Laserfiche. You can use tokens to automatically populate fields.

0 0
replied on June 18

@ Blake, I know its a token selector, it is suppose to be there if the field is simply for test that will be filled manually? As you can see in the image, the sender and receiver will be manually input. I need it removed if I don't need token.

0 0
replied on June 18

Yes, they are always there and cannot be removed. 

0 0
replied on June 18

I will push this to Laserfiche developer, please try and fix this. That arrow is not needed when token is not used. Thanks

0 0
replied on June 18

If the token selector is getting in the way of using Tab to navigate fields, you can use the shortcut Shift + Enter to go directly to the next field, skipping the token selector and any other UI elements.

Since they are a common, popular feature, we will not be hiding the UI element.

0 0
replied on June 19

Would be nice to have the option to turn that on and off per template.

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

Sign in to reply to this post.