Step 2 records what your data product means to the business: the terms that define it, the jobs it serves, the products beside it, and the labels that classify it. It is the second of the wizard’s seven steps, building on the identity you set in Step 1 — Basics.
What you set here
The step has four sections. Three of them attach objects that already exist in the catalog. The fourth, Use Cases, is where you write new content.
| Section | What you add | What it creates |
|---|---|---|
| Business Terms & Indicators | Glossary terms that define what the product means | A related relation from the product |
| Use Cases | The jobs consumers do with the product | A use case object under the product |
| Related data products | Products a consumer of this one usually needs too | A related relation from the product |
| Labels | Values from the Labels code list | A has label relation from the product |
Each attach section shows a count, such as 1 attached, once it holds something.
Business Terms & Indicators
Search for a term and select it. The term then appears below the search box with its hierarchy path, object type, and workflow state. Click the ✕ to detach it.
Your metamodel drives this picker, not a fixed list. An administrator connects object types to the data product type with a related relation, and whatever they connect becomes attachable here. That is why the section covers indicators such as KPIs as well as business terms. In a standard installation, the terms come from the Business Glossary application.
Use Cases
Use cases are the one thing on this step you write rather than pick. Click + Add use case, enter a name, and add an optional description.
Each saved use case becomes a use case object under your data product. It is not a block of text stored on the product: it gets its own page in the catalog and its own place in the hierarchy. Deleting the row here deletes that object when you save. For the object type and its attributes, see Use case.
You can have one use case open at a time. While a row is in edit mode, + Add use case and the other rows’ edit buttons stay disabled until you save or cancel.
Related data products
Search for another data product and select it. This picker covers every Space you have access to, so you can attach a product from outside the Space you chose in Step 1. The product you are building never appears in its own results.
Labels
Labels come from the Labels code list of the Space you selected in Step 1 — Basics. Selected labels appear as chips under the search box rather than as full rows. When the value you need does not exist, an administrator adds it to the code list.
Choose the Space first. Until you do, the section says that a Space is needed and shows no picker. This stops you from attaching a label that belongs to a different Space.
Why a section may be missing or empty
The four sections come from your installation’s metamodel, so the step does not look the same everywhere. A section has nothing to offer when the application that supplies its objects is not installed. The same happens when an administrator has not connected that application to the data product type.
| What you see | What it means | What to do |
|---|---|---|
| The Labels section is not on the step at all | No label relation connects the data product type to a code list, usually because the Code List application is not installed | Ask an administrator to install the application and connect it |
| Labels asks you to select a Space first | The Space in Step 1 — Basics is still empty | Set the Space, then return to this step |
| Business Terms & Indicators finds no results | No object type is connected to the data product type with a related relation, usually because the Business Glossary application is not installed | Ask an administrator to install the application and connect it |
| Related data products finds no results | No other data product exists that you have access to | Nothing to fix — attach products once more of them exist |
A missing section never blocks you. The wizard continues to Step 3 — Ownership whatever this step offers.
Why it matters
Business context makes a product findable by someone who does not already know its name. A consumer browsing the Data Market searches for the term they use day to day, such as churn or active customer. They do not search for the title you gave the product. Attaching the glossary term connects the two.
The entries also build the graph around the product. Terms and related products become related relations, labels become has label relations, and use cases become child objects.
Dawiso draws all of them on the product’s page and in the knowledge graph. A reader can then move from a definition to the product that implements it. For how these object types and relations fit the wider model, see Data product object types and attributes.
Use cases answer a different question from the description. The description states what the product contains. A use case states what job someone does with it. Recording the jobs separately lets a consumer scan them without reading the description in full.
Rules the wizard enforces
The wizard enforces these rules on the Business Context step:
- Nothing here is required. No entry on this step appears in the completeness check on Step 7 — Review and publish, and none of it blocks publishing.
- A use case needs a name. Save stays disabled until you enter one. The description is optional.
- One use case at a time. While a row is open, + Add use case and every other row’s edit button are disabled. Save or cancel the open row first.
- Cancel discards rather than keeps. Canceling a new row removes it. Canceling an edited row restores the values it held before you opened it.
- No duplicates. An object you have already attached no longer appears in that section’s search results.
- No self-reference. The product you are building never appears in its own related data products.
- Labels follow the Space. The Labels picker offers values from the Space selected in Step 1 and no other.
Recommendations
None of these are enforced, but they decide whether the context helps a consumer or clutters the product:
- Attach the terms a consumer would search by, not every term the underlying data touches.
- Write each use case as the job someone does, such as
Weekly churn review, rather than as a second description of the data. - Attach a related product only when a consumer of this one genuinely needs it. Attaching too many makes the recommendations useless.
- Agree the label values with your administrator before you start, so the whole portfolio classifies products the same way.
Business context is what lets a consumer find this product without knowing its name. Next, record who is accountable for it in Step 3 — Ownership.