The purpose of the Dynamic Forms module is to allow churches to quickly and easily create sign-up, registration, and payment forms. The drag-and-drop functionality will be based off of the [url removed, login to view] dynamic form builder. Please review that site thoroughly to get idea of how we want our form builder to function.
We are developing online and kiosk software for churches. View our website at [url removed, login to view] to get a better idea of what we do.
This is just one of many projects that we will be posting on this site. We are looking for a development company we can develop a long-term relationship with.
Here are the steps that will be involved in creating a form:
1. Form Creation
(Step 1 ï¿½ Payment)
The church will be able to create a confirmation that will be emailed to the user once the form is completed. The email should support all strings from the form elements (if they create a required field called ï¿½ageï¿½ they should be able to write %age% into the confirmation email form and have it insert whatever was entered into the form.) The [url removed, login to view] ï¿½Form Wizardï¿½ does an excellent job of this. They create a dropdown list of all elements currently on the page, and when you select one of the items, it automatically inserts it into the email.
(Step 1 ï¿½ Add fields)
The user will create the forms using an intuitive drag and drop interface.
ï¿½ They will be able to add: text, heading, textboxes, textarea, radio buttons, checkboxes, and dropdown lists.
ï¿½ Required ï¿½configurationï¿½ fields (for the church to fill out):
o Form name
o Email confirmation when form is completed? (Checkbox)
&#61607; Email (if checked) (default to email on file)
o Payment options
ï¿½ Churches will want to use the dynamic forms to create registration AND accept payment for camps, retreats, etcï¿½ The form creation page will need have a place where the user can enter a price for the form. This cause the form to take them to a payment page where they will be asked to enter their billing info as well as a Credit/Debit/Ach info (depending on what the church is setup to accept). If the form is filled out on the kiosk, then it would take them to a page asking if they wanted to pay with check or credit/debit.
o If check is selected, then they will be asked to enter their account, and routing number as well as name and address.
o If debit/credit is selected, then they will be asked to swipe their card.
(Steps 3-5 See Photoshop file)
2. Form Publishing
Once a form is created, the church will be able to publish it to their church website and to their ChurchLink kiosk.
There will be two different website integration methods:
1. The church will place a button on their website that will pop up a window with the form. This window will not display the address bar, which will make the user not realize it is on a different site. With this setup, there is no need for a page header and footer.
2. The church will embed the form into their website using an iframe.
If the church has an onsite system, they will need to specify how they want to link to the form.
Ideally, this plugin will link with the WYSIWYG interface editor. When a new form is created, the user will be able to drag-and-drop a button onto any page of the interface. They will be able to change the text of the button. I can foresee that a church might have multiple registrations and would want to be able to have a button on the main page that links to a ï¿½Registrations and Signupsï¿½ page where all forms are listed.
3. Data Collection
When a form is created, a table will be created in the church's database to store all data. The church will then be able to access this data from their admin panel. They need to be able to export the data to CSV and Excel.
Must use CSS for all page layout. The exact design of the dynamic form builder is likely to change, so it needs to be designed with that in mind. Code must be commented well.