[ENGCE-57552] feat(uipath-maestro-flow): array filter + mandatory-filter guidance

[baishalighosh]

Jira: ENGCE-57552 — [Skills][CLI] Add support for array filter in trigger
RCA: ENGCE-57498 — Gmail Email Received trigger returns 400 on Debug (Confluence)

Summary

Aligns the uipath-maestro-flow > connector-trigger skill with the matching CLI fix in uipcli #1823 so agents stop authoring freeform filter leaves for connector-mandated event parameters (the original ENGCE-57498 / Gmail folder filter footgun).

Before
No mandatory filters

Eval coverage

• New tests/tasks/uipath-maestro-flow/connector_trigger/trigger_with_array_filter.yaml — Gmail INBOX scenario with a freeform "subject contains invoice" leaf. Asserts:
  • eventParameters.folder === "INBOX" (mandatory source lives here, not in filter).
  • filter tree exists for the user's subject leaf, no top-level filterExpression.
  • Freeform tree does NOT contain a folder / ParentFolders leaf id (regression guard for the original 400).
• Renames the existing connector_trigger eval suite from tests/tasks/uipath-maestro-flow/nodes/connector_trigger/ to the flatter tests/tasks/uipath-maestro-flow/connector_trigger/ so both filter tests live alongside each other.

Architecture context

When the maestro-flow skill configures a Gmail trigger, the CLI call is:

uip maestro flow node configure <flow> <nodeId> --detail '{
  "connectionId": "...", "folderKey": "...", "eventMode": "polling",
  "eventParameters": { "folder": "INBOX" },
  "filter": { ... }
}'

In Studio Web, ConnectorTriggerViewModel.update() calls _setMandatoryFilterExpression() on every input-field property change and persists the result on TriggerActivityConfiguration.mandatoryFilterExpression. The translator at connector-translator-utils.ts:152 (post SW PR #18040) reads triggerConfig.combinedFilterExpression — a getter that AND-joins user filterExpression + persisted mandatoryFilterExpression. The CLI's uipcli #1823 ports this contract end-to-end (defects 1-3 fixed; defect 4 — wiring mandatory-filter-builder.ts into flow-tool and case-tool to actually compute and persist the value — is the follow-up).

This skill PR ensures agents stop emitting the wrong shape (mandatory field as a freeform leaf) ahead of the CLI defect-4 fix landing, and gains the array-filter coverage the original RCA called out.

Depends on

• uipcli #1823 — CLI defects 1-3 + defect-4 prep. Merge this skills PR only after uipcli #1823 lands and a release is published, otherwise the skill will instruct agents to use a CLI behavior their installed version does not yet support.

Test plan

• tests/tasks/uipath-maestro-flow/connector_trigger/trigger_with_filter.yaml — existing Outlook subject+from filter eval still passes against the renamed path
• tests/tasks/uipath-maestro-flow/connector_trigger/trigger_with_array_filter.yaml — new Gmail INBOX + subject filter eval passes locally
• Spot-check the updated impl.md renders cleanly in the skill viewer

References

• StudioWeb PR #18007 — array projection (defect 1)
• StudioWeb PR #18040 — scalar quoting + sanitized-id lookup + translator wiring (defects 2-3, SW-28437, SW-28497)
• PO.Frontend PR #5206 — Maestro side of defect 4

[github-actions]

PR Review: ENGCE-57552 array filter + mandatory-filter guidance

• Read review criteria and project conventions
• Read full diff and existing PR comments
• Read each changed file in full context
• Verify relative links resolve
• Check for cross-skill references, secrets, CODEOWNERS
• Verify test task structure and tags
• Post review

View job run