Add ExternalConfig.smtp_display_settings returning a form-shaped hash
(host/port/username/password/domain/from_email/security/authentication)
so that the read-only Email SMTP settings view reflects the actual
SECURITY value (e.g. noverify) when configured via env vars, instead
of always defaulting to STARTTLS.
* feat: externalize storage config via environment variables (v1.5.0)
- Add storage_configured?, storage_service, storage_settings to ExternalConfig
- Show read-only banner and disable form when S3/GCS/Azure env vars are set
- Keep storage link visible in settings nav when externally configured
- Add 8 RSpec tests for storage config detection and settings
* fix: add server-side guard to reject storage form POST when env-configured
Addresses Devin Review feedback: the disabled fieldset was client-side only.
Now StorageSettingsController#create redirects with an alert when
ExternalConfig.storage_configured? is true.
* fix: use i18n key for storage read-only banner instead of hardcoded string
* fix: use conditional fieldset tags to avoid BetterHtml interpolation error
---------
Co-authored-by: Bob Develop <developbob50@gmail.com>
* feat: add pluggable field detection system (v0.14.0)
Add external field detection via Ruby scripts and YAML profiles.
Two plugin mechanisms supported side-by-side:
1. Ruby scripts (FIELD_DETECTION_SCRIPTS_DIR) - full-power handlers
registered via Templates::FieldDetection.register(name, handler)
2. YAML profiles (FIELD_DETECTION_CONFIG_DIR) - declarative configs
with text anchors + relative offsets OR absolute positions
Core changes:
- lib/templates/field_detection.rb: registry, loader, dispatcher
- lib/templates/field_detection/config_based.rb: YAML profile engine
with anchor-based and absolute positioning, negative page indices
- Controller accepts algorithm param, dispatches accordingly
- Split-button UI: main action = ML detection, dropdown = profiles
- RSpec tests for both modules with fixture YAML profiles
No business-specific algorithms ship with docuseal - all are injected
at deploy time via ConfigMap/mounted volumes.
* fix: use proper user/account setup in config_based spec
* fix: include submitters in algorithm detection response
---------
Co-authored-by: Bob Develop <developbob50@gmail.com>
Bob Develop
devin-ai-integration[bot]