When deploying applications with DevOps Pipelines using the LifeTime API, the deployment started with the API will skip the "Configuration or confirmation" step and will assign the modules automatically to the "(Main)" catalog causing a lot of manual rework in Service Center assigning the correct catalogs. When exactly the same deployment plan is executed with LifeTime the deploymet stops at the "Configuration or confirmation" step.

With this idea, we suggest to apply an option to activate the "Configuration or confirmation" step when a deployment is started via the API. It is not desired to assign the catalogs via the API, however that could be a great additional functionality but it is not desired to get "our" pipeline problem "fixed".