Epicollect5 User Guide
  • What is Epicollect5
  • About
    • Projects and Entries Syncing
    • Our Community
    • Privacy Policy
    • Cookie Policy
    • News & Papers
    • Epicollect5 Citation
  • Web Application
    • Intro
    • Create a Project
    • Project Info & Privacy
    • Delete Projects (Web)
    • View Projects
    • Search Projects
    • Viewing Entries
    • Print Entries
    • Add & Edit Entries
    • Manage Entries
      • Entries Limits
      • Entries Bulk Deletion
      • Entries Bulk Uploads
      • Entries Ownership & Metadata
    • Manage Users
    • Transfer Ownership
    • Manage Entries
    • Data Mapping
    • Downloading Data
    • Downloading Media
    • Metadata
    • Clone Project
    • Rename Projects
    • Import & Export Projects
    • Web Link to Add Entries
  • Formbuilder
    • Intro
    • Languages and Translations
    • Question Types
    • Add Questions
    • Edit Questions
    • Linking Forms
    • Rename Forms
    • Print Forms
    • Remove Forms
    • Search
    • Jumps (If-Else)
    • Branches
    • Groups
    • Title
    • Uniqueness
    • Double-entry Verification
    • Import & Export Forms
    • Import & Export Possible Answers
    • Edit Possible Answers
  • Mobile Application
    • Intro
    • Platforms and Media
    • Mobile App Authentication
    • Mobile App Permissions
    • Add Projects
    • Add Entries (Single Form)
    • Add Entries (Multiple Forms)
    • Edit Entries
    • Re-use answers
    • Save & Resume Entries
    • Upload Entries
      • Upload Errors
      • Incomplete Entries
      • Missing required aswers
      • Unsync entries
    • Entries Limits
    • Download Entries
    • Delete Entries
    • Delete Projects (App)
    • Location Questions
    • Add Bookmarks
    • Project Info
    • Share Media Files
    • Adjust Font Size
    • Filter Entries
    • Beta updates (Android)
    • Xiaomi Troubleshooting
  • Developers
    • Intro
    • API
    • Apps
  • Integrations
    • Google Maps
    • Google Earth
    • Microreact
    • Survey Toolkit
    • Google Sheets
  • Common Use Cases
    • Matrix Style Questions
    • Consolidate data
    • Jumps 101
    • Other, Please Specify
    • Non-Hierarchical Forms
    • Users Working Groups
    • Excel and UTF-8
    • Excel All Data in One Cell
    • Barcodes
    • Child Forms vs Branches
    • Dependent Dropdowns
    • Referencing Parent Form Responses
  • Extra
    • Useful Links
    • Demo Projects
    • FAQ
    • How-to Videos
    • Known Issues
Powered by GitBook
On this page
  1. Common Use Cases

Jumps 101

Example Implementation of Jumps in the Epicollect5 Platform

PreviousConsolidate dataNextOther, Please Specify

Last updated 4 months ago

We created a playground project called for anyone to explore and experiment with jumps logic. The form structure is straightforward, asking for a person’s Name and Sex. We designed the form to display a different follow-up question based on the selected sex or skip follow-ups entirely if the user prefers not to disclose that information.

Form Setup Details:

  • The Sex question is set as required, ensuring users cannot skip it.

  • Available answers: MALE, FEMALE, PREFER NOT TO ANSWER.

Jump Logic Configuration:

  1. If the user selects MALE:

    • No jump is needed because the next question is already the MALE-only follow-up question.

  2. If the user selects FEMALE:

    • We add a jump to the FEMALE-only follow-up question, effectively skipping the MALE-only follow-up question, which should not be asked to female users.

  3. If the user selects PREFER NOT TO ANSWER:

    • We add a jump directly to the End of the Form, as no further questions are needed.

Resolving a Logical Flow Issue:

We noticed a small issue in the form flow:

  • After selecting MALE and answering the MALE-only follow-up question, the user was still presented with the FEMALE-only follow-up question, which was unintended due to the standard form flow.

Solution:

To fix this, we added a jump on the MALE-only follow-up question to always jump to the End of the Form after it is answered. This adjustment skips the FEMALE-only follow-up question, ensuring the intended logic flow.

Final Outcome:

With this correction, the form now follows the proper logic, asking only relevant questions based on the user’s input while skipping unnecessary ones. This streamlined experience improves data collection accuracy and enhances user experience.

EC5 Jumps 101