Skip to content

Document per-domain email notification defaults - #33

Merged
nahumtimerman merged 1 commit into
mainfrom
docs/per-domain-email-notification-defaults
Oct 7, 2026
Merged

nahumtimerman merged 1 commit into
mainfrom
docs/per-domain-email-notification-defaults

Conversation

@nahumtimerman

Copy link
Copy Markdown
Collaborator
  • New how-to: Setting Email Notification Defaults per Domain (devguide/available-cs-api/useful-cs-api-examples/per-domain-email-notification-defaults.md). It covers UpdateDomainSetting/GetDomainSettings, the six settings that take effect per domain, and a Python example (60 minutes for Domain1, 24 hours for Domain2).
  • Email Notifications overview: new "Per-domain defaults" subsection linking to the how-to.
  • Removed the Admin REST API pages get-domain-settings.md and update-domain-setting.md. The Admin REST API has no /domains/{id}/settings route (see WebApiRoutesConfigurer.cs), so these pages documented an endpoint that doesn't exist. The feature is Automation API only (Trunk CS 189265).

Facts were checked against the code: the overrides are merged in ResourceManagementService.GetReservationEmailSettings and used only for the Reserve-form defaults (ReservationsLogic.SetCreateReservationDefaultValues). The email sender always uses the global settings.

Requested in support ticket #67441.

🤖 Generated with Claude Code

Add a how-to for UpdateDomainSetting/GetDomainSettings (Automation API),
which override the Reserve-form email notification defaults per domain,
and link it from the Email Notifications overview.

Remove the Admin REST API "Get domain settings"/"Update domain setting"
pages: the Admin REST API has no /domains/{id}/settings route, so those
pages described an endpoint that doesn't exist.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@nahumtimerman
nahumtimerman merged commit 7d8c3ef into main Oct 7, 2026
1 check passed
@nahumtimerman
nahumtimerman deleted the docs/per-domain-email-notification-defaults branch October 7, 2026 10:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant