Filenames not working for signatures in WebForms

[Vinzafy]

Hey all,

I've encountered an issue where filenames are not working for signatures in WebForms. They work in the S123 app, but do not work properly in WebForms launched on mobile devices. Strangely, the filenames seem to work in WebForms on a Desktop.

Survey123 App (filename visible below signature)

WebForm (filename visible below signature)

Viewing the HFL in Pro

The expression I have is the following which is in the bind::esri:parameters column:

fileName=concat(${ff_attd_name_first}, "_", ${ff_attd_name_last}, "_signed_ff_training_waiver_", format-date(now(), "%Y%m%d_%H%M%S"))

Please note that I have seen this thread along with this page from Ismael.

Hopefully it's a simple fix! Thanks all.

EDIT: Extract of the XLSForm is attached here and results from testing on various browsers is found below:

Method Used	Filename
Survey123 App on iPad	Testing_App_iPad_signed_ff_training_waiver_20230413_081355.jpg
Desktop WebForm - Edge	Testing_Desktop Edge_signed_ff_training_waiver_20230413_081134.jpg
Desktop WebFrom - Chrome	signature-20230413081307182.jpg
Desktop WebForm - Firefox	Testing_Desktop Firefox_signed_ff_training_waiver_20230413_081246.jpg
Mobile WebForm - Edge	signature-20230413081934364.jpg
Mobile WebForm - Chrome	signature-20230413081509456.jpg
Mobile WebForm - Firefox	Testing_Mobile Firefox_signed_ff_training_waiver_20230413_082043.jpg

Seems that Firefox is able to respect the filename both in mobile and desktop; chrome in neither; and edge only on desktop.

[ChristopherCounsell]

For issues like this I'd recommend trying to reproduce the unexpected behaviour with a simple form that you can share. This helps rule out if it's tied to your XLSForm or workflows.

Testing with the Images and Annotation sample in Survey123 Connect 3.17.55, the signature_2 question should calculate the fileName of the signed in user.

• In Chrome (desktop) it succeeds
• On Safari (iOS) it names it signature-date, the same behaviour you are seeing.

I would say that this is a bug tied to the browser or device. The next step is to raise it with support, who can formally lodge a defect to be passed to the development team. This also lets you follow the defect status.

We can also tag some of the Survey123 gurus here like @IsmaelChivite to add to their internal system.

[Vinzafy]

Thanks so much for your reply @ChristopherCounsell! Appreciate it. Admittedly this was a rushed post that I should've saved for today. The advice you gave at the end is key for newer users like myself to help the community grow. Thank you!

Attached is a simplified XLSForm where I was able to recreate the issue. I tried in three different browsers both on desktop and mobile. Results are below:

Method Used	Filename
Survey123 App on iPad	Testing_App_iPad_signed_ff_training_waiver_20230413_081355.jpg
Desktop WebForm - Edge	Testing_Desktop Edge_signed_ff_training_waiver_20230413_081134.jpg
Desktop WebFrom - Chrome	signature-20230413081307182.jpg
Desktop WebForm - Firefox	Testing_Desktop Firefox_signed_ff_training_waiver_20230413_081246.jpg
Mobile WebForm - Edge	signature-20230413081934364.jpg
Mobile WebForm - Chrome	signature-20230413081509456.jpg
Mobile WebForm - Firefox	Testing_Mobile Firefox_signed_ff_training_waiver_20230413_082043.jpg

Seems that Firefox is able to respect the filename both in mobile and desktop; chrome in neither; and edge only on desktop.

Additionally, in everything apart from the S123 app, the filename field that I made visible below the signature returns a generic filename.

S123 App

Any Browser - Mobile or Desktop

Hopefully this helps with troubleshooting! In any case, I'll raise this with support when I have the chance later today/tomorrow.

Thanks again.

[IsmaelChivite]

@Vinzafy  @ChristopherCounsell   You rock!  Agreed 100%. This is ready for an official Tech Support case to be opened. 

In the meantime, I will also let my colleagues in the Survey123 team know as a heads up to the Tech Support case. Many thanks!

[Vinzafy]

Thank you for your response Ismael and apologies for my delayed one! Busy end of week.

I've logged a Tech Support case with basically the same details and attachments in this thread (along with linking this thread in that case).

For reference, the case number generated was 03318039.

Thanks again!