Mandatory Catalog Update when no Catalog available

The current Communication Studio behavior requires user confirmation to reload the catalog when creating a new project with an externally provided controller via the command line.

• The current behavior deviates from the standard Communication Studio workflow.
• This issue was encountered at the Customer site.

Issues at Customer:

• Problem 1: If the user rejects the catalog update, the project and controller creation fail. This creates inconvenience for Customer's workflow.
• Problem 2: Aborting the catalog reload during the process also results in failing project and controller creation.

Desired Behavior:

For Customer, the Communication Studio should:

• Mandate the catalog update process during the first-time project creation with an external controller. This ensures a successful setup without requiring user intervention.
• Allow the user to script the catalog update process. This provides flexibility for automation within Customer's environment.

Acceptance Criteria:

• The Communication Studio enforces mandatory catalog update during the initial project creation with an external controller.
• Project and controller creation should proceed successfully upon mandatory catalog update.
• No ability to cancel catalog updates.