We are having an issue where the other forms that we are creating aren't saving their autofill data to the repository. Please see the process below. Does anyone have any tips or advice regarding this part of our process?
Question
Question
Replies
Please provide more details.
Which values aren't being saved? Is it the document name including the form name and Case Name variables? Is it one or both that aren't being saved? If it's both, try saving with just form name and another try with just Case Name to see if you can narrow down the problem. What are the documents currently being named, and what are you hoping for?
If the issue is with Case Name, check the Monitor page variables tab to see what the value of that variable is. Make sure it's the value you're expecting.
Apologies for any vagueness; The form is saving, but it is saving a blank form. It isn't saving the information that has been pulled into the form. The information appears when it is sent out, but it is not present when it is saved to the repository. Please see below.
I noticed since your last post you swapped "Save the form with current process data" to "Save the submitted form from this step". Since the save to repository is directly after the user task you wish to save, both should work for you since the current values should be the same as the ones submitted in that step.
I assume the user task just before the save to repository is "Mail Reporter Letter - Screened in (Reporter Letter)". If it's not, make sure you select the correct user task to save the submission of.
If that doesn't work (it should), you can try to save the form being used in that user task with current process data. Since the save to repository is directly after that submission, current data will be the same as what's submitted in that form. Give that a try.
Next troubleshooting steps
- For the "Save the submitted form" option, go into Monitor page and open up the submitted form from that step. Does it have the values filled in? If the Monitor page form shows values and the saved form does not, you may need to open a support case for an issue with the save to repository service. If the forms is also blank in the Monitor page, your problem is with the submission of that user task.
- For the "Save a form with current data" option, go into the Monitor page and look at the current variables tab. If values exist there but not in the form, this also will require a support case. If values are blank, something else is going on in the process and wiping the values.
Also, I notice there are two back to back save to repository steps. Is the second one configured differently? Does the second one work?
Hi Jared,
The second one does work except for the signature fields, but I believe that's another issue (one signature field will show but the other will not). The second save to repository is our base form with all of the information that populates the other forms.
We just ran a test so that we could give you more information. There are variables listed in the variables tab as you suggested looking into. The email that is sent does contain the correct information and in monitor, it does state that it has successfully saved to the repository, but when it is saved, nothing shows up in the form. Please see below.
Oh, I think I know the problem.
When you are carrying values from one form to another, it seems as though you are creating a new field on the secondary form and setting the default value of the new field to the field from form 1.
Re: is set to Children's Information/Name
This won't work for saving to the repository. You should build your forms differently. When you have a second (or third/forth...) form where you want to show values from a previous form, instead of dragging a new Single line field on to the form and setting its default value, go to the Variables tab above single line and drag the matching existing variable on the form. This will automatically show the current value for that variable on the second form. You can even change the field label and field properties on the second form but still keep the variable the same.
Thank you Jared; we are testing that now!
We did run into the issue where it's not in the same format as we would want it to be. Is it possible to change it so that it keeps the variable but displays it in a different Field type? For example, for the reporter address, it is set to the address field in the first form, but we really just wanted it to be in a multi-line field for the second form.
One way to do that would be to include the multi-line field on the first form and use the calculation =Address on the first form as well. You can use a field rule to hide it so the users filling out the form won't know it's there. By doing the calculation on the first form and submitting, the value will already be set on the multi-line field. THEN you can just use the multi-line field on the second form saved to the repository.
Saving to the repository cannot run calculations, set default values, run lookups, or do many things that happen once the form is loaded to be filled out. You need to do these on the opened first form.
Jared, this worked! However, for some fields we have different values set for choices and it is printing the specified values... For example, our supervisor field:
We have it set so that the values will determine who the form will send an email to. Is there another way to do this?
Thank you for all of your help on this- It's a pretty complicated form!