I’ve been struggling for the last two or three days and racking my brain as to why some of my submissions are considered complete and some are considered partial.
Today I tested a smaller version of my form. I have conditions that hide and show some elements. Some of these elements are repetitive and based on a prior quantity selected. I went for the easy route and grouped them into a container and set the show / hide logic on the container itself rather than the individual elements.
When the individual elements have the “hide logic” and the form is submitted it is marked as complete.
When the container that houses the elements has the “hide logic” the form is submitted and it is marked as partial.
Both were set to required should the conditions be met to show the elements. It appears if the container is set to “hide” and houses elements that are required, it does not take into account the elements aren’t present and provides a partial submission.
The quick solution for me is to set the conditional hide on the elements themselves.
I’m wondering if this is normal behavior and meant to interact this way with containers or just a slight oversight.
I was stumped for a bit and didn’t find a topic that fit this issue.
Hey there, appreciate the detailed description. The completion status however shouldn’t be affected in this case. A required field if hidden by container hide logic is not counted for completion. I was able to confirm on my end that these work the same on either case.
Good to know you’ve already set up in one way that works but if it proves to be a blocker kindly share the user account, form names, and necessary details where the issue can be observed.
As you can see from the testing in the screenshots I’ve provided, when the container is set with the conditional rule the submission is counted as partial.
When the element is set with the rule, the submission is completed.
It appears whenever the container contains the hide / show logic the elements inside the container aren’t updating accordingly and when they aren’t filled, because they aren’t shown the submission is counted as partial.
hey @locayt, the order for checking container-based visibility comes at the end as designed. in the Contact1 form, it seems you’re only going up until the submit step. the submit step still has a button with validate & submit on it which doesn’t make it the definite end of the form.
if you click on Browse our products, that should make submissions (with fields hidden by container logic) be marked as Completed. alternatively, you could uncheck Validate & Submit on that button since you don’t really need it at that point.
@Locayt this could be both due to the Stripe checkout (since it leaves the form) and the Back buttons. for all of your Back buttons, instead of using the Go To Step action can you try with using Go To Previous Step instead? this should help the completion logic identify where the form ends.
@eri Hello, I’ve gotten the form to submit and complete using the inform stripe payment field. I’m noticing that it is really slow during the checkout process and one of the disadvantages of using the inform field vs stripe checkout is not being able to use apple pay and google pay.
Ideally we could utilize the stripe checkout for apple and google pay. Is there a way to validate and submit the form after stripe checkout?
Does feathery have contracts for consulting / building out forms or know of anyone that will provide these types of services?
Hi @Locayt , we have form implementation services available. You can reach out to sales@feathery.io for this enterprise support and provide necessary use case details.
We see you’ve already updated this to in-form stripe. Could you try with reverting to the external stripe checkout and adding this action after the Stripe actions on the final button:
Hi @eri ! Thank you for the help, that did indeed complete the form. Now there appears to be another issue. It doesn’t validate the users payment, if the payment is declined or fails or they just hit complete and exit the page with the “Action 3” “Finish Form” it still submits the form as completed.
The form completion status here reflects as expected and does not cover for the external activities. You should use the Payment Indicator field in the Stripe configuration and use that as the basis for payment completion.
