Skip to main content

Onboarding and Setup

The recommended setup sequence for a new implementation is outlined below.

Discovery and Mapping​

Collect and validate:

  • XML samples
  • API samples
  • Mapping spreadsheets
  • Required filter attributes
  • Scenario rules
  • Report requirements
  • Expected reporting outputs

Output of this step:

  • Approved source-to-target mapping
  • Approved XML build mapping
  • Approved XML parse mapping

Environment Readiness​

Prepare:

  • Fabric workspace
  • Lakehouse
  • Access to secrets
  • SQL connectivity
  • API connectivity
  • Environment-specific table names

Output of this step:

  • Environment ready for notebook execution

Configuration Build​

Prepare the YAML configurations based on the approved mappings.

Use:

  • Runtime YAML-driven parsing for XML parse flows

Output of this step:

  • Validated YAML configuration set
  • Approved configuration values for environment, source, target, and API

XML Build​

Choose the appropriate source mode:

  • DB mode when source data is relational
  • XML mode when source files must be read from a shortcut or file path

Validate:

  • Identity column
  • Target root path
  • Source-to-target key mapping
  • Repeated structure handling

Output of this step:

  • Built XML target rows ready for parsing or API processing

XML Parse​

Use the generic parser pattern for XML parsing.

For repeated XML structures:

  • RowIdentity must define row creation
  • Repeated rows must be expanded using row-scope logic
  • Scalar extraction alone is not sufficient for repeated blocks

Output of this step:

  • Normalized Delta tables populated from XML

API Integration​

Configure:

  • Context payload mapping
  • Throughput settings
  • Timeout settings
  • Retry settings
  • Branch behavior
  • Request wrapper rules
  • Optional environment-based Basic authentication inputs

Validate:

  • Scenario metadata query
  • Runtime endpoint parameter mapping
  • Authentication and headers
  • Per-policy response persistence

Output of this step:

  • End-to-end API execution path ready

Reporting​

Use approved analytical mappings to build:

  • Dimension views
  • Fact views
  • Analytical outputs

Validate:

  • Business keys
  • Joins
  • Measures
  • Derived metrics
  • Data-quality assumptions
  • Semantic model table mappings to Lakehouse SQL views
  • Live connection behavior for report files
  • Embedded URL filter behavior from the application
  • Measure folder organization in the semantic model

Also complete:

  • Publish or validate the SQL view layer from views_config.yml
  • Confirm Fact_PolicyPremium grain and foreign-key resolution
  • Publish the shared Import semantic model
  • Connect report artifacts to the shared semantic model
  • Configure semantic model schema-drift handling and refresh orchestration

Output of this step:

  • Reporting-ready SQL views
  • Semantic model ready for refresh and consumption
  • Report artifacts ready for embedded or direct workspace use

Testing and Sign-off​

Complete:

  • Unit validation for YAML configurations and notebook parameters
  • Source-to-target reconciliation
  • Repeated-node parsing validation
  • API branch validation
  • Negative-path validation
  • Performance validation
  • Business signoff