Page Comparison

...

• AO_4025C4_CONFIGURATION_DAO

  • App configuration data. You don't have to migrate this, you can just use the Easy Forms admin tool to setup configuration on your new instance

    • CREATED

      • timestamp

    • DESCRIPTOR

      • JSON descriptor like

        Code Block
        {"notifyWorkboxEditors":true,"notifyWorkboxUsers":false,"notifyWorkboxUsersList":"","notifyEmailIncludeData":false,"notifyEmailEditors":false,"notifyEmailUsers":false,"notifyEmailUsersList":"","notifyHipChatServer":"api.hipchat.com","notifyHipChatRoomToken":"","notifyWebhookUrl":""}

    • ID

      • PK id

    • UPDATED

      • timestamp

• AO_4025C4_FORM

  • Defines forms (not submitted form data)

  • CREATED_BY, UPDATED_BY contain user keys that may need to be transformed

  • PAGE_ID contains page IDs that may need to be transformed

    • CREATED

      • timestamp

    • CREATED_BY

      • user key

    • DESCRIPTOR

      • JSON descriptor like

        Code Block
        {"fields":[{"label":"Between 1 and 10 (inclusive)", "field_type":"number", "required":true, "field_options":...

      • FIELD_ORDER

        • ids of FORM_FIELD rows, comma separated, in order

      • HIP_CHAT_ROOM_TOKEN

      • ID

        • PK id

      • NAME

      • PAGE_ID

      • REPORTS _UNRESTRICTED

      • TITLE

      • UPDATED

        • timestamp

      • UPDATED_BY

        • user key

• AO_4025C4_FORM_FIELD

  • Defines fields in forms, FK to the form table (not submitted form data)

    • CID

      • client ID

    • CREATED

      • timestamp

    • DELETED

      • TRUE if deleted

    • FIELD_OPTIONS

      • JSON data like

        Code Block
        {"min":"1", "max":"10", "description":"", "integer_only":false}

    • FORM_ID

      • FK id of parent form

    • ID

      • PK id

    • LABEL

    • PLUGIN_VERSION

    • REQUIRED

    • TYPE

      • number, text, etc.

    • UID

    • UPDATED

      • timestamp

• AO_4025C4_SUBMISSION

  • User submissions for the forms

    • This table has a single row for each submission, used to identify/ID the submission values and associate them with a user

    • The individual values in the submission are in the submission field table (see below)

  • USER_KEY contain user keys that may need to be transformed

  • Data migration is only necessary if you want to preserve old submissions

    • ANONYMOUS_USER_KEY

      • hashed user ID, used for anonymous forms.

    • CREATED

      • timestamp

    • FORM_ID

      • FK id of parent form

    • ID

      • PK id

    • PLUGIN_VERSION

      • version of the Easy Forms plugin used for this submission

    • UPDATED

      • timestamp

    • USER_KEY

• AO_4025C4_SUBMISSSION_FIELD

  • User submissions submission values for all of the fields on the formsa form, one row for each field, FK to the submission table

    • CREATED

      • timestamp

    • FORM_ID

      • FK id of parent form

    • ID

      • PK id

    • NAME

      • input field name

    • SHORT_VALUE

      • the first 255 chars of the value, used for search filtering

    • SUBMISSION_ID

      • FK id of the parent submission

    • UID

      • input field UID

    • UPDATED

      • timestamp

    • VALUE

      • the CLOB value containing the entire value, used when the value is > 255 chars

Transforming User Keys

A username is unique on an instance. A username will be the same user on your source and destination but, depending on how you migrated your data from source to destination, your user keys that are mapped to those usernames may not be equal. The user keys might be different on your destination. 

...