Forum Discussion

Qrew Member

10 months ago

Questions & Checklist setup

I'm trying to create an app for product owners to go through the checklist with a set of questions before releasing the product. A Product form will have a checklist type and there will be a se...

ChayceDuncan
9 months ago
Predecessors don't necessarily have to have a start and end - those are useful if you picture a gantt but a predecessor is just a requirement that something else be done before you can start, thus it's independent of any specific date. If you use native QB predecessor fields then what they will do it provide a work date field that acts as the date that item is unlocked - which is a date but for your concerns you're just trying to make sure that prior items are done - which is just the presence of a date in that case. If you're choosing to use the key field approve - then same logic more or less applies - you don't need a date, you can instead just look at the status of your predecessor tasks to determine if you're able to commence.

Possibly - this would need a form entry though. In your question setup you could make a 'Sub Question Label' - that when you display it in your task you have a rich-text field display like the form label so it feels unique to each question and then have them provide an input.

Grid edit will most likely stray you further way from the subquestion component. Grid Edit is a fixed report of columns so you can't adjust the input or entry based on the question. I might suggest that you leverage buttons and the ability for OpenAsPopup and data-refresh so that your users click a question - answer it in a pop up and save - then close the window back down and refresh or open the next question. With the workflow you've described, Grid Edit will be a little too limiting unless you pare back the dynamic input style you've described.

------------------------------
Chayce Duncan
------------------------------

Qrew Member

Hi Chayce, Thank you so much for your response.

One question/sub question will be used in multiple checklist, hence I created a template table to show checklist and list of questions connected to it.

Predecessor setup needs a start date and end date right? Can you please explain more on how to set this logic using predecessor please
Let me explain this with an example: Question: Are you creating new app in QB? If yes then display Sub Question: Provide details about the new app. When a checklist with the above question is selected in the product table, I want the Sub questions to be displayed as well. Is it possible to display the sub question based on the Question's input?
User will be updating the answers in Grid edit format. I'm thinking to create a table specific to the Input types and choices, connect it back to the Questions table. Do you think that's a good solution or do you have any other recommendations?

Thanks for your time Chayce. Appreciate your help

------------------------------
Hemavathy Rajendran
------------------------------

ChayceDuncan

Qrew Captain

9 months ago

Predecessors don't necessarily have to have a start and end - those are useful if you picture a gantt but a predecessor is just a requirement that something else be done before you can start, thus it's independent of any specific date. If you use native QB predecessor fields then what they will do it provide a work date field that acts as the date that item is unlocked - which is a date but for your concerns you're just trying to make sure that prior items are done - which is just the presence of a date in that case. If you're choosing to use the key field approve - then same logic more or less applies - you don't need a date, you can instead just look at the status of your predecessor tasks to determine if you're able to commence.
Possibly - this would need a form entry though. In your question setup you could make a 'Sub Question Label' - that when you display it in your task you have a rich-text field display like the form label so it feels unique to each question and then have them provide an input.
Grid edit will most likely stray you further way from the subquestion component. Grid Edit is a fixed report of columns so you can't adjust the input or entry based on the question. I might suggest that you leverage buttons and the ability for OpenAsPopup and data-refresh so that your users click a question - answer it in a pop up and save - then close the window back down and refresh or open the next question. With the workflow you've described, Grid Edit will be a little too limiting unless you pare back the dynamic input style you've described.

------------------------------
Chayce Duncan
------------------------------

RH
Qrew Member
9 months ago
Hi chayce,

This is the given requirement for the app
Purpose of app: A product should go through a set of checklist before delivery/rollout

A new product should go through 1 standard checklist and 19 checklist(this count may vary depending on standard checklist answer)

Each checklist have a set of questions(total 400 to 500 questions in 19 checklist)

the answer for the above questions will be either text/text multiple choice/multi line/link/multi select

Depending on the user answer few sub questions might pop up

This 500 questions have phases associated to it(8 phases in total)

I was thinking about two approach. One is above method and

the other one is creating all the questions as a field in product table with respective answers field type and control the questions dependency using form rules. But the challenge I will have here is reporting.

Can you please share your recommendation for the same?

------------------------------
Hemavathy Rajendran
------------------------------
- ChayceDuncan
  Qrew Captain
  9 months ago
  The honest answer, be it a good or bad answer is whatever you personally feel like you can implement. I personally prefer creating the template model as you first described and then commonly I will build/code QB code pages to display it because it's too dynamic for Quickbase inputs and so I just build my own custom forms. However - if you're not confident in the template approach and it's easier to build out the fields for each question - it's also a very viable option and one that you can certainly build out with native forms and form rules. I'm not 100% sure if by bullet (2) you have 19 checklist each with 400-500 questions - so equating to roughly 10000 questions - if that is the case then you won't be able to do that with fields. That's simply too many fields for one table to manage and you should lean to the template approach.
  
  You might consider reaching out to a Quickbase partner or Quickbase support to potentially blueprint and architect this with you and help provide development support where needed. I'm happy to discuss more if want to take it offline as well.
  
  ------------------------------
  Chayce Duncan
  ------------------------------
  - RH
    Qrew Member
    9 months ago
    Thank you for your response!
    
    ------------------------------
    Hemavathy Rajendran
    ------------------------------