Help Centre

In this section

About stages and operations ↓

Stage types ↓

Working with stages ↓

Editing, renaming and re-ordering ↓

Adding and configuring stages and operations ↓

Stage inputs ↓

Stage outputs ↓

Disabling stages and operations ↓

Configuration errors ↓

About stages and operations

Quantemplate breaks the data transformation process down into stages and operations, allowing you to sequence and structure your data transformation process in a way that is easy to browse and navigate.

Stages are structural components with a defined number of inputs and outputs. There are three kinds of stage: Transform, Union and Join.

Operations are individual transformation steps, grouped together within a Transform stage.

For a full list of operations available in Transform stages, see the Operations Index.

Stages can be visually expanded to show inputs, outputs and configuration options, and can be collapsed to provide an overview of the whole process. When clicked, operations slide across to reveal their configuration panel.

Stage types

Join stage

A Join stage combines two different datasets which have one or more shared columns of data. For example, a premium dataset could be joined to a claims dataset using the policy number column as the join point. A join stage would typically have one or two outputs. Learn more about the Join stage.

Union stage

A Union stage is used to combine multiple datasets with identical sets of column headers to produce a single output. Because the headers are the same in each source file the rows can be stacked on top of each other to produce a single unified output dataset. Learn more about the Union stage.

Transform stage

Operations to transform data are accessed and sequenced in Transform stages. Transform stages allow multiple input datasets; the number of output datasets will usually equal the number of input datasets, unless the Aggregate or Partition operations have been used. These operations can potentially change the number of output datasets created.

Working with stages

Sequencing and connecting stages

Data runs through the pipeline in sequential order, from top to bottom in the pipeline view. For the data to run between stages, the outputs of one stage are selected as the inputs to a lower stage.

Visualising connections

Connections between stages are shown to the right of the pipeline panel. Hovering over a stage highlights the connections to other stages.

Previewing changes with ‘Trace’

Trace is a feature that enables changes in pipeline configuration to be rapidly previewed downstream. As you build and edit a pipeline, Trace simulates and validates any changes you make along the way, without the need to execute the pipeline. This provides a real time view of the data structure at any point in a pipeline and helps to flag errors prior to running the pipeline.

As you make changes, it may take a few moments for Trace to run through the pipeline. Trace progress is indicated by a spinner on each stage being processed.

Editing, renaming and re-ordering

Editing stages

Click on a stage to expand it and view its inputs, outputs and operations.

Expand or contract all stages

Click the expand-contract button at the top of the pipeline to expand or contract all stages at once.

Renaming stages

To rename a stage, double click on the stage name, or click the edit icon to the right of the stage name.

Editing and renaming operations

To edit an operation, click on the operation to go to its edit panel. The stage the operation sits within is listed top left – click it to go back to the stages view.

To rename an operation, click on the operation to go to its edit panel. Click on the name to edit it.

Reordering stages and operations

To reorder stages, click on the ‘...’ next to the stage icon. Select ‘Move stage’ and enter the position to move it to.

Note that if a stage that uses outputs from a previous stage is reordered above its inputs, the inputs will be removed. Outputs may also need to be reconnected if inputs are lost.

To reorder operations, hover over the operation you wish to move then drag and drop it to its new position.

Adding and configuring stages and operations

To configure a Transform stage:

1. Click ‘Add stage’ and select ‘Transform stage’.
2. Click ‘Add inputs’ to select inputs for the stage.
3. Click ‘Add operation‘ and select or search for an operation.
4. Click on the operation to view its configuration panel.
5. Run the pipeline to view the results.
6. Add more operations as desired.

To configure Join stages, add inputs and click on the join configuration panel. Learn more.

To configure Union stages, simply add inputs – no further configuration required. Learn more.

Stage inputs

Adding stage inputs

Use the input selector to define inputs to a stage.

To add stage inputs:

1. If the stage is contracted, expand it to reveal the operations.
2. Click the green ‘Add inputs’ button. In the popup, navigate and search the available input files.
3. Select the desired input files by clicking their checkboxes, or select all the results of a search by clicking ‘Select all results’.
4. Click the green ‘Apply selection’ to apply the changes. Click ‘Cancel’ or close the popup to discard the changes.

Tip

Selections are retained when performing an additional search. This means you can search for ‘Premiums’ and select all results, then search for ‘Claims’ and select all results to input all datasets with either ‘Premiums’ or ‘Claims’ in their filename.

Import and auto-update feeds

To automatically import data from feeds, see connecting feeds to pipelines.

Link stages

The ‘Link stages’ feature enables the outputs of one stage to be linked to the inputs of another stage. If the first stage’s input files change, the new files will be passed through to the linked stage.

Using Linked Stages

A common use for Linked Stages is to link the output of Stage 1 to the inputs of a Stage 2, which is often a Union. When new files are added to Stage 1, they will flow through automatically to Stage 2.

Tip

If using Linked Stages, it's still recommended to Union incoming files early in the pipeline. The output ID from a Union Stage is immutable, so stages referencing it are not affected by changes to the Union's input files. Using a Union early makes the pipeline faster to Trace and more resilient to configuration changes.

To enable Linked Stages:

1. Open to the Input Selector popup and navigate to the Stage Outputs tab.
2. Hover over the Stage you wish link from. The Linked Stages button appears on the right.
3. Click the Linked Stages and click the toggle in the popup to enable Linked Stages.
4. Finally, click ‘Apply Selection’ to apply the setting.

Input sources

A stage can accept inputs from five sources:

• Feeds
  Raw datasets uploaded to submissions within feeds.
• Uploads
  Raw datasets uploaded to this pipeline. Files can be added directly to the pipeline here.
• Stage outputs
  Outputs from upstream stages in this pipeline. These are grouped by stage.
• Reference data
  Datasets in your data repo.
• Partners
  Pipelines outputs shared by other organisations, if your organisation has enabled this feature. These are grouped by Partner organisation.

When an input is selected within a category, a green dot is shown next to the category icon.

Uploading data to a pipeline

Bordereaux or submission data which requires cleansing should be uploaded to a pipeline, rather than the Data Repo.

The best way to upload data to a pipeline is via the Input Selector.

1. Open a stage.
2. Click add inputs.
3. Go to the Uploads tab and add files via drag-and-drop or the ‘choose files’ button.
4. Select the uploaded files using the checkbox and click ‘Apply Selection’.

Uploaded files are made available to all stages in the pipeline.

Stage outputs

Stage outputs are the datasets resulting from the processes applied to the data in a stage. They can be connected to the inputs of subsequent stages for further processing, exported your data repo, or downloaded directly.

Output file naming

The names of output files from a Transform stage are generated by appending the stage name to the start of the name of the source file. Stages that the data has passed through are therefore recorded in the file name.

A Join stage will name the output files according to the input file names and the matching options selected. See the article on Join stages for more.

A Union stage will name its single output file with the name of the stage.

Example

Making stage outputs exportable

By default all stage outputs appear in your pipeline outputs available for export. Making an output non-exportable removes it from the list of Output Datasets, though it is still available for use in subsequent pipeline stages. Disabling outputs that are not required for export has two benefits:

1. Cleaner output list
Your output list only displays your final datasets, so it’s easier to configure their export destinations.

2. Accelerated pipeline run-times
Limiting the number of datasets available for export will speed up pipeline run time.

To disable stage outputs, expand the outputs list and toggle off the ones that are not required. Toggle off all outputs for that stage by using the toggle at the top of the list. Next time the pipeline runs the disabled stage outputs will not appear in the list of output datasets.

If new inputs are added to a stage, they will be enabled by default.

Disabling operations and stages

Transform operations and Join stages can be temporarily disabled, allowing before and after comparison of the effects of that stage on your output data, without losing their configuration.

To disable an operation or stage, click on the diamond-shaped Operation button next to the operation name. The operation or stage is greyed-out, but the parameters can still be edited.

To disable all operations in a Transform stage, click on the All Operations button next to the Operations heading. Stages with all the operations disabled will display greyed-out in the pipeline editor.

Configuration errors

If a stage has an issue which might prevent a pipeline from running, or might give an unexpected result, you will be notified via an error message in the pipeline panel.

Red warnings indicate an issue with the data or configuration that needs to be resolved.

Yellow warnings are for potentially less critical issues, such as a new column being detected by Map Column Headers (see Default column mapping rules).