...
- Review customer goals, ideal workflow, any available design specs
- Understand Quik! architecture
- Review core setup components
- Finding forms
- Client Prefill
- Generating forms
- Review Quik! Field Definition
- Text fields: Consist of instance # (1) parent field (Owner) & base field (FName) (complete field example: 1own.FName)
- When mapping, create a translation table that relates Quik! base field name to your field name
- When prefilling, query translation table and prepend Quik! parent field to base field, loop through all records, supply to Quik! via AddFieldToForm or LoadXML with "shotgun approach"
- Checkboxes: Consist of field name (1acc.RegType) & export value (52 for Roth IRA)
- When mapping, create translation table that relates Quik! base field name to your field name, as well as Quik! export value to your options
- When prefilling, query translation tables and prepend Quik! parent field to base field, loop through all records, supply with export value to Quik! via AddFieldToForm or LoadXML with "shotgun approach"
- Calculated Fields: When forms ask for combined field (example: 1own.FullName)
- When mapping, fields should be mapped individually as above (for 1own.FullName, just map FName & LName)
- When prefilling, provide Quik! individual fields as above then let Quik! combine automatically
- Text fields: Consist of instance # (1) parent field (Owner) & base field (FName) (complete field example: 1own.FName)
- Review Quik! Form Enterprise Manager
- How to subscribe to forms
- How to create Form Groups
- Field Rules, E-Signature
- Determine if there is a need to create child accounts under your account
- Provide any further questions to Quik! onboarding team