19.03.2026
11:02
Hi,
today, saving processes, apps, and artifacts in the Studio lacks a structured way to document what changed and why. This creates several limitations:
- Low transparency: Changes are saved without clear intent or context.
- Weak traceability: No consistent link between a change and a requirement, bug, or external ticket (e.g., Jira).
- Inconsistent documentation: Teams rely on manual conventions, which quickly diverge.
- Difficult audits: Reviewing history becomes time-consuming and error-prone.
- Limited collaboration: Understanding someone else’s change requires digging into details instead of reading a concise summary.
Proposed Solution: “Change Commit Dialog”
Introduce a lightweight, optional dialog when saving changes, inspired by commit workflows in modern version control systems like GIT.
Core elements:
- Scope Type (mandatory)
Automatic assignment to the environment with different scopes of changelog details. Testers need more detailed information about changes from dev to test for quality management. Common users need details about new features, changes and bugfixes for daily usage.
Multiple selection of target scope: Testing, Production
- Change Type (mandatory)
Dropdown e.g.: Feature, Change, Bugfix, Improvement, Refactoring, Hotfix, Documentation
- Short Description (mandatory)
One-line summary of the change
- Detailed Description (optional)
Free text for additional context
• References (optional, structured)
• a WEBCON item ID
• External ID (e.g., Jira, Azure DevOps)
• Impact Scope (optional)
Affected processes, forms, integrations
• Breaking Change flag (optional)
Additional Capabilities:
• Search & filter change history by type, reference, or keyword
• Enforced conventions via admin configuration (e.g., mandatory Jira reference)
• API exposure for integration with application lifecycle management (ALM) tools
• Exportable automatically well designed changelog with scopes (testing and/or production) for test or final releases and audits with API support to push content eg to a Confluence page where the app supervisor can have an overview of all versions during tests and productive versions.
Benefits:
• Improved governance and audit ability through structured change tracking
• Faster collaboration with clear, standardized context
• Better integration into enterprise DevOps and ticketing ecosystems
• Higher quality deployments due to explicit change classification
• Less overhead to get testers and users updated
• Higher awareness of users about changes
This feature would significantly enhance WEBCON’s positioning as an enterprise-ready platform by bridging the gap between low-code development and professional software lifecycle practices.
(Text creation supported by AI - I’ve been too lazy to write everything from scratch)
Kind regards
Sébastien
