Docs

Create an Application

What this screen is for

Create scaffolds a new application from a template: it generates the repository, wires the CI/CD, and registers the result in the Catalog. It is how a new service starts life already connected to the platform rather than being retro-fitted later.

Before you start

To do this You need
Open Create and run a template scaffolder access

Several things must already exist, and a template will fail late rather than early if they do not:

Opening it

  1. Build › Create… in the sidebar.

Direct URL: /create

The interface

📸 Screenshot Placeholder: The template chooser. Mark: (1) the template cards, (2) the parameter form, (3) the review step, (4) the task log.

# Control What it does When you’d use it
1 Template list The available software templates Choosing what to create
2 Parameter form Name, owner, and template-specific options Every run
3 Review Final confirmation before anything is created Always read it
4 Task log Live output of the scaffolding run Watching it, and diagnosing a failure

The owner field matters more than it looks. It becomes the catalog owner, and a component created without a real owning group starts its life unowned.

Walkthroughs

Create an application

  1. Build › Create…
  2. Choose the template.
  3. Fill in the parameters. Name it as your teams will refer to it — this name propagates into the repository, the catalog entry, and deployment targets.
  4. Set the owner to a real group.
  5. Review, then create.
  6. Watch the task log through to completion. A template that fails part-way can leave a repository created and nothing else.

After creation

  1. Confirm the component appears in the Catalog with the right owner.
  2. Check the repository is connected and validated.
  3. Run the first pipeline from Deploy › Dev.

Scenario

A new service, from nothing to running in dev.

  1. Confirm the prerequisites first — repository provider, tested CI/CD, target system, owning group. Every one of these failures shows up mid-template, when partial work already exists.
  2. Build › Create…, choose the template, fill in name and owner.
  3. Review and create; watch the task log.
  4. Open the Catalog and confirm the entry and its owner.
  5. Go to Deploy › Dev, create an environment for the branch and deploy.
  6. Watch the Events tab rather than assuming success.
  7. If the pipeline never starts, the cause is almost always step 1: an untested CI/CD integration or an unvalidated repository. Neither fails at creation time.

Step 1 is the entire lesson. Create is fast, and the things it depends on fail slowly.

When it doesn’t work

Symptom Cause How to check Fix
Create… is not in the submenu You lack scaffolder access Access Explorer Ask for a role granting it
No templates listed None registered for this install — A platform-level setup task
Template fails part-way A prerequisite is missing — usually the repository or CI/CD The task log Fix the prerequisite, then re-run; clean up anything partially created
Component created without an owner The owner field was left blank or set to a non-existent group Catalog Set the owner on its system
Repository created, pipeline never runs CI/CD integration untested CI/CD Test the integration
Component missing from the catalog Registration failed, or the catalog has not refreshed The task log Re-check the log; wait for the refresh

Next