For each record (type of job) related Checklist records can be generated automatically by the Record Change Trigger. Such Checklist records are displayed as related details. The example database (https://www.teamdesk.net/inspection_checklist) only makes use of a single list of items. We have different types of jobs -- each with a different checklist. So, I have the following questions:
1) What would be the "ideal" way to add Checklist records based on the type of job? 2) What if the type of job changes after the Checklist records are created/added? Is there a function/workflow trigger we can utilize that will delete the existing Checklist records and add new Checklist records based on the new type of job? 3) Would it be recommended if we added checklist fields in the master table and make the appearance/validation dependent on the type of job selected? That way, we won't have to deal with a separate table but it will limit our options of adding more data for each Checklist item (which I am fine with). It gives more control over the Checklist items though.