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

Question

Question

Workflow write to PDF activity results lack a comma for thousands delimiter

asked on August 3, 2021

Hello, our Customer is observing the lack of the comma separator for thousands delimiter when Workflow writes to a PDF fillable field.

We have tested the PDF and the PDF field DOES insert the thousands delimiting comma into a number which is typed or pasted into the field, however, when Workflow writes the value into the fillable PDF field, the comma does NOT occur.

What is different when Workflow writes a value compared to when I just type into the field that stops the PDF from inserting the comma?

Thx

0 0

Answer

SELECTED ANSWER
replied on August 3, 2021

PDFs can be so complex and run tons of different validation scripts/javascript/formatters just like HTML. It is likely this particular formatter is not ran when inserting the value via code. My recommendation would be to just add it at time of workflow. Use token formatters for this.

3 0

Replies

replied on August 3, 2021

What is the source of the value being used by Workflow? Have you tried adding a Track Tokens activity to the workflow to make sure it is definitely holding the value as a string with the comma?

The reason I ask is that "display" formats are not necessarily the same as the actual value, so if you retrieve a value from an entry field, Forms variable, etc. it may display with the comma, but that's not the "actual" value workflow would be retrieving so you may just need to format it as John mentioned.

1 0
replied on August 3, 2021

@████████ thanks Jason, we observed the PDF fillable field format "number" with style: 1,234.56 does add the comma for thousands when we pasted or typed digits without the comma...  

... so an assumption was made ( I know ) that the PDF field would also generate its own comma when LFWorkflow wrote the value.

going forward, we will use token magic in LFWorkflow to force the value to contain the comma before it arrives at the PDF.

Regards, and thanks to @████████ as well

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

Sign in to reply to this post.