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

Question

Question

Forms Submissions - Inconsistent Results

asked on May 3, 2017

Could you help me troubleshoot some inconsistent results I'm getting on a new form for Scholarship Applications?  

I’m seeing these inconsistencies:

  • The name of the applicant does not always fill in properly in the name of the document even though the Save to Repository service task is programmed to save as:  2017 Scholarship Application - {/dataset/Last_Name}, {/dataset/First_Name}
    • Sometimes full name comes in right;
    • Sometimes just the last name is there;
    • Sometimes neither first or last name show up in the name of the document.

 

  • Not all the uploaded documents come in:
    • Sometimes, one or more of the uploaded documents do/does not arrive in LF and/or the email Notification does not have a link to the uploaded documents; 
    • So far in testing, never more than two of the 3-4 uploaded documents get added to the email Notification.

 

Thanks for any help you are able to provide!

0 0

Answer

SELECTED ANSWER
replied on May 5, 2017

The attachment issue happens for email service task or email notification in user task? How did you configure the attachment part?

1 0

Replies

replied on May 3, 2017

Hi Connie,

(concerning your first bullet point...) As a process Admin in Forms, go to Reports, select your process, go to Instances and find one of the instance that caused you problem. You should be able to visualize the submitted form. Can you see that the Last Name and First Name fields were well captured on the form?

Additionally, to test it out, you can send yourself an email reusing those same tokens {/dataset/Last_Name}, {/dataset/First_Name} and if the email also doesn't display the full name correctly, there might be something wrong with the variable capture.

 

1 0
replied on May 4, 2017

Thanks, Stephane!

(first bullet point) I believe I have resolved this one - looks like it was because I changed the First Name field from reading "Given Name", but I did not change all the places (original form, review form, plus the variables for both places).  I missed one spot.  And when it missed the whole name, I think that was on the email configuration.  I believe I've fixed that one, as well.  The token I had used was "Name" not a combination of First and Last.

(second bullet) I still can't figure out why it will not bring links to all four (or 3 sometimes) attachments into the email attachments.  Last test was four uploaded attachments, of which all four were successfully brought into LF: 

And only two of those attachments shows up in the email:

0 0
replied on May 4, 2017

Clue maybe?  It's always the same ones that won't attach; the Short Answer Response test document and the GPA one.  (these are mostly blank Word documents used for the testing).

0 0
replied on May 4, 2017

How many File Upload field do you have on your form? Just one where you upload all your files at once? Or do you have multiple fields (one to upload GPA file, one to upload Proof of Completion, one for Short Answer, etc...)? If multiple, did you make sure each one of them are well reference in the email Service task?

Alternatively, can you try creating a brand new form process. With just a File Upload button on the form and an email Service Task sending the attachment, see if it's still the exact same GPA and Short Answer files missing on the attachment. That would be curious behavior but maybe something to do with the file itself.

 

1 0
SELECTED ANSWER
replied on May 5, 2017

The attachment issue happens for email service task or email notification in user task? How did you configure the attachment part?

1 0
replied on May 5, 2017

Ah Ha!!  That was it!  Thanks, guys!  It was in the coding on the email notification.  I had changed the wording on the Upload fields, and just now when I went into how the email notification was configured, it had the old wording on those two.  

Thanks so much!

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

Sign in to reply to this post.