feat(designer) - Show operation default setting values and host settings in the designer by JoaquimMalcampo · Pull Request #9253 · Azure/LogicAppsUX

JoaquimMalcampo · 2026-06-05T17:09:43Z

Commit Type

feature - New functionality
fix - Bug fix
refactor - Code restructuring without behavior change
perf - Performance improvement
docs - Documentation update
test - Test-related changes
chore - Maintenance/tooling

Risk Level

Low - Minor changes, limited scope
Medium - Moderate changes, some user impact
High - Major changes, significant user/system impact

What & Why

Adds UI visibility for operation setting defaults returned by the settingDefaults API. Previously, settings like retry policy showed "Default" with no detail fields when no explicit value was set in the workflow definition. Now the designer fetches defaults from the host and displays actual values (e.g., "Exponential interval", count, intervals) while preserving the existing serialization behavior — no changes are written to the workflow JSON.

Additionally, unknown host-level settings returned by the API (e.g., maxMessageBatchSize) are now surfaced in a new read-only "Host settings" section in the settings panel.

Changes

settingDefaults.ts - React Query cached fetch for the settingDefaults API endpoint. Applies merge logic for returned setting values and routes additional settings as hostSettings.
added defaultHint to SettingData and hostSettings map to Settings interface
serializer.ts - if defaultHint is present, does not serialize on retry
hostsettings.tsx - dynamic read only section that renders host settings as text fields and is included with the rest of the settings sections in index.tsx
operationmanifest.ts (standard/consumption/base) - add getSettingDefaults to operation manifest service interface and implementations.

Impact of Change

Users:
Settings panel now shows actual default values for retry policy and other settings instead of an opaque "Default" label. Host-level read-only settings (e.g., maxMessageBatchSize) are visible in a new collapsible section. No changes to saved workflow definitions.
Developers:
New defaultHint field on SettingData — indicates the value came from API defaults and should not be serialized. hostSettings on Settings is a dynamic Record<string, SettingData> for arbitrary host-returned keys. KNOWN_SETTING_KEYS set in settingDefaults.ts controls which API keys are treated as known vs host-level.
System:
One additional HTTP call per operation during deserialization (cached by React Query). No changes to workflow JSON serialization output.

Test Plan

Unit tests added/updated
E2E tests added/updated
Manual testing completed
Tested in: VS Code Extension Development Host with Standard Logic App (Service Bus completeQueueMessageV2 operation)

Contributors

Screenshots/Videos

github-actions · 2026-06-05T17:10:37Z

🤖 AI PR Validation Report

PR Review Results

Thank you for your submission! Here's detailed feedback on your PR title and body compliance:

✅ PR Title

Current: feat(designer) - Show operation default setting values and host settings in the designer
Issue: None blocking. The title is descriptive and identifies the affected area and outcome clearly.
Recommendation: No change required.

✅ Commit Type

Properly selected (feature).
Only one commit type is selected, which is correct.

✅ Risk Level

The selected risk level (Medium) is reasonable for the UI + serialization + backend call changes.
Advised risk is still medium based on the diff; no higher risk assignment is needed.

✅ What & Why

Current: Clear and specific explanation of the new setting defaults behavior and the new host settings section.
Issue: None blocking.
Recommendation: No change required.

✅ Impact of Change

Good coverage of users, developers, and system impact.
Recommendation:
- Users: Already clear.
- Developers: Already clear.
- System: Already clear.

✅ Test Plan

Test plan passes because unit tests were added/updated in the diff (retryPolicy.spec.ts and settingDefaults.spec.ts). Manual testing is also documented.
No issue found with the lack of E2E tests since unit tests are present.

⚠️ Contributors

No contributors listed.
Recommendation: If PMs, designers, or other engineers contributed ideas or validation, please tag them here for credit. This section is optional, so it does not block the PR.

✅ Screenshots/Videos

Visual evidence is included and appropriate for this UI change.
Recommendation: No change required.

Summary Table

Section	Status	Recommendation
Title	✅	No change required
Commit Type	✅	No change required
Risk Level	✅	No change required
What & Why	✅	No change required
Impact of Change	✅	No change required
Test Plan	✅	Unit tests are present; no further action needed
Contributors	⚠️	Optional, but add contributors if applicable
Screenshots/Videos	✅	No change required

Overall, this PR passes review. The advised risk level does not need to be increased beyond the submitter's Medium selection.

Last updated: Fri, 19 Jun 2026 16:28:17 GMT

Copilot

Pull request overview

This PR enhances the Designer settings panel to display concrete default operation setting values returned by the backend settingDefaults API (instead of an opaque “Default”), and surfaces unknown host-level settings in a new read-only “Host settings” section—while keeping workflow JSON serialization behavior unchanged.

Changes:

Add a React Query–cached settingDefaults fetch + merge path during operation initialization/deserialization.
Extend settings types (SettingData, Settings, SettingSectionName) to support read-only/default-hint semantics and host-level settings display.
Add a new Settings panel section to render host-level settings as read-only text fields.

Reviewed changes

Copilot reviewed 13 out of 13 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
Localize/lang/strings.json	Adds localization entry for the new “Host settings” section title.
libs/logic-apps-shared/src/designer-client-services/lib/operationmanifest.ts	Extends the operation manifest service interface with optional `getSettingDefaults`.
libs/logic-apps-shared/src/designer-client-services/lib/standard/operationmanifest.ts	Implements `getSettingDefaults` for Standard (including hybrid proxy path).
libs/logic-apps-shared/src/designer-client-services/lib/consumption/operationmanifest.ts	Implements `getSettingDefaults` for Consumption using the existing baseUrl/connectorId URL pattern.
libs/designer/src/lib/ui/settings/sections/hostsettings.tsx	New UI section that renders host-level settings as read-only fields.
libs/designer/src/lib/ui/settings/index.tsx	Wires the new Host Settings section into the Settings panel and centralizes `SettingSectionName`.
libs/designer/src/lib/core/state/setting/settingInterface.ts	Adds `HOSTSETTINGS` to the settings section name map.
libs/designer/src/lib/core/queries/settingDefaults.ts	Adds supported-settings key extraction, React Query fetch, and merge logic (including hostSettings routing).
libs/designer/src/lib/core/actions/bjsworkflow/settings.ts	Extends settings types to support `readOnly`, `defaultHint`, and `hostSettings`.
libs/designer/src/lib/core/actions/bjsworkflow/serializer.ts	Avoids serializing retry policy when it was populated from API defaults (via `defaultHint`).
libs/designer/src/lib/core/actions/bjsworkflow/operationdeserializer.ts	Fetches and merges setting defaults during manifest-based operation initialization.
libs/designer/src/lib/core/actions/bjsworkflow/add.ts	Fetches and merges setting defaults during operation creation/initialization flows.
libs/designer-v2/src/lib/core/actions/bjsworkflow/settings.ts	Adds `readOnly` to v2 `SettingData` to keep parity for read-only settings support.

github-actions · 2026-06-05T17:28:08Z

📊 Coverage Check

The following changed files need attention:

⚠️ libs/designer/src/lib/core/queries/settingDefaults.ts - 13% covered (needs improvement)
⚠️ libs/designer-v2/src/lib/ui/settings/sections/hostsettings.tsx - 17% covered (needs improvement)
⚠️ libs/designer/src/lib/ui/settings/sections/hostsettings.tsx - 17% covered (needs improvement)
⚠️ libs/designer-v2/src/lib/core/actions/bjsworkflow/operationdeserializer.ts - 17% covered (needs improvement)
⚠️ libs/designer-v2/src/lib/core/actions/bjsworkflow/serializer.ts - 37% covered (needs improvement)
⚠️ libs/designer-v2/src/lib/core/actions/bjsworkflow/settings.ts - 17% covered (needs improvement)
⚠️ libs/designer/src/lib/core/actions/bjsworkflow/add.ts - 5% covered (needs improvement)
⚠️ libs/designer/src/lib/core/actions/bjsworkflow/operationdeserializer.ts - 4% covered (needs improvement)
⚠️ libs/designer/src/lib/core/actions/bjsworkflow/serializer.ts - 16% covered (needs improvement)
⚠️ libs/designer/src/lib/core/actions/bjsworkflow/settings.ts - 17% covered (needs improvement)
⚠️ libs/logic-apps-shared/src/designer-client-services/lib/consumption/operationmanifest.ts - 75% covered (needs improvement)
⚠️ libs/logic-apps-shared/src/designer-client-services/lib/standard/operationmanifest.ts - 13% covered (needs improvement)

Please add tests for the uncovered files before merging.

…thub.com/Azure/LogicAppsUX into jmalcampo/nodeSettingDetailsEnhancements

andrew-eldridge · 2026-06-15T19:38:21Z

    );

    settings = addDefaultSecureSettings(settings, connector?.properties?.isSecureByDefault ?? false);
+    const swaggerDefaults = await fetchSettingDefaults(


mcpDefaults, manifestDefaults, and swaggerDefaults are fetched the same. Can these be combined earlier in the method?

andrew-eldridge · 2026-06-15T19:42:23Z

+import { getReactQueryClient } from '../ReactQueryProvider';
+import Constants from '../../common/constants';
+
+const KNOWN_SETTING_KEYS = new Set<string>([


how is the settings view usually updated with new settings? Is it possible that this list will fall out of sync if another setting is added elsewhere? If possible, we should be pulling these values from some source of truth rather than hardcoded here

andrew-eldridge · 2026-06-15T19:43:58Z

+  supportedSettings: string[],
+  workflowKind?: string
+): Promise<Record<string, any> | undefined> => {
+  const service = OperationManifestService();


nit: 'service' is vague here

andrew-eldridge · 2026-06-15T19:51:59Z

+        queryParameters: { 'api-version': apiVersion },
+        content: { settings: supportedSettings, workflowKind },
+      });
+    } catch {


are there any exceptions which should be surfaced here rather than silently failing

andrew-eldridge · 2026-06-15T19:54:42Z

+    if (isReadOnly) {
+      (merged as Record<string, unknown>)[settingKey] = { ...existing, value: defaultValue, readOnly: true };
+    } else if (settingKey === 'retryPolicy' && isDefaultRetryPolicy(existing.value)) {
+      (merged as Record<string, unknown>)[settingKey] = { ...existing, value: defaultValue, defaultHint: defaultValue };


Is retryPolicy the only setting that uses defaultHint? I see it's included on the SettingData interface but only see usages for this setting

andrew-eldridge · 2026-06-15T19:56:42Z

some of the copilot comments seem valid

…st settings circular import

…derive known keys from settings, log setting-default fetch failures

…keyed backend route HTTP-family built-ins (Http, HttpWebhook, ApiConnection, ApiConnectionWebhook, OpenApiConnection, OpenApiConnectionWebhook) are synthetic on the client and not resolvable through the operationGroups catalog, so the connector route fails backend validation for them. Thread the node operationType through applySettingDefaults and select operationTypes/{operationType}/settingDefaults for these types; all catalog-resolvable operations keep the existing operationGroups route. Skip the fetch entirely for no-retry types (Request, Response, Schedule, DateTime, Compose, control/variable actions).

JoaquimMalcampo added 6 commits May 20, 2026 17:10

initial changes

b3c002d

Merge branch 'main' into jmalcampo/nodeSettingDetailsEnhancements

8c84fbc

Merge branch 'main' into jmalcampo/nodeSettingDetailsEnhancements

dece2f1

Merge branch 'main' into jmalcampo/nodeSettingDetailsEnhancements

ef1e80a

default retry policy visibility

a1d22c0

add read only host setting section

c043636

Copilot AI review requested due to automatic review settings June 5, 2026 17:09

Copilot started reviewing on behalf of JoaquimMalcampo June 5, 2026 17:09 View session

github-actions Bot added the needs-pr-update label Jun 5, 2026

Copilot AI reviewed Jun 5, 2026

View reviewed changes

Comment thread libs/designer/src/lib/ui/settings/sections/hostsettings.tsx

Comment thread libs/designer/src/lib/core/queries/settingDefaults.ts

Comment thread libs/designer/src/lib/ui/settings/sections/hostsettings.tsx Outdated

JoaquimMalcampo changed the title ~~Jmalcampo/node setting details enhancements~~ Show operation default setting values and host settings in the designer Jun 5, 2026

github-actions Bot added pr-validated needs-pr-update and removed needs-pr-update pr-validated labels Jun 5, 2026

JoaquimMalcampo added 2 commits June 15, 2026 15:12

Merge branch 'jmalcampo/nodeSettingDetailsEnhancements' of https://gi…

2dfb28f

…thub.com/Azure/LogicAppsUX into jmalcampo/nodeSettingDetailsEnhancements

Merge branch 'main' into jmalcampo/nodeSettingDetailsEnhancements

83ce0c9

JoaquimMalcampo assigned wsilveiranz, JoaquimMalcampo, Gargimitra12300 and andrew-eldridge Jun 15, 2026

JoaquimMalcampo changed the title ~~Show operation default setting values and host settings in the designer~~ feat(designer): Show operation default setting values and host settings in the designer Jun 15, 2026

JoaquimMalcampo changed the title ~~feat(designer): Show operation default setting values and host settings in the designer~~ feat(designer) - Show operation default setting values and host settings in the designer Jun 15, 2026

andrew-eldridge reviewed Jun 15, 2026

View reviewed changes

Merge branch 'main' into jmalcampo/nodeSettingDetailsEnhancements

b10a26a

JoaquimMalcampo added 4 commits June 17, 2026 14:16

port default settings uri to designer v2 and add spec test files

84b3766

fix(designer): address Copilot review - settingDefaults cache key, ho…

44309ae

…st settings circular import

fix(designer): address review - extract applySettingDefaults helper, …

b02719c

…derive known keys from settings, log setting-default fetch failures

test(designer-v2): cover applySettingDefaults helper

8490f2c

JoaquimMalcampo assigned Elaina-Lee and JoaquimMalcampo and unassigned wsilveiranz, JoaquimMalcampo, andrew-eldridge, Gargimitra12300 and Elaina-Lee Jun 18, 2026

JoaquimMalcampo requested a review from Elaina-Lee June 18, 2026 22:38

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat(designer) - Show operation default setting values and host settings in the designer#9253

feat(designer) - Show operation default setting values and host settings in the designer#9253
JoaquimMalcampo wants to merge 14 commits into
mainfrom
jmalcampo/nodeSettingDetailsEnhancements

JoaquimMalcampo commented Jun 5, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Jun 5, 2026 •

edited

Loading

Uh oh!

Copilot AI left a comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

github-actions Bot commented Jun 5, 2026 •

edited

Loading

Uh oh!

andrew-eldridge Jun 15, 2026

Uh oh!

andrew-eldridge Jun 15, 2026

Uh oh!

andrew-eldridge Jun 15, 2026

Uh oh!

andrew-eldridge Jun 15, 2026

Uh oh!

andrew-eldridge Jun 15, 2026

Uh oh!

andrew-eldridge commented Jun 15, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

Conversation

JoaquimMalcampo commented Jun 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Commit Type

Risk Level

What & Why

Changes

Impact of Change

Test Plan

Contributors

Screenshots/Videos

Uh oh!

github-actions Bot commented Jun 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🤖 AI PR Validation Report

PR Review Results

Thank you for your submission! Here's detailed feedback on your PR title and body compliance:

✅ PR Title

✅ Commit Type

✅ Risk Level

✅ What & Why

✅ Impact of Change

✅ Test Plan

⚠️ Contributors

✅ Screenshots/Videos

Summary Table

Overall, this PR passes review. The advised risk level does not need to be increased beyond the submitter's Medium selection.

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

github-actions Bot commented Jun 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📊 Coverage Check

Uh oh!

andrew-eldridge Jun 15, 2026

Choose a reason for hiding this comment

Uh oh!

andrew-eldridge Jun 15, 2026

Choose a reason for hiding this comment

Uh oh!

andrew-eldridge Jun 15, 2026

Choose a reason for hiding this comment

Uh oh!

andrew-eldridge Jun 15, 2026

Choose a reason for hiding this comment

Uh oh!

andrew-eldridge Jun 15, 2026

Choose a reason for hiding this comment

Uh oh!

andrew-eldridge commented Jun 15, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

JoaquimMalcampo commented Jun 5, 2026 •

edited

Loading

github-actions Bot commented Jun 5, 2026 •

edited

Loading

github-actions Bot commented Jun 5, 2026 •

edited

Loading