Technical Kick-off Guide

Typically, when a new customer is beginning a Quik! implementation, the Quik! onboarding team will walk through the following items with the customer's development team. Information and helpful links are provided for customer reference.

Agenda:

1. Review customer goals, ideal workflow, and any available design specs.

2. Understand Quik! architecture

   Open

   

    

3. Review core setup components.

   1. Finding forms

   2. Client Prefill

   3. Generating forms

4. Review Quik! Field Definition

   1. Text fields: Consist of instance # (1) parent field (Owner) & base field (FName) (complete field example: 1own.FName)

      1. When mapping, create a translation table that relates Quik! base field name to your field name

      2. When prefilling, query the translation table and prepend the Quik! parent field to the base field. Loop through all records and supply to Quik! via AddFieldToForm or LoadXML with a "shotgun approach" (i.e., send all the data you have for a client, and the data will prefill what is asked for on the form, and the rest will be ignored).

   2. Checkboxes: Consist of field name (1acc.RegType) & export value (52 for Roth IRA)

      1. When mapping, create translation table that relates Quik! base field name to your field name, as well as Quik! export value to your options

      2. When prefilling, query translation tables and prepend Quik! parent field to base field, loop through all records, and supply with export value to Quik! via AddFieldToForm or LoadXML with a "shotgun approach" (i.e., send all data you have for a client, and the data will prefill what is asked for on the form, and the rest will be ignored).

   3. Calculated Fields: When forms ask for combined field (example: 1own.FullName)

      1. When mapping, fields should be mapped individually as above (for 1own.FullName, map FName & LName)

      2. When prefilling, provide Quik! individual fields as above, then let Quik! combine automatically

   4. Generic Fields: When building automation around the Quik! forms, you can safely rely on fields named according to the Quik! Field Definition, but not randomly named generic fields.

      • If a non-Quik! (Generic) field is used for automation purposes, the field name may change without notice the next time the form is built.

        • What is a “Generic” field name? - When a field on a form does not match a field defined in the Quik! Field Definition: the field is given a random field name with a prefix

5. Review Quik! Form Enterprise Manager

   1. How to subscribe to forms

   2. How to create Form Groups

   3. Field Rules, E-Signature

6. Determine if there is a need to create child accounts under your account.

7. Provide any further questions to Quik! onboarding team.