The development team at a holding company implemented a CI/CD pipeline for ELMA 365, moving widget script management from the platform's web designer to a Git repository. This transition enables code reviews, version control, and AI-assisted development, which were previously impossible within the browser-based environment.
The team initially used a headless browser to automate script deployment, but found it unreliable due to interface dependencies. They later reverse-engineered the platform's server-side TypeScript compiler. By replicating the server's type definitions and compilation logic locally, they ensured that code compiled in their repository matches the platform's execution requirements.
The developers identified that import failures on the authoring server were caused by version identity conflicts rather than signature issues. They also discovered that the platform does not recompile scripts during import, meaning the compiled code must be included in the package. To mitigate this, they implemented a post-installation verification step that exports and compares the server state against the source.
The final CI/CD workflow involves exporting the solution, modifying TypeScript files, compiling locally, and performing a diff review. After installation, the system performs a secondary export to confirm that the server state matches the repository. This process also includes comparing forms before applying third-party updates to prevent the accidental removal of custom modifications.
