feat(routing-forms): sync booking questions UI with event types

[akankshahu]

What does this PR do?

This PR unifies the custom input system between Event Types and Routing Forms by replacing the custom field editor in Routing Forms with the shared FormBuilder component used in Event Types. This ensures that any new input type added to Event Types automatically becomes available in Routing Forms, eliminating the need to maintain two separate systems for form inputs.

Fixes #18987
Fixes CAL-5097

/claim #18987

Visual Demo (For contributors especially)

A visual demonstration is strongly recommended, for both the original and new change (video / image - any one).

Video Demo (if applicable):

• Show screen recordings of the issue or feature.
• Demonstrate how to reproduce the issue, the behavior before and after the change.

Image Demo (if applicable):

• Add side-by-side screenshots of the original and updated change.
• Highlight any significant change(s).

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected).
• I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. If N/A, write N/A here and check the checkbox.
• I confirm automated tests are in place that prove my fix is effective or that my feature works.

How should this be tested?

• Are there environment variables that should be set?
• What are the minimal test data to have?
• What is expected (happy path) to have (input and output)?
• Any other important info that could help to test that PR

Checklist

• I haven't read the contributing guide
• My code doesn't follow the style guidelines of this project
• I haven't commented my code, particularly in hard-to-understand areas
• I haven't checked if my changes generate no new warnings
• My PR is too large (>500 lines or >10 files) and should be split into smaller PRs

---

[github-actions]

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title "Feat/routing forms sync booking questions". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

[graphite-app]

Graphite Automations

"Send notification to Community team when bounty PR opened" took an action on this PR • (02/18/26)

2 teammates were notified to this PR based on Keith Williams's automation.

[Copilot]

Pull request overview

This pull request combines two separate features: (1) unifying the custom input system between Event Types and Routing Forms by integrating the FormBuilder component, and (2) adding Exchange 2019 support and NTLM authentication for Exchange calendar integrations. The PR title and description focus on routing forms synchronization, but the majority of file changes are related to Exchange calendar enhancements.

Changes:

• Replaced custom Routing Forms field editor with shared FormBuilder component from Event Types
• Added Exchange 2019 version support and NTLM authentication method for Exchange 2013/2016 calendar integrations
• Introduced bidirectional synchronization between two form instances to bridge Routing Forms and FormBuilder schemas

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 19 comments.

Show a summary per file

File	Description
packages/app-store/exchangecalendar/enums.ts	Added Exchange2019 enum value to support newer Exchange servers
packages/app-store/exchange2016calendar/package.json	Added @ewsjs/xhr dependency for NTLM authentication support
packages/app-store/exchange2016calendar/lib/CalendarService.ts	Implemented NTLM authentication, made getExchangeService async, added configurable exchange version
packages/app-store/exchange2016calendar/api/add.ts	Extended API schema to accept authenticationMethod and exchangeVersion parameters
packages/app-store/exchange2013calendar/package.json	Added @ewsjs/xhr dependency for NTLM authentication support
packages/app-store/exchange2013calendar/lib/CalendarService.ts	Implemented NTLM authentication, made getExchangeService async, added configurable exchange version
packages/app-store/exchange2013calendar/api/add.ts	Extended API schema to accept authenticationMethod and exchangeVersion parameters
apps/web/components/apps/exchangecalendar/Setup.tsx	Added Exchange 2019 option to version selector dropdown
apps/web/app/(use-page-wrapper)/apps/routing-forms/[...pages]/FormEdit.tsx	Replaced custom field editor with FormBuilder component, added transformation and synchronization logic

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[285729101]

@hariombalhara this replaces the custom field editor in routing forms with the shared FormBuilder component from event types, so new field types automatically become available in both places.

[sahitya-chandra]

@akankshahu Can youadd a before and after video demo of the change and address the Copilot comment

[Copilot]

Pull request overview

Copilot reviewed 10 out of 10 changed files in this pull request and generated 11 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[akankshahu]

Hello @sahitya-chandra I attempted to create a video demo as requested, but encountered licensing/feature flag restrictions when testing routing forms locally. Routing forms requires a Teams plan feature flag that's difficult to enable in a local development environment without proper enterprise license configuration.

[sahitya-chandra]

Hello @sahitya-chandra I attempted to create a video demo as requested, but encountered licensing/feature flag restrictions when testing routing forms locally. Routing forms requires a Teams plan feature flag that's difficult to enable in a local development environment without proper enterprise license configuration.

@akankshahu you dont need an enterprise license configuration to create teams locally, their must be an issue in your development setup. please try it again and without a video demo we will not be able to approve this pr.