General Discussion

Hi Moritz,

Understanding your form is already built, are the sections you have the questions grouped in, broken down by which Maintenance Type they apply to?

IE:
Sections 1 to 5 are for Light
Sections 6 to 10 are for Medium
etc, etc.

If so, you could use the Is Ignored/Is Not Ignored conditional logic actions to hide entire sections depending on the Maintenance Type selected.
This will allow you to show/hide groups of questions based on the section they are in. This also applies to Pages if you want to go even broader.

I have attached an MS Excel 'Form Export' of the demo I created to test this so you see how the demo form was constructed.

The documentation that talks to Is Ignored/Is Not Ignored is here and will provide you with more details: (Scroll down to the 'Actions' section)
https://docs.prontoforms.com/1374411/Content/Published/218858037.html    

Hi Stu,

the maintenance activities for "light", "medium" and " full can unfortnuately not be put in one section each since a suitable sequence of the maintenance activities has priority. 

Do you have any other suggestions?

br

Moritz

Hi Moritz,

Understanding your form is already built, are the sections you have the questions grouped in, broken down by which Maintenance Type they apply to?

IE:
Sections 1 to 5 are for Light
Sections 6 to 10 are for Medium
etc, etc.

If so, you could use the Is Ignored/Is Not Ignored conditional logic actions to hide entire sections depending on the Maintenance Type selected.
This will allow you to show/hide groups of questions based on the section they are in. This also applies to Pages if you want to go even broader.

I have attached an MS Excel 'Form Export' of the demo I created to test this so you see how the demo form was constructed.

The documentation that talks to Is Ignored/Is Not Ignored is here and will provide you with more details: (Scroll down to the 'Actions' section)
https://docs.prontoforms.com/1374411/Content/Published/218858037.html    

Hi Moritz, 

Great question! As there are many ways to Rome I'm sure you'll get a few interesting takes on how to solve for this. Here are a few from my side:

(1) The current 1 form you have, but group all the questions into Sections, or Pages, and use Conditional Logic to hide/show the corresponding Page or Section, according to their choice in the dropdown. This will cut down on the number of Conditional Logic rules. 

(2) A simple option you may have already considered, to create entirely separate forms for each Light, Medium, and Full inspection. You can tag these forms so they're searchable in the mobile app. 

(3) This one is a little complex, bear with me.You start with 4 separate forms, and then you could then connect them using a Dispatch Data Destination. That's highlighted here. Form #1 is the main form where they fill out the details they will have no matter what, and then Form #2 is for Light, Form #3 is for Medium, Form #4 is the Full. Then, depending on the choices in Form #1, this dispatches to one of the other 3 forms, and you can have information populate over from Form #1 into Form #2, and so on.

You can also tag forms so that mobile users can pull up the forms directly if they need to. I made a lesson about Dispatch Data Destinations in the ProntoForms University, Level 3 training, which we're releasing this month. You could also accomplish this with a Customer Feedback Form (CFF), where Form #1 connects into Form #2, Form #3, Form #4. Then you could have the CFF be a barcode, so the mobile user arrives on site (as long as they have an internet connection), and scans the barcode which brings them to the CFF, then over to the Form #2, Form #3, Form #4 they need to continue working on. 

I trust these are helpful! Feel welcome to reach out in case I can offer any more insights. 

Warmly, 

Erika

------------------------------
Technical Content Developer
ProntoForms
------------------------------

Dear Erika,

(1) The current 1 form you have, but group all the questions into Sections, or Pages, and use Conditional Logic to hide/show the corresponding Page or Section, according to their choice in the dropdown. This will cut down on the number of Conditional Logic rules. 

As I said in my reply to Stu, this is not an option since a suitable sequence of the maintenance activities has priority.

(2) A simple option you may have already considered, to create entirely separate forms for each Light, Medium, and Full inspection. You can tag these forms so they're searchable in the mobile app. 

We want to keep a lean workflow to update our forms. Updating three forms including language dimensions in case of an additional task is not an option. We want to reuse our content as much as possible.

(3) This one is a little complex, bear with me.You start with 4 separate forms, and then you could then connect them using a Dispatch Data Destination. That's highlighted here. Form #1 is the main form where they fill out the details they will have no matter what, and then Form #2 is for Light, Form #3 is for Medium, Form #4 is the Full.

This is not an option due to the fact that a suitable sequence of the maintenance activities has priority. In addition, this option is quite difficult to maintain... 

Could you please add "conditional logic based on tags instead of specific questions" as a feature request?

br

Moritz

Hi Moritz, 

Great question! As there are many ways to Rome I'm sure you'll get a few interesting takes on how to solve for this. Here are a few from my side:

(1) The current 1 form you have, but group all the questions into Sections, or Pages, and use Conditional Logic to hide/show the corresponding Page or Section, according to their choice in the dropdown. This will cut down on the number of Conditional Logic rules. 

(2) A simple option you may have already considered, to create entirely separate forms for each Light, Medium, and Full inspection. You can tag these forms so they're searchable in the mobile app. 

(3) This one is a little complex, bear with me.You start with 4 separate forms, and then you could then connect them using a Dispatch Data Destination. That's highlighted here. Form #1 is the main form where they fill out the details they will have no matter what, and then Form #2 is for Light, Form #3 is for Medium, Form #4 is the Full. Then, depending on the choices in Form #1, this dispatches to one of the other 3 forms, and you can have information populate over from Form #1 into Form #2, and so on.

You can also tag forms so that mobile users can pull up the forms directly if they need to. I made a lesson about Dispatch Data Destinations in the ProntoForms University, Level 3 training, which we're releasing this month. You could also accomplish this with a Customer Feedback Form (CFF), where Form #1 connects into Form #2, Form #3, Form #4. Then you could have the CFF be a barcode, so the mobile user arrives on site (as long as they have an internet connection), and scans the barcode which brings them to the CFF, then over to the Form #2, Form #3, Form #4 they need to continue working on. 

I trust these are helpful! Feel welcome to reach out in case I can offer any more insights. 

Warmly, 

Erika

------------------------------
Technical Content Developer
ProntoForms

Hi Mortiz, I have logged a formal Feature Request with our Product team on your behalf and mentioned other customers have also ran into this scenario, based on this thread. Thank you very much for sharing this with us.

Dear Erika,

(1) The current 1 form you have, but group all the questions into Sections, or Pages, and use Conditional Logic to hide/show the corresponding Page or Section, according to their choice in the dropdown. This will cut down on the number of Conditional Logic rules. 

As I said in my reply to Stu, this is not an option since a suitable sequence of the maintenance activities has priority.

(2) A simple option you may have already considered, to create entirely separate forms for each Light, Medium, and Full inspection. You can tag these forms so they're searchable in the mobile app. 

We want to keep a lean workflow to update our forms. Updating three forms including language dimensions in case of an additional task is not an option. We want to reuse our content as much as possible.

(3) This one is a little complex, bear with me.You start with 4 separate forms, and then you could then connect them using a Dispatch Data Destination. That's highlighted here. Form #1 is the main form where they fill out the details they will have no matter what, and then Form #2 is for Light, Form #3 is for Medium, Form #4 is the Full.

This is not an option due to the fact that a suitable sequence of the maintenance activities has priority. In addition, this option is quite difficult to maintain... 

Could you please add "conditional logic based on tags instead of specific questions" as a feature request?

br

Moritz

Hi Moritz, 

Great question! As there are many ways to Rome I'm sure you'll get a few interesting takes on how to solve for this. Here are a few from my side:

(1) The current 1 form you have, but group all the questions into Sections, or Pages, and use Conditional Logic to hide/show the corresponding Page or Section, according to their choice in the dropdown. This will cut down on the number of Conditional Logic rules. 

(2) A simple option you may have already considered, to create entirely separate forms for each Light, Medium, and Full inspection. You can tag these forms so they're searchable in the mobile app. 

(3) This one is a little complex, bear with me.You start with 4 separate forms, and then you could then connect them using a Dispatch Data Destination. That's highlighted here. Form #1 is the main form where they fill out the details they will have no matter what, and then Form #2 is for Light, Form #3 is for Medium, Form #4 is the Full. Then, depending on the choices in Form #1, this dispatches to one of the other 3 forms, and you can have information populate over from Form #1 into Form #2, and so on.

You can also tag forms so that mobile users can pull up the forms directly if they need to. I made a lesson about Dispatch Data Destinations in the ProntoForms University, Level 3 training, which we're releasing this month. You could also accomplish this with a Customer Feedback Form (CFF), where Form #1 connects into Form #2, Form #3, Form #4. Then you could have the CFF be a barcode, so the mobile user arrives on site (as long as they have an internet connection), and scans the barcode which brings them to the CFF, then over to the Form #2, Form #3, Form #4 they need to continue working on. 

I trust these are helpful! Feel welcome to reach out in case I can offer any more insights. 

Warmly, 

Erika

------------------------------
Technical Content Developer
ProntoForms

Hi Moritz, 

Great question! As there are many ways to Rome I'm sure you'll get a few interesting takes on how to solve for this. Here are a few from my side:

(1) The current 1 form you have, but group all the questions into Sections, or Pages, and use Conditional Logic to hide/show the corresponding Page or Section, according to their choice in the dropdown. This will cut down on the number of Conditional Logic rules. 

(2) A simple option you may have already considered, to create entirely separate forms for each Light, Medium, and Full inspection. You can tag these forms so they're searchable in the mobile app. 

(3) This one is a little complex, bear with me.You start with 4 separate forms, and then you could then connect them using a Dispatch Data Destination. That's highlighted here. Form #1 is the main form where they fill out the details they will have no matter what, and then Form #2 is for Light, Form #3 is for Medium, Form #4 is the Full. Then, depending on the choices in Form #1, this dispatches to one of the other 3 forms, and you can have information populate over from Form #1 into Form #2, and so on.

You can also tag forms so that mobile users can pull up the forms directly if they need to. I made a lesson about Dispatch Data Destinations in the ProntoForms University, Level 3 training, which we're releasing this month. You could also accomplish this with a Customer Feedback Form (CFF), where Form #1 connects into Form #2, Form #3, Form #4. Then you could have the CFF be a barcode, so the mobile user arrives on site (as long as they have an internet connection), and scans the barcode which brings them to the CFF, then over to the Form #2, Form #3, Form #4 they need to continue working on. 

I trust these are helpful! Feel welcome to reach out in case I can offer any more insights. 

Warmly, 

Erika

------------------------------
Technical Content Developer
ProntoForms
------------------------------

Hi Moritz, 

Great question! As there are many ways to Rome I'm sure you'll get a few interesting takes on how to solve for this. Here are a few from my side:

(1) The current 1 form you have, but group all the questions into Sections, or Pages, and use Conditional Logic to hide/show the corresponding Page or Section, according to their choice in the dropdown. This will cut down on the number of Conditional Logic rules. 

(2) A simple option you may have already considered, to create entirely separate forms for each Light, Medium, and Full inspection. You can tag these forms so they're searchable in the mobile app. 

(3) This one is a little complex, bear with me.You start with 4 separate forms, and then you could then connect them using a Dispatch Data Destination. That's highlighted here. Form #1 is the main form where they fill out the details they will have no matter what, and then Form #2 is for Light, Form #3 is for Medium, Form #4 is the Full. Then, depending on the choices in Form #1, this dispatches to one of the other 3 forms, and you can have information populate over from Form #1 into Form #2, and so on.

You can also tag forms so that mobile users can pull up the forms directly if they need to. I made a lesson about Dispatch Data Destinations in the ProntoForms University, Level 3 training, which we're releasing this month. You could also accomplish this with a Customer Feedback Form (CFF), where Form #1 connects into Form #2, Form #3, Form #4. Then you could have the CFF be a barcode, so the mobile user arrives on site (as long as they have an internet connection), and scans the barcode which brings them to the CFF, then over to the Form #2, Form #3, Form #4 they need to continue working on. 

I trust these are helpful! Feel welcome to reach out in case I can offer any more insights. 

Warmly, 

Erika

------------------------------
Technical Content Developer
ProntoForms
------------------------------