Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

This use case is ideal for an RIA firm that wants a higher level of automation than the Quik! App provides but wants to keep the workflow simple. The focus of this case is on a single custodian, but it could be extended to multiple custodians.

Workflow Overview

The ideal scenario is as follows:

  1. From within the CRM, choose a client and then click on a button or link to initiate the forms workflow.

  2. Still within the CRM, a custom screen asks the user to pick a form bundle from Quik!.

    1. Configure the form bundle directly within the Quik! Customer Central website (https://qcc.quikforms.com/QFE/)

    2. Call the Form Group API to get the forms:

      1. API guide: Form Groups Services

      2. Swagger: https://websvcs.quikforms.com/rest/formgroups/v1000/swagger/index.html

      3. Method: Get FormGroups

    3. Display the list of form groups to the user

  3. The user clicks a button or link to generate the forms

    1. Call the Quik! authentication API (REST APIs)

    2. Pass the following info to the Quik! Forms Engine API (Execute HTML Quik! Forms Engine Services)

      1. FormGroupID = the form group the user selected

      2. Client Data Fields = all of the CRM fields for the selected client(s)

      3. Form Configuration Settings = all of the settings for e-sign, form viewer control, etc.

        1. https://efficienttech.atlassian.net/wiki/spaces/QAG/pages/96403457/Quik!+Forms+Engine+Property+List

        2. Configurations

    3. Receive the HTML form to display to the user

  4. Display the form to the user

  5. User completes the form and either prints or sends for e-signature (using the SIGN button in the form viewer).

  • No labels