What is one of the steps to store an Avaloq API?

To store an Avaloq API, one of the essential steps is to drag the change to the instance. This action is significant because it allows the customized API, which may involve the definition of new services or alterations to existing ones, to be transferred directly to the relevant environment where it can be utilized.

By dragging the change to the instance, you are effectively marking the modifications for deployment. This step is part of a broader workflow in which changes are initiated, developed, and tested before they are finalized and integrated into the system. The process requires a clear connection to the development environment, ensuring that the API behaves as expected and adheres to the necessary specifications.

Other choices describe important actions in the broader development and deployment workflow but do not specifically pertain to the immediate step of storing an Avaloq API. For instance, compiling in the database typically involves preparing code for execution and validating its integrity, while checking out a script involves retrieving code from a code repository for modifications. Executing an SQL command relates more to database interactions rather than the direct process of storing an API within the Avaloq ICE framework.