Creating Components with the Wizard

Reading time: ~5 minutes | Level: Beginner Prerequisites: Walkthrough 4: Understanding Components and Data Types

What You'll Learn

• How to launch the Component Wizard
• What happens at each of the six wizard steps
• How to navigate forward, back, and skip optional steps
• Tips for filling out each step efficiently

When to Create Components Manually

Most components are created automatically when you upload a data file and the AI processes it. You create components manually when you want to:

• Add a field that was not in your uploaded data
• Build a model from scratch without uploading a file
• Create reusable components for use across multiple models

Launching the Wizard

1. Open Components (/app/components)
2. Click Create Component (100 credits when the component is created on the last step; editing and publishing are free)
3. The Component Wizard opens at /app/components/wizard

(The Quick Create button next to it opens a small modal that asks only for the component type; its Create Component button sends you to that type's single-page form. This walkthrough uses the wizard.) New accounts fund the wallet with at least $10 (10,000 credits) at /app/welcome before creating anything; a component mint costs 100 credits.

The wizard is a linear, forward-progression flow in create mode. You complete each step before moving to the next. Optional steps can be skipped.

Step 1: Choose Type

The type grid is organized in four groups:

• Data Types (12): String, Boolean, Count, Quantity, Temporal, Float, Double, Ordinal, Link, File, Token, Interval
• List Types (8): Boolean List, String List, Token List, Decimal List, Double List, Integer List, Non-Negative Int List, Positive Int List
• Structural (2): Cluster, Units
• Contextual (4): Party, Participation, Audit, Attestation

Choose the type that best fits your data. See Walkthrough 4 for guidance on when to use each type. Data types, list types and Units go through all six steps; Cluster and the contextual types (Party, Participation, Audit, Attestation) have no Advanced Settings step, so they have five. For a Cluster, the wizard points you to the Cluster Assembly Wizard instead (see Walkthrough 7).

Click Next to proceed.

Step 2: Basic Information

Enter the core identity of your component:

• Project (required, first field): the project this component belongs to. The later steps load their choices from this project
• Label (required, up to 100 characters): human-readable name. Use proper capitalization: "Customer Email Address", not "customer_email"
• Description: what this component represents and how it should be used. Be specific: "Primary contact email for customer communications and account recovery"
• Language: BCP 47 tag, default en-US
• Public Component: checkbox; leave it off unless the component should be visible outside the project

Click Next to proceed.

Step 3: The type's constraints

The step takes the name of the type you selected in Step 1, the same name the edit form uses: String Constraints, Count Constraints, Quantity Constraints, Boolean Values, Temporal Configuration and so on. Its fields change with the type:

For String: - Min Length, Max Length, Exact Length - String Format (regex), for example an email pattern - Enumerations (JSON array), for example ["active", "inactive"]; you can set a regex or enumerations, not both - Default Value

For Count: - Min Magnitude, Max Magnitude - Total Digits - Units (required): what is being counted (items, people, shares) - Default Value

For Quantity: - Min Magnitude, Max Magnitude - Fraction Digits (decimal places) and Total Digits - Units (required): measurement unit (mmHg, kg, USD) - Default Value

For Temporal: - Allowed forms, as checkboxes: Date, Time, DateTime, Duration, Year, Month, Day, Year-Month, Month-Day

For Boolean: - True Values and False Values (JSON arrays such as ["True", "Yes", "1"]) - Default Value

For Ordinal: - Ordinals, Symbols and Annotations, one entry per line, defining the ordered set

Fill in the constraints that apply to your data. You can leave optional fields empty and come back to them when editing the component later.

Click Next to proceed.

Step 4: Advanced Settings

Configure optional advanced properties (this step exists for data types, list types and Units only):

• Sequence Number: order position within a cluster (default 0000)
• UI Type: hint for form rendering: Input, Dropdown, Radio Group, Radio, Checkbox
• Hard Validate: enable strict validation for this component
• XdAny Flags: for each of these, whether an instance must carry the value (Require) or may carry it (Allow):
• ACT: Access Control Tag (Require only)
• VTB: Validity Time Begin
• VTE: Validity Time End
• TR: Time Recorded
• MOD: Time Modified
• Location

These are all optional. If you are unsure, leave them at their defaults and adjust later when editing.

Click Next (or Skip to accept the defaults) to proceed.

Step 5: Semantic Linking

Link your component to ontology concepts using RDF predicate-object pairs ("RDF Objects") that already exist in the project:

1. Available RDF Objects on the left lists the project's existing pairs; use the search box to narrow it
2. Move the ones you want to Selected RDF Objects on the right

The creation wizard cannot create new RDF Objects and has no vocabulary search. If the pair you need does not exist yet, finish the wizard and add it from the component's edit form, where the Semantic Linking step has a + button (Create New RDF Object) and a Google search button for controlled vocabularies.

Semantic linking is optional but recommended. It adds machine-readable meaning to your component, improving interoperability and enabling richer output generation.

Click Next (or Skip) to proceed to the final step.

Step 6: Review & Save

The Review & Save step shows a summary of everything you entered:

• Component Type
• Basic Information (project, label, description, language, public)
• The type's constraints (under the same name as the step)
• Advanced Settings
• Semantic Linking (when any RDF Objects are selected)

Each section has an Edit link that takes you back to that step. When satisfied, click Create Component. You are redirected to the new component's detail page.

Wizard Navigation Summary

In create mode, you can click back to a step you have completed or skipped, but not forward past the current one. The stepper at the top shows your progress and which steps are completed.

Summary

• Launch the Component Wizard from the Components page via Create Component
• The wizard has six steps for data types: Choose Type → Basic Information → the type's constraints → Advanced Settings → Semantic Linking → Review & Save (Units has all six; Cluster and the contextual types have five, with no Advanced Settings)
• Fill in required fields at each step; skip optional steps to come back later
• Click Create Component on the Review & Save step to save your component
• You can edit the component afterward using the stepped edit form, where new RDF Objects can be created

Next walkthrough

Editing Components: The Stepped Edit Form covers how to modify existing components and the difference between Save and Save & Publish.