2018 Webinar Series: Form Building with Zerion Software
2018 Webinar Series
Welcome to iFormBuilder, the mobile data collection platform that empowers you to collect better data anywhere. Building forms is both science and art, merging the principles of data integrity with the understanding of real-world challenges.
In this monthly webinar series, learn from the best as our Customer Success Team builds user-submitted forms. We're here to answer questions and educate you on the platform's capabilities.
How Do I Participate?
- Register for the webinar each month. Select the episode and fill in your contact information.
- Add to the pool of forms. Reply to this thread with a link to your form and a description of how it is completed.
- Ask questions. Reply to this thread and share your challenges with the community. We're here to help!
List of Broadcasts
Click here to register for a future broadcast
- February 13 Gravity Line Manhole Inspection: Form Package URL | Webinar Recording
- March 13 - Asset Registration Tracking: Form Package URL | Webinar Recording
- April 10 - Employee Timesheet: Form Package URL | Webinar Recording
- May 8 - Crop Trial ERD: Webinar Recording
- June 12 - GDPR Patient Intake: Form Package URL | Webinar Recording
- July 10 - International Registration: Form Package URL | Webinar Recording | Starter Form Package
- August 14 - Participant Check-In: Form Package URL | Webinar Recording
- September 11 - Form Package URL | Webinar Recording
- December 4 - Webinar Recording
-
Hi, Jon. This sounds like it should be a lot of fun. Just a couple of questions so everyone is clear:
- Do you have a preference of what kind of file to include?
- What if people can't make that time? Will there be a recording?
- Is this just for our current customers or can anyone submit a form?
-
Joe,
- PDF or Word doc is going to be best. Most important thing is that it's readable.
- Recordings will be made available on the Zerion Software website and as a link at the top of this thread.
- Anybody can participate! In fact, if you're considering iFormBuilder as a potential solution, then seeing one of the Customer Success team members working on the form will help you make an informed decision.
-
Thanks to all who participated in February's webinar. I wanted to highlight some of the great questions that were asked and post the answers for all to learn.
- What is the difference between a double equal sign and a triple equal sign? This question can get really technical really fast. In JavaScript, the underlying language used by iFormBuilder, a double equal sign compares the value of two operands while a triple equal sign compares the value as well as the data type. In terms of iFormBuilder, what this means is that comparing a Number element and Text element with the same input would evaluate to true with a double equal sign and false with a triple equal sign. For more detail check out this article: JavaScript — Double Equals vs. Triple Equals
-
Can a Key Value have a space instead of an underscore? The short answer is yes; however, this is a hotly contested question because we recommend keeping your key values database-friendly. There are both functional limitations as well as technical limitations. The key value is not a database column name it is not required to be database-friendly. On the other hand, Multi-Select elements display as a comma-separated list so including a comma would be a valid entry in the database, but functionally break certain displays.
My recommendation is to avoid symbols, but that you can use spaces freely. Just be sure your key values don't have leading or trailing white space because it will make doing comparisons very difficult.
Remember, the recordings will always be listed in the original post.
-
Beth that's a great question. The challenge is focused on what are called "Floating Point" Numbers. A quick google search will give you a lot of information, most of it overly technical. The main takeaway is that exact decimals cannot be stored in binary. So if I want to save the number 1.1, the computer is actually saving an expression that evaluates to 1.1 and sometimes this causes inconsistencies. It's a binary issue, wish I could change it.
To overcome this, we use text elements for numbers with decimals to ensure the EXACT value entered is stored. A couple tips around using Text for decimals.
- Switch the keyboard to number or number w/ punctuation
- Use Number() if you want to round with .toFixed(x)
- Careful when you try to add two text numbers because the plus sign has two purposes: addition and concatenation
Thanks for sharing the question, it's really helpful to talk through them there so others can see and refer back in the future.
Please sign in to leave a comment.
Comments
6 comments