Forum Discussion

hheckert's avatar
hheckert
Qrew Trainee
3 months ago

Best way to have a repository of pre-configured options but also allow users to add/edit

I am building an application that will be used to house business requirements for various outbound call campaigns. One of the aspects of the campaign is a questionnaire that needs to be filled out by the user post-call with the member. Most of the campaigns use the same question/response combinations but there may be times where a response option may change. What is the best way to allow users to choose from pre-configured question/response values (based on historical requirements) but also have the ability to request a change for their purpose?

5 Replies

  • When I have done these type of surveys in the past, I have a parent child relationship. One Campaign has many Campaign Questionnaires, and one Campaign Questionnaire  has many Questionnaire Questions.   When the Campaign is set up, presumably you know the type of Questions which need to be asked.  So that selection would flow down to the Campaign Questionnaire.

    Then there will be a table of Standard Questions.

    Then when the Campaign Questionnaire is created a Pipeline would fire to search for Standard Questions which are tagged in say a multi select field that include the type needed by the Campaign.   The the result of that search would either be created in a for each loop, or more effiently with a bulk upsert (if there are going to be a lot of questions, say like more than 20 ish) or else try out the new Import to Quickbase step which should be perfect for this situation.

    Now this presumes that the format of the questions is always the same, for example, a question and then a free form text box. If you have other question types, which have a yes/no answer or some kind of rating answer then what I have done in the past is to have say three question types and then that would be selected on the standard question as to what question type it is and then when they're imported across as questionnaire questions, form rules will show and hide the appropriate fields.

     Feel free to post back if you have any questions. 

  • Well, the best design would be to have a table with a list of standard campaign questions, possibly group with tags in a multi select field.

    Then, when you create a survey record either by a pipeline or an a button push, you could import the standard survey questions into the particular survey you just initiated. That way you can control which questions are associated with a survey and they could be selected from a library of Choices.

     

    • hheckert's avatar
      hheckert
      Qrew Trainee

      I am ok with creating a table to house question and/or response options but i dont want the users to have to create a child record per question, ideally I am looking to have

      • One form to capture up to 25 questions
      • Question + response options managed together on that form
      • Users can see existing (standard) options for a question
      • Users can change/add/remove options if needed without requesting a change
      • DonLarson's avatar
        DonLarson
        Qrew Deputy

        The Users would only have to create child records for the unique or custom questions.  A Pipeline should auto build the records from the Standard table to the questionnaire table for the particular campaign.   I have used the technique Mark has described for multiple business cases.

  • .... you can also have a standard question come into the child record and then a form rule fire to copy to an editable text field