Spike: Inventory all config properties used by Experiments, Telemetry, Content Analytics, and dotAI

[john-thomas-dotcms]

Parent Issue

No response

User Story

As a system administrator, I want to be able to change the behavior of data-driven features in the dotCMS back-end, so I can modify the behavior of these features without submitting a support ticket, and without the need to restart my environments.

We currently have both an App and a portlet for dotAI, and an App for analytics (which affects both Experiments and Content Analytics, and will soon affect Telemetry as well). Despite the fact that we have the ability to change the config via the UI (App or portlet), we still have config properties which require setting via environment variables or the system table.

We should move as many of the config props as possible into the Apps and/or portlets. This card is a first step, to identify all the config props used by these features. This will enable us to estimate the effort to move those properties to Apps or portlets, and help us ensure we don't lose any of this configurability as we merge Experiments and Telemetry data with Content Analytics data.

Acceptance Criteria

• Add a comment to this card with separate lists of all config properties for each of the following features:
  • Experiments
  • Telemetry
  • Content Analytics
  • dotAI

Proposed Objective

Technical User Experience

Proposed Priority

Priority 3 - Average

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response