How are changes in source integration managed within Avaloq ICE?

The management of changes in source integration within Avaloq ICE is primarily achieved by merging them with the existing repository. This process is vital for maintaining consistency and coherence across various integrations. When changes are made to source integrations, they are often designed to enhance functionality or address issues within the system. By merging these changes into the existing repository, Avaloq ICE ensures that all components remain synchronized and that the integrity of the overall system is preserved.

Merging incorporates new features and updates directly into the current codebase, allowing for smoother deployment and integration workflows. This process reduces the risk of conflicts that can arise from keeping separate versions, ensuring that all relevant components work together effectively.

Other methods mentioned, such as archiving changes for future reference or communicating with external systems, play different roles in the integration process but do not directly manage how changes are implemented into the existing frameworks as effectively as merging does. Separating changes into different versions can complicate integration workflows and make it challenging to maintain an up-to-date codebase, which reinforces the importance of merging in the Avaloq ICE context.