> ## Documentation Index
> Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Advanced Condition Builder — Integration

> Feature ID: FW-17 Status: ✅ Complete Spec: FW-17-advanced-condition-builder.md Last Updated: 2026-03-17

**Feature ID:** FW-17\
**Status:** ✅ Complete\
**Spec:** [FW-17-advanced-condition-builder.md](../../../specs/fw/archive/FW-17-advanced-condition-builder.md)\
**Last Updated:** 2026-03-17

***

## Overview

FW-17 provides a two-pane Advanced Condition Builder UI for workflow designers: attribute browser (left) and condition configuration (right). It integrates with PF-17 for entity field discovery and with FW-16 for event-payload condition attributes.

***

## Integration Points (from Spec)

| Dependency                         | Pattern        | Purpose                                                                                           |
| ---------------------------------- | -------------- | ------------------------------------------------------------------------------------------------- |
| PF-17 (Entity Field Configuration) | Platform Layer | Attribute discovery via `useEntityFields()`; organization-scoped field visibility.                |
| FW-16 (Event-Based Triggers)       | Intra-core     | Event payload fields exposed as condition attributes when building conditions for event triggers. |

***

## Platform Integration (FW-17 → PF-17)

* **Location:** [PLATFORM\_INTEGRATION\_LAYERS.md](./PLATFORM_INTEGRATION_LAYERS.md#fw-17--pf-17-condition-builder-field-discovery)
* **Hook:** `useConditionAttributes` (or PF-17 `useEntityFields` via platform field-config layer)
* **Behavior:** Map PF-17 field config to FW-17 `EntityAttribute`; merge standard fields; respect visibility and picklists.

***

## Event / Context Integration (FW-17 ↔ FW-16)

* When the condition builder is used in an event-trigger context, event payload fields are available as selectable attributes.
* No new event contracts; consumes existing FW-16 event payload schemas.

***

## Security and Tenant Isolation

* Attribute visibility and field references are organization-scoped via PF-17 and workflow context.
* No dedicated RLS tables for FW-17; condition config is stored in existing workflow definition JSON.

***

## Related Docs

* [CROSS\_CORE\_INTEGRATIONS.md](./CROSS_CORE_INTEGRATIONS.md)
* [PLATFORM\_INTEGRATION\_LAYERS.md](./PLATFORM_INTEGRATION_LAYERS.md#fw-17--pf-17-condition-builder-field-discovery)
* [FW-17 Spec](../../../specs/fw/archive/FW-17-advanced-condition-builder.md)