The Data Product Wizard

Building a good data product means getting several things right at once. It needs a clear identity, an accountable owner, the right data, clean interfaces, a contract that states its guarantees, and enough completeness to be trusted. Each of these is a concept in its own right: domains, ports, contracts, ownership, quality. The Data Product Wizard exists so you do not have to assemble them by hand or hold the whole model in your head.

The wizard guides you through the decisions in order, enforces the rules that keep a product valid, and produces a complete, standards-conformant product ready to publish to the Data Market. Use it whenever you create a data product: it is the fastest way to build one correctly, and every rule it enforces is a rule that keeps your product high quality and safe for others to depend on.

The seven steps

The wizard walks you through seven steps. Each one adds a layer to the product, and each has its own detailed page.

1. Step 1 — Basics: the product’s identity and where it lives — Space, domain, name, ID, type, visibility, and the description consumers read first.
2. Step 2 — Business Context: the meaning around the product — glossary terms, use cases, related products, and labels.
3. Step 3 — Ownership: who is accountable — the Owner, required to publish, plus optional Steward, Custodian, SME, and Producer.
4. Step 4 — Data Assets: the catalog assets the product is built from.
5. Step 5 — Ports: the output ports that expose data to consumers, and the input ports that record what it consumes.
6. Step 6 — Contracts: the optional data contract that governs what each port delivers.
7. Step 7 — Review and publish: the completeness check, then park the product in announcement or publish it to production.

Before you start

The wizard assumes a few things are already in place:

• The Data Product Standard application is added to your Space.
• The domain your product belongs to exists.
• The data assets you want to include are already cataloged in Dawiso (scanned or added manually).

Launch the wizard

In the top navigation, click + Create and, under Wizards, select Create Data Product.

You can also start from a domain in the hierarchy. The wizard then opens with the Space and domain already filled in and locked, so the product is created where you started.

To reopen an existing product, use Edit in wizard on the detail page of the data product, one of its ports, or its data contract. Starting from a port or a contract opens the product’s wizard on the step that owns it.

Resume or restart your draft

The wizard autosaves your progress as a draft. If you leave and return, a dialog asks whether to Resume draft or Start over — it blocks the wizard until you choose one.

The draft is stored in your browser, not on the server. It survives a reload or a closed tab on the same machine, but it does not follow you to another browser or device. Drafts are kept separately for a new product and for each product you edit.

Opening the wizard from a data product proposal is the one exception: the proposal is applied straight away and replaces the draft, without showing that dialog. See Open the wizard from a data product proposal.

Open the wizard from a data product proposal

An AI agent can draft a data product proposal from an object already in the catalog. It creates nothing in the catalog itself: it hands you a link that opens the wizard with the proposal already filled in.

Start a proposal

On an object’s detail page, a Promote to data product button appears when all of the following are true: an administrator has enabled Agent Studio for your environment, the object is flagged as a candidate for promotion, and you have write permission on the object.

1. Select Promote to data product. A Preparing a data product proposal. notification confirms the agent has started. It runs in the background, so you can keep working elsewhere while it does.
2. When it finishes, look for the notification that says Your data product proposal is ready, with an Open in wizard link. Select it to continue below.

The agent can also come back without a proposal, and tells you why: the object is already part of a data product, the object can’t become one, it has too many dependencies to model cleanly, no single domain could be determined, data products aren’t configured for this environment, or the run itself timed out or couldn’t be prepared. Resolve the underlying issue (permissions, configuration, or an overly complex object) and try again, or build the product yourself with the wizard instead.

What happens next

Open the Open in wizard link and the wizard starts on Step 1 — Basics with the proposal already filled in: the product’s identity and domain, the ownership roles the agent suggested, the catalog assets it picked, its ports, and any contract it drafted. From there the wizard behaves exactly as it does for a product you started yourself: work through the steps, correct whatever the agent got wrong, and finish with Save for later or Publish now. Nothing is written to the catalog until you choose one of those.

Two things differ from the normal start:

• The proposal replaces an unfinished draft. Following the link is itself your answer to resume or start over, so the wizard applies the proposal without showing the Resume draft dialog and discards the draft it had saved. Finish or publish an in-progress product before you open a proposal link.
• The link applies the proposal once per visit, then leaves the address bar. After the proposal loads, the wizard removes the token from the URL. The wizard only starts saving a draft once you make an edit or select Save for later. Do one of those before you reload the page or navigate away, or your next visit opens an empty wizard instead of resuming your edits.

A proposal is never deleted, so the link still works if you come back to it days or weeks later. But nothing marks a proposal as already applied, so opening the same link again re-applies it from scratch and discards whatever draft you had been working on since, exactly as the first bullet above describes. Treat the link as a starting point to follow once per product, not a bookmark to return to. Only a Contributor or an Administrator can open a proposal link; a Viewer sees the wizard’s error page, as they do for an unrecognized or mistyped token.

Save for later or publish

At the last step you choose what happens to the product:

• Save for later keeps the product in the announcement workflow state — the first state of the data product workflow. It is not visible in the Data Market, and it does not need an Owner. Complete Step 1 — Basics first: until every field there is filled in, Save for later stays disabled.
• Publish now moves the product to production — live, listed as trusted, and shoppable in the Data Market. This requires an Owner: without one, Publish now stays disabled.

You can publish only once every completeness item is resolved. See Step 7 — Review and publish for the full checklist.

To see the whole flow with concrete values — a real domain, real assets, and a contract with service levels — follow Build your first data product. Before you publish, check the product against the Pre-publish checklist.