Cascading Search (Productivity Kit)

Provides a systematic way to access data, making it easier for users to navigate through large datasets and locate specific information efficiently. 

This workflow uses a configurable schema to dynamically generate a form and have a cascading set of fields that query one layer.

It supports strings and numbers, and the form can contain drop-down lists and auto-complete fields. If the field is a domain field, it is recognised automatically.

Requirements

• VertiGIS Studio Productivity Kit with active service subscription

• Activity Pack Deployment
  The deployment of Activity Packs is described in this section.

   

Inputs

1. schema: object array

   The schema for the form. The following properties are included:

   1. layer: string

      The name of the layer to be buffered. If not found the model uri of the layer to be queried. (ex. "layer": "0b7c62a2-2bdd-46e2-b82a-9e6bbaa749c9"). Feature Layers and Map Image Layers are supported.

   2. fields: object array

      An array of definitions for each field. The following properties are included:

      1. hierarchy: number

         Order of the cascading search. Must start at 0 and must increment by one for every field. The workflow will not work properly if hierarchy is not configured correctly.

      2. id: string

         Field name in the layer.

      3. title: string

         Label for the field in the workflow.

      4. autoComplete: boolean

         Indicates if it's an autocomplete (true) or a dropdown (false). Auto-Complete uses the language resource @defaultPromptText for the prompt.

      5. minLength: number

         The amount of characters for an autocomplete to start suggestions. Defaults to 3.

      6. type: string

         Type of the field in the ArcGIS layer - Currently "string" and "number" are supported.

      7. required: boolean 

         Indicates if the field is required to have a value for the workflow to finish. If a field is required, all parents above must also be required. If a field is not required, any children will ignore this configuration and will not be required.

Behaviour

1. The form is dynamically populated for each field. They each have a "change" event dynamically added.
2. Whenever a selection changes on a list, the next descendant will be activated and filled automatically.
3. If parents of an already selected field is changed, all children will be reset.
4. After click into Search the corresponding query will be triggered.

Configuration Example

1. Configuration Example with Layer ID:
   
   
    

2. Configuration Example with Domain Values: