Introduction of DTAP Configuration sets to keep track of configuration elements

Introducing M11101 for DTAP configuration management

Overview

M11101 is designed to streamline configuration management in applications within a DTAP environment. Configurations often comprise a combination of multiple datasets, working together to form a complete setup.

Datatypes in Configuration

Typical datatypes included in DTAP configurations are:

  • Export definitions
  • Import definitions
  • Workflow configurations
  • Data definitions for REST endpoints
  • Activity templates
  • Headless CMS elements

The Challenge

In large applications, managing and tracking related datasets can be complex. For example, new Headless CMS elements might depend on updated REST endpoint definitions. M11101 simplifies this by clustering datasets into a single DTAP configuration set, allowing for a unified export.

Key Features of M11101

  • Dataset Clustering: Group multiple datasets into a single DTAP configuration set.
  • Seamless Export: Perform one-click exports of entire configuration sets.
  • Universal Compatibility: M11101 works out of the box for any datatype.
  • Optional Enhancements: Small components can be added for improved usability, making it easier to link configurations, though they are not mandatory.
  • Flexible Import: Exported data can be imported into any application with an import engine — M11101 is not required in the target application.

Using DTAP Configuration Sets

You can create multiple DTAP configuration sets within your application. Each set requires two key elements:

  1. Export Definitions: Define how each datatype will be exported.
  2. Datasets: Select all datasets to be included in the DTAP configuration set.

For each dataset type, you must link an export definition.

Example: If your DTAP configuration contains 7 export definitions, 3 import definitions, and 4 REST data definitions, you will need to link the corresponding export definitions for each datatype.


Setting Up a DTAP Configuration Set

Step 1: Define Export Definitions

  • Navigate to Settings > DTAP Dataset Configurations.
  • In panel (1), link the export definitions needed to export the desired data types.

Step 2: Link Datasets

  • In panel (2), add the individual datasets to be exported.
  • Ensure export definitions are correctly linked; datasets without a corresponding export definition will not be exported.
  • Add comments or notes for yourself or team members as needed.

Step 3: Export the Configuration

  • Use the export button at panel (3) to generate a ZIP file containing all defined data.
  • This ZIP file can be imported into another Novulo application using the Import with embedded definition option (XML format).

Linking Datasets

M11101 offers two ways to link datasets to DTAP configuration sets:

  1. From the DTAP Configuration: Directly add datasets within the DTAP configuration interface.
  2. From the Dataset: Link a dataset to a DTAP configuration set from its own record view.

M11101 natively supports import and export definitions. Additional components or new revisions can be created to support other record types, but these are not included by default.


Community Contributions

For integrations beyond the standard datatypes, you can develop and share custom components that implement this functionality. Feel free to post these contributions in the relevant community thread.


With M11101, managing and exporting complex configurations within DTAP environments becomes straightforward and efficient. Start clustering your datasets today for better control and seamless deployment!

2 Likes

Hey Joost,

As we discussed I’m currently trying to implement this great component and it works like a charm!

One QoL improvement would be that you can toggle the “is_active” of the linked DTAP exportdefintion on tabelindex (the gridview).

Besides that we’ve talked about it being able to allow expressions to be used or the “export everything” function. Because I’ve noticed I still export multiple records via the same export definition and I know we discussed that that undermines the purpose of the component I still think being able to do that in combination with the ability to group export definitions is extremely usefull, since I’ve lost track of my datasets and exportdefinitions quite a lot :slight_smile:.

Anyways, big thanks for this component, I will be using the for the coming weeks and maybe even months.

Jesse

Hey @Joost, I keep getting an error, which I don’t understand good enough to fix. I want to export my full set-up, to back it up, but for some reason there is one exportdefinitions which blocks me from doing so. I try to export:

with these parameters settings:

But I keep getting this error:

If I understand the cause I might be able to solve this, but these settings one looks just the same as the others to me.

Jesse

Hi Jesse,
This error typically occurs when the Export Definition itself is incorrect. For example, when the Filters don’t match the parameter. It’s not an error from the M11101 component.
You can use System Health to identify corrupt fields in Export Definitions.

1 Like