Properties

Use to find objects in data store, e.g. Active Directory. It performs searches using pipes and stores a selected value for next steps to consume.

Properties

Name	Desciption	Default value	Mandatory
type	Must be Selector	N/A
pipe_id	Id of pipe searching for objects	Same as control id
columns	What columns to be displayed in UI.	N/A
submit_on_change	Should selection of an item move to next step. true/false	true
search	Should user be able to enter custom search data.	false
ui	Extra ui configuration, see below

Example

{
  "id": "contactSelector",
  "control": "Selector",
  "config": {
    "required": true,
    "readonly": false,
    "pipe_id": "contacts_pipe",
    "columns": ["name", "email", "phone", "date_of_birth"],
    "search": true,
    "submit_on_change": true,
    "identifier": "id",
    "required_property": "name",
    "remove_empty_items": true
  },
  "ui": {
    "ui:sort_priority": ["email", "name", "phone", "date_of_birth"]
  }
}

Searching for object to show

To populate list of items in UI a pipe must be executed. List of items returned should at least contain properties defined in columns.

Data sent to pipe is:

• search - containing user input if config -> search is set to true

• columns - comma separated string of defined columns

Return data must be in a form of a list of items.

Data exposed to flow

When pressing Select, data exposed to flow is found using key if control id. Value is item id returned from pipe

Ui

For row ordering according to columns use the following type of configuration. In this example the rows will be sorted first by email, then name, phone and lastly date_of_birth. You can also see the configuration example in the example above in the properties table examples.

"ui": {
    "ui:sort_priority": ["email", "name", "phone", "date_of_birth"]
}