JotForm is a free online form builder which helps you create online forms without writing a single line of code. No sign-up required.
We believe that if one user has a question, there could be more users who may have the same question. This is why many of our support forum threads are public and available to be searched and viewed. If you’d like help immediately, feel free to search for a similar question, or submit your question or concern.
Encrypted Forms: Not possible to decrypt Input Mask based fieldsAsked by ptomshack0 on October 07, 2015 at 05:35 PM
I have 2 forms that are encrypted. I read in the forums that I will only have 1 key. I have that key.
When I use my key, some of my entries are not becoming un-encrypted correctly.
What is strange is that it is works some times and other times it does not. So for example, I have a phone number field that on some of the responses comes through fine. On others, it is still scrambled.
Unfortunately, we can't check your form submissions because we don't have the key to check your submissions. Does it happen randomly on the form fields? Can you provide us a screenshot of your submission where the issue occurred?
We will wait for your response.
It only seems to be happening the telephone fields. Not on all submissions. On the submissions that it does occur, it occurs in all the fields (I have multiple phone# fields).
Is it possible to remake the form (hopefully a copy function) and issue new keys?
Here is the field properties that I used.
I am afraid that there is some bug between the Input Mask and the form encryption options. I would like to suggest disabling the Input Mask option if you would like to use the form encryption. It should fix the issue for incoming form entries.
We have escalated a bug report ticket to our Development Team about this issue. There is no ETA, but we will let you know if we have any updates.
I am sorry to inform you, but we do not have any updates as of this time. I have moved your inquiry into a separate thread to attach an additional bug report.
We are very sorry for the long wait, but this bug is now fixed.
Please feel free to contact us again should you have any other issues or concerns.