We were wondering if there was a way to limit the number of submissions a Formulate form could have before disabling. I have been delving into the code a bit and see that when the Formulate submission gets sent to the database, you can retrieve it on the backoffice, this uses AngularJS.
However, I do not know if we can or how I might be able to utilize this previously written code to collect the number of submissions. Also, I am a little unclear how to extend Formulate by creating a 'form submission handler', as your Guided Tour as well as your Formulate Extensibility pages do not go into any practical code details in how to do this.
Thanks for your time, and any pointers to capturing the number of successful form submissions and how to disable the form programmatically when the maximum number of submissions is reached would be of great value.
We were wondering if there was a way to limit the number of submissions a Formulate form could have before disabling.
Not super sure why you'd want to do this, but two options come to mind:
Submit a pull request so that the Submitting event (see here) allows for a form submission to be cancelled (e.g., by adding a boolean to the FormSubmissionContext). Then in your app, you can subscribe to that event and use whatever logic you like to cancel the submission.
Handle the logic for displaying (or not displaying) the form on your side. If too many submissions have been received for that form (using whatever logic you like to indicate "too many" submissions), then no longer display the form. You can query the table Formulate uses to store submissions (IIRC, it's called FormulateSubmission), supposing you're using the Store Data handler. Alternatively, you can create your own handler that has the singular purpose of counting form submissions using whatever method you like (e.g., storing the count to a database table).
I am a little unclear how to extend Formulate by creating a 'form submission handler'
Note that you can't do template: formulateDirectives.get('some-path.html') (that's internal to Formulate). Instead, you'll do templateUrl: '/some-path.html'.
In many cases, the trickle of form submissions means a form can be manually closed off and the few extra posts can be managed personally.
But in cases where a wave of submissions are expected in a short period of time (ie, LAPD applications might reach 5000 submissions in 10 minutes) you really want to restrict the form from displaying to new visitors and manage people who already have the form open when they hit "submit". After the limit is reached it would be nice to show them an on-screen message of some kind (ie, "Sorry, the 5000 applications limit has been reached. Please try again next time").
A few minutes spent counting and checking totals could result in thousands of unwanted additional submissions appearing before you shut it down manually and lots of unhappy people.
Looking at your Submissions.cs file, you mention that the FormSubmissionContext has a boolean to prevent form submission, but looking here at the anonymous class you create, and the subsequent Submit method, there seems to be no way to halt the submission using this context.
I understand the concept, but without some way of checking that a flag is changed (and having a flag to change) before the form is submitted, this will not prevent the form from submitting.
Thanks for any time, if you wish I can add a small bit of code change for your vetting.
Looking at your Submissions.cs file, you mention that the FormSubmissionContext has a boolean to prevent form submission
Nope, I said that you can submit a pull request to create that functionality. It doesn't exist yet. Here is what I said for your reference:
Submit a pull request so that the Submitting event (see here) allows for a form submission to be cancelled (e.g., by adding a boolean to the FormSubmissionContext). Then in your app, you can subscribe to that event and use whatever logic you like to cancel the submission.
For anybody following this, The Fuel Agency submitted a pull request that has been merged in and released with the latest version of Formulate (2.2.0).
Limiting the number of successful Formulate submissions
Hello
We were wondering if there was a way to limit the number of submissions a Formulate form could have before disabling. I have been delving into the code a bit and see that when the Formulate submission gets sent to the database, you can retrieve it on the backoffice, this uses AngularJS.
However, I do not know if we can or how I might be able to utilize this previously written code to collect the number of submissions. Also, I am a little unclear how to extend Formulate by creating a 'form submission handler', as your Guided Tour as well as your Formulate Extensibility pages do not go into any practical code details in how to do this.
Thanks for your time, and any pointers to capturing the number of successful form submissions and how to disable the form programmatically when the maximum number of submissions is reached would be of great value.
Not super sure why you'd want to do this, but two options come to mind:
Submittingevent (see here) allows for a form submission to be cancelled (e.g., by adding a boolean to theFormSubmissionContext). Then in your app, you can subscribe to that event and use whatever logic you like to cancel the submission.FormulateSubmission), supposing you're using theStore Datahandler. Alternatively, you can create your own handler that has the singular purpose of counting form submissions using whatever method you like (e.g., storing the count to a database table).Here is the short version:
IFormHandlerType: https://github.com/rhythmagency/formulate/blob/6ce70e7cb8be672ce4b92f1ef0c4855c0b62a6dd/src/formulate.app/Forms/Handlers/Email/EmailHandler.cstemplate: formulateDirectives.get('some-path.html')(that's internal to Formulate). Instead, you'll dotemplateUrl: '/some-path.html'.If you manage to get something working, would really appreciate it if you could write something up to add to the documentation: https://github.com/rhythmagency/formulate/tree/gh-pages/articles
If you send me a pull request for a markdown file in that folder, it'll show up on the website, such as with this example: http://www.formulate.rocks/articles/custom-field-types
Limiting form submissions is actually a pretty common requirement:
:)
Thanks for those examples. I have never had to do that myself, but it makes sense now that you mention it.
In many cases, the trickle of form submissions means a form can be manually closed off and the few extra posts can be managed personally.
But in cases where a wave of submissions are expected in a short period of time (ie, LAPD applications might reach 5000 submissions in 10 minutes) you really want to restrict the form from displaying to new visitors and manage people who already have the form open when they hit "submit". After the limit is reached it would be nice to show them an on-screen message of some kind (ie, "Sorry, the 5000 applications limit has been reached. Please try again next time").
A few minutes spent counting and checking totals could result in thousands of unwanted additional submissions appearing before you shut it down manually and lots of unhappy people.
Looking at your Submissions.cs file, you mention that the
FormSubmissionContexthas a boolean to prevent form submission, but looking here at the anonymous class you create, and the subsequent Submit method, there seems to be no way to halt the submission using this context.I understand the concept, but without some way of checking that a flag is changed (and having a flag to change) before the form is submitted, this will not prevent the form from submitting.
Thanks for any time, if you wish I can add a small bit of code change for your vetting.
Nope, I said that you can submit a pull request to create that functionality. It doesn't exist yet. Here is what I said for your reference:
If you would like to modify the core of Formulate, please submit an issue here explaining your plan: https://github.com/rhythmagency/formulate/issues
And then submit a pull request based off of the develop branch.
For anybody following this, The Fuel Agency submitted a pull request that has been merged in and released with the latest version of Formulate (2.2.0).
Here is the pull request for reference: https://github.com/rhythmagency/formulate/pull/131/files
You can now hook into the form submitting event and prevent submissions (e.g., if the maximum number of submissions has been reached).
is working on a reply...