Pipes and flows

Management Center provides structured editors for common pipe and flow settings. These views keep routine changes out of raw JSON while preserving the underlying configuration format.

LDAP attribute and property editors

LDAPSearch, LDAPAdd, and LDAPModify use a tag-style editor where attributes or properties can be added, edited, and removed individually. The UI writes the resulting value as a comma-separated string.

Attributes

{
  "attributes": "sAMAccountName,memberOf,objectGUID;binary"
}

Modify properties

{
  "add": "mail,mobile",
  "replace": "displayName",
  "delete": "obsoleteAttribute"
}

For LDAPSearch, mark an attribute as binary to append ;binary to its name. The previous multivalue option is not available in the new editor and is not written when the value is saved.

Caution

The editor can read legacy array-based values for migration, but it writes only the comma-separated format. Review a legacy value before saving because obsolete properties such as multivalue are intentionally dropped.

LDAPSearch result limit

Use Max results in the LDAPSearch editor to limit how many LDAP entries a search can return. The value is stored as the positive integer config.max_results and defaults to 1000 when no explicit value is provided.

{
  "max_results": 1000
}

max_results limits the number of returned entries. It does not replace expected_item_count, which validates how many results the search is expected to produce.

Pipe metrics

Open a pipe and select Metrics to switch from configuration to runtime metrics. The button behaves as a toggle like the other pipe view controls; select it again to return. Valve rows use the configured display name when one is available.

SubPipe usage

A SubPipe has a Used by view that lists known references before you edit or delete it. Each row includes the referencing pipe, its location, and a deep link. In Access, the related authenticator is shown when Management Center can resolve it.

The view scans normal pipes, SubPipes, Access authenticators, and Flow or Flow-step configuration. Control pipes owned by Schedules or API Endpoints are not currently scanned, so absence from the list is not a guarantee that those object types do not reference the SubPipe.

Flow visibility in Launchpad

Use Hide in Launchpad on the Flow General tab to control the hide_in_launchpad property without editing JSON.

Hiding a Flow removes it from Launchpad navigation. It does not disable the Flow, and the Flow remains reachable through its direct URL.