Skip to main content

Transformation Hub in Views: Configuring Action Flows and writeback connection

After configuring your object-centric data model, you now need to set up four Action Flows and configure the writeback connection. Action Flows are essential for the Transformation Hub in Views app to function correctly, acting as the connection between your analytical data and your actual business operations.

Without setting up Action Flows, the Transformation Hub would be a "read-only" environment. You need Action Flows to manage the following:

  • Enable writeback: They allow the system to send data back to your data pools, ensuring that the manual mapping and configurations you do in the interface are saved and reflected in the underlying data.

  • Automate manual tasks: They replace the need for manual data entry by automatically updating attributes when triggered.

  • Track value: They are the mechanism that links specific "Opportunities" to "KPIs," which is how Celonis calculates and tracks the realized value of your process improvements.

Action Flows to configure

For the Transformation Hub in Views app, you need to configure four Action Flows:

Action Flow

Purpose

Map Opportunity

Takes inputs like SnapshotTaskID and OpportunityName and writes them into a specific OpportunityMapping table in your data pool. See: Manually configuring the Map Opportunity Action Flow.

Map KPI (Action Based)

Updates Augmented Attributes in your Knowledge Model to define how specific actions contribute to a KPI. See: Manually configuring the Map KPI (Action Based) Action Flow.

Map KPI (Rate Based)

Handles KPI mapping where the value is derived from a frequency or percentage rate. See: Manually configuring the Map KPI (Rate Based) Action Flow.

Map KPI (Non-Monetary)

Manages tracking for KPIs that aren't measured in currency (e.g., carbon emissions or cycle time). See: Manually configuring the Map KPI (Non Monetary) Action Flow.

Using Action Flow Blueprints (recommended) vs. manually configuring Action Flows

When setting up the four essential Action Flows for the Transformation Hub in Views app, you can choose between importing pre-built blueprints or configuring each module from scratch.

You should use blueprints when:

  • Speed is a priority: Blueprints provide the underlying logic and module structure immediately, significantly reducing setup time.

  • Standardizing across environments: If you are deploying the Transformation Hub across multiple teams or instances, blueprints ensure a consistent configuration.

  • Reducing manual error: Importing a JSON file eliminates the risk of missing a specific module or misconfiguring the basic flow logic.

And you should fully manually configure your Action Flows when:

  • Custom data structures are required: If your data pool or Knowledge Model uses highly customized table names or attributes that deviate from the standard app installation, manual setup allows for precise mapping.

  • Blueprint access is restricted: In environments where external file imports (JSON) are restricted by security policies, you must follow the manual steps to build the flow.

  • Troubleshooting specific steps: If a blueprint fails to run due to environment-specific variables, manually building the modules can help identify exactly where the connection or mapping is breaking.

Recommended: Downloading and importing Action Flow blueprints

To accelerate your setup, Celonis provides pre-configured blueprints for the four required Action Flows. These blueprints contain the standard logic and module sequences out-of-the-box, allowing you to establish the connection between your Transformation Hub and Data Pool with minimal manual effort. Follow the steps below to retrieve these assets from the Marketplace and import them into your Studio package.

To download and import Map Action Flow blueprints:

  1. Click Celonis Marketplace.

  2. Search for 'Map', displaying the four Action Flow blueprint needed:

    • Map Opportunity

    • Map KPI Action Based

    • Map KPI Non-monetary

    • Map KPI Rate Based

    map_action_flows.png

  3. Open each Action Flow module and click Download.

    This saves a local JSON file, allowing you to import that to your Action Flow. In this example, we're downloading the Map Opportunity blueprint.

    download_module.png

  4. Click Studio and open the package where you installed the Transformation Hub in Views app (as part of Installing the App).

  5. Find the Automation folder and click + Asset - Action Flow.

    Add_Action_Flow.png

  6. Configure the following Action Flow fields:

    • Name: We suggest Map Opportunity or relevant name for the module you're importing.

    • Execution type: Select Manual.

  7. Click Create.

    The Action Flow is added to the Studio package and the configuration screen loads.

    create_action_flow.png

  8. Click Blueprints - Import Blueprint and select the local JSON file.

    import_blueprint.png

  9. The blueprint is added to your Action Flow editor, allowing you to fast track the configuration of each Action Flow.

  10. Repeat steps 5 to 9 for each of the four Action Flows you need to configure.

Once you have successfully imported the blueprints, the core logic for your Action Flows is established. However, because every environment has unique connection parameters, you must now open each Action Flow and map the specific Connections, Knowledge Models, and Data Pool variables to match your instance.

Manually configuring the Map Opportunity Action Flow

Tip

If you've downloading and imported the Map Opportunities blueprint (as detailed in Recommended: Downloading and importing Action Flow blueprints), you can start this process at Step 8.

The Map Opportunity Action Flow takes inputs like SnapshotTaskID and OpportunityName and writes them into a specific OpportunityMapping table in your data pool.

To manually configure the Action Flow for the Transformation Hub in Views app:

  1. Click Studio and open the package where you installed the Transformation Hub in Views app (as part of Installing the App).

  2. Find the Automation folder and click + Asset - Action Flow.

    Add_Action_Flow.png

  3. Configure the following Action Flow fields:

    • Name: We suggest Map Opportunity.

    • Execution type: Select Manual.

  4. Click Create.

    The Action Flow is added to the Studio package and the configuration screen loads.

    create_action_flow.png

  5. Click Inputs.

    click_inputs.png

  6. Add the following inputs:

    Input Name

    Input Type

    Required

    SnapshotTaskID

    Text

    Yes

    OpportunityName

    Text

    Yes

    OpportunityType

    Text

    Yes

    For example:

    scenario_inputs.png

    You input configuration should then look like this:

    finished_scenario_inputs.png

  7. Using the Action Flow editor, click Add Module - Celonis and select Update Augmented Attribute.

    add_augmented_attribute.png

  8. Configure the Action Flow module using the following fields:

    • Connection: Select the created Application Key

    • Knowledge Model: Select the Knowledge Model from the same Studio package as the app installation.

    • Augmented Attribute: Select Opportunity Name. When selecting the attribute, ensure you choose the one listed under the o_custom_THSnapshot Data Model Table in the dropdown menu.

    • Execution type: Single update.

    • Value: Select OpportunityName.

    • Identifier: Select SnapshotTaskID.

    configure_action_flow_module.png

  9. Create a second Celonis - Update Augmented Attribute module and configure it using the following fields:

    • Connection: Select the created Application Key

    • Knowledge Model: Select the Knowledge Model from the same Studio package as the app installation.

    • Augmented Attribute: Select Opportunity Type. When selecting the attribute, ensure you choose the one listed under the o_custom_THSnapshot Data Model Table in the dropdown menu.

    • Execution type: Single update.

    • Value: Select OpportunityType. You may need to map this value by toggling the Map button, going to the Variable tab, and selecting the OpportunityType Action Flow input.

    • Identifier: Select SnapShotID.

    new_action_flow_screenshot.png

  10. Create a third module, selecting Celonis - Write back to data pool table and configure it using the following fields:

    Note

    A '404: Undefined' error may appear by default during this step. To resolve this, manually select the correct Data Pool connection from the dropdown menu as specified below.

    • Connection: Select the created Application Key

    • Data Pool: Select the Data Pool of the app (Marketplace Installed Pool) from the dropdown menu

    • Knowledge Model: Select the Knowledge Model from the same Studio package as the app installation.

    • New Connection Name: Enter TH Writeback. Use the same name as the backend object transformations that reference this name.

    • Create a new table name: Enter OpportunityMapping.

    • Data source: Select Manually map table columns. And then add three columns:

      Column name

      Define as Primary Key

      Type

      Value

      Example

      SnapshotTaskID

      Yes

      String

      SnapshotTaskID

      column1.png

      OpportunityName

      No

      String

      OpportunityName

      column2.png

      OpportunityType

      No

      String

      OpportunityType

      column3.png

  11. After configuring the Action Flow modules, click Save.

    Your Action Flow should look like this:

    save_action_flows.png

  12. To establish the writeback connection, right click on the Write back to data pool table module and click Run this module only.

    run_this_module_only.png

  13. To confirm that the writeback connection is active, click Data - Data Integration and open your Marketplace Installed Pool.

  14. Click Data Connections and confim that your TH Writeback connection is active.

    TH_Writeback_status.png

Manually configuring the Map KPI (Action Based) Action Flow

Tip

If you've downloading and imported the Map KPI (Action Based) blueprint (as detailed in Recommended: Downloading and importing Action Flow blueprints), you can start this process at Step 8.

This Action Flow updates Augmented Attributes in your Knowledge Model to define how specific actions contribute to a KPI.

  1. Click Studio and open the package where you installed the Transformation Hub in Views app (as part of Installing the App).

  2. Find the Automation folder and click + Asset - Action Flow.

    Add_Action_Flow.png

  3. Configure the following Action Flow fields:

    • Name: We suggest Map KPI (Action Based).

    • Execution type: Select Manual.

  4. Click Create.

    The Action Flow is added to the Studio package and the configuration screen loads.

  5. Click Inputs.

    map_action_based_inputs.png

  6. Add the following inputs:

    Input Name

    Input Type

    Required

    KpiID

    Text

    Yes

    kpiApproach

    Text

    Yes

  7. Using the Action Flow editor, click Add Module - Celonis and select Update Augmented Attribute.

    add_augmented_attribute.png

  8. Configure the Action Flow module using the following fields:

    • Connection: Select the created Application Key

    • Knowledge Model: Select the Knowledge Model from the same Studio package as the app installation.

    • Augmented Attribute: Select KPI Approach (Action Based). When selecting the attribute, ensure you choose the one listed under the o_custom_THKPI Data Model Table in the dropdown menu.

    • Execution type: Single update.

    • Value: Select KpiApproach. You may need to map this value by toggling the Map button, going to the Variable tab, and selecting the KpiApproach Action Flow input

    • Identifier: Select KpiID.

    configure_action_based_action_flow.png

  9. Create a second module, selecting Celonis - Write back to data pool table and configure it using the following fields:

    • Connection: Select the previously created TH Writeback connection.

    • Knowledge Model: Select the Knowledge Model from the same Studio package as the app installation.

    • Create a new table name: Enter KPIMapping.

    • Data source: Select Manually map table columns. And then add two columns:

      Column name

      Define as Primary Key

      Type

      Value

      Example

      KpiID

      Yes

      String

      KpiID

      rate_based_column_1.png

      KPIApproach

      No

      String

      KpiApproach

      rate_based_column_2.png

  10. After configuring the Action Flow modules, click Save.

    Your Action Flow should look like this:

    rate_based_example.png

  11. To establish the writeback connection, right click on the Write back to data pool table module and click Run this module only.

    run_this_module_only.png

  12. To confirm that the writeback connection is active, click Data - Data Integration and open your Marketplace Installed Pool.

  13. Click Data Connections and confim that your TH Writeback connection is active.

    TH_Writeback_status.png

Manually configuring the Map KPI (Rate Based) Action Flow

Tip

If you've downloading and imported the Map KPI (Rate Based) blueprint (as detailed in Recommended: Downloading and importing Action Flow blueprints), you can start this process at Step 8.

This Action Flow handles KPI mapping where the value is derived from a frequency or percentage rate.

  1. Click Studio and open the package where you installed the Transformation Hub in Views app (as part of Installing the App).

  2. Find the Automation folder and click + Asset - Action Flow.

    Add_Action_Flow.png

  3. Configure the following Action Flow fields:

    • Name: We suggest Map KPI (Rate Based).

    • Execution type: Select Manual.

  4. Click Create.

    The Action Flow is added to the Studio package and the configuration screen loads.

  5. Click Inputs.

    rate_based_inputs.png

  6. Add the following inputs:

    Input Name

    Input Type

    Required

    KpiID

    Text

    Yes

    kpiApproach

    Text

    Yes

  7. Using the Action Flow editor, click Add Module - Celonis and select Update Augmented Attribute.

    add_augmented_attribute.png

  8. Configure the Action Flow module using the following fields:

    • Connection: Select the created Application Key

    • Knowledge Model: Select the Knowledge Model from the same Studio package as the app installation.

    • Augmented Attribute: Select KPI Approach (Rate Based). When selecting the attribute, ensure you choose the one listed under the o_custom_THKPI Data Model Table in the dropdown menu.

    • Execution type: Single update.

    • Value: Select KpiApproach. You may need to map this value by toggling the Map button, going to the Variable tab, and selecting the KpiApproach Action Flow input

    • Identifier: Select KpiID.

    MAP_KPI_Rate_Based_example.png

  9. Create a second module, selecting Celonis - Write back to data pool table and configure it using the following fields:

    • Connection: Select the previously created TH Writeback connection.

    • Knowledge Model: Select the Knowledge Model from the same Studio package as the app installation.

    • Table: Select the existing KPIMapping.

    • Data source: Select Manually map table columns. And then add two columns:

      Column name

      Define as Primary Key

      Type

      Value

      Example

      KpiID

      Yes

      String

      KpiID

      rate_based_column_1.png

      KPIApproach

      No

      String

      KpiApproach

      rate_based_column_2.png

  10. After configuring the Action Flow modules, click Save.

    Your Action Flow should look like this:

    rate_based_example.png

  11. To establish the writeback connection, right click on the Write back to data pool table module and click Run this module only.

    run_this_module_only.png

Manually configuring the Map KPI (Non Monetary) Action Flow

Tip

If you've downloading and imported the Map KPI (Non Monetary) blueprint (as detailed in Recommended: Downloading and importing Action Flow blueprints), you can start this process at Step 8.

This Action flow manages tracking for KPIs that aren't measured in currency (e.g., carbon emissions or cycle time).

  1. Click Studio and open the package where you installed the Transformation Hub in Views app (as part of Installing the App).

  2. Find the Automation folder and click + Asset - Action Flow.

    Add_Action_Flow.png

  3. Configure the following Action Flow fields:

    • Name: We suggest Map KPI (Non Monetary).

    • Execution type: Select Manual.

  4. Click Create.

    The Action Flow is added to the Studio package and the configuration screen loads.

  5. Click Inputs.

    non_monetary_inputs.png

  6. Add the following inputs:

    Input Name

    Input Type

    Required

    KpiID

    Text

    Yes

    kpiApproach

    Text

    Yes

  7. Using the Action Flow editor, click Add Module - Celonis and select Update Augmented Attribute.

    add_augmented_attribute.png

  8. Configure the Action Flow module using the following fields:

    • Connection: Select the created Application Key

    • Knowledge Model: Select the Knowledge Model from the same Studio package as the app installation.

    • Augmented Attribute: Select KPI Approach (Non monetary). When selecting the attribute, ensure you choose the one listed under the o_custom_THKPI Data Model Table in the dropdown menu.

    • Execution type: Single update.

    • Value: Select KpiApproach. You may need to map this value by toggling the Map button, going to the Variable tab, and selecting the KpiApproach Action Flow input

    • Identifier: Select KpiID.

    non_monetary.png

  9. Create a second module, selecting Celonis - Write back to data pool table and configure it using the following fields:

    • Connection: Select the previously created TH Writeback connection.

    • Knowledge Model: Select the Knowledge Model from the same Studio package as the app installation.

    • Table: Select the existing KPIMapping table.

    • Data source: Select Manually map table columns. And then add two columns:

      Column name

      Define as Primary Key

      Type

      Value

      Example

      KpiID

      Yes

      String

      KpiID

      rate_based_column_1.png

      KPIApproach

      No

      String

      KpiApproach

      rate_based_column_2.png

  10. After configuring the Action Flow modules, click Save.

    Your Action Flow should look like this:

    rate_based_example.png

  11. To establish the writeback connection, right click on the Write back to data pool table module and click Run this module only.

    run_this_module_only.png

Enabling the transformations, executing the data jobs, and deploying the version

After the Action Flows are configured and the writeback connection is established, you must synchronize your data environment to reflect these changes. This final phase involves activating the backend transformations, deploying a new version of your data model, and executing a full data load. Completing these steps ensures that the "Opportunities" and "KPIs" managed by your Action Flows are correctly processed and visible within the Transformation Hub interface.

  1. Click Data - Objects and Events and select your Marketplace Installed Pool.

  2. Click Transformations and enable all transformations.

    enable_all_transformations.png

  3. Click Create version.

    create_version.png

  4. Select Open deployment after creating the version and click Create Version.

    create_version_window.png

    The data model version is created and the deployment window opens.

  5. Select the deployed version of the data model, choose the Development environment, and then click Deploy.

    select_version_and_then_deploy.png

    The data model is now deployed to the data pool.

  6. Click View Data Pool, opening your Marketplace Installed Pool.

    click_view_data_pool.png

  7. Click Data Jobs.

    select_data_jobs.png

  8. Locate the test data jobs and click Options - Execute Data Job.

    execute_data_jobs.png

  9. Select Full load and click Execute Selection.

    full_load.png

    The data jobs execute, updating the data available.

  10. From the data pool diagram, click Data Models and select your perspective.

    click_data_models.png

  11. Click Data loads and then Load Data Model.

    load_data_models.png

  12. Select Standard Query Engine and click Load data model.

    SQE_and_load.png

  13. Verify the load: Wait for the status to change to a green checkmark.

Next steps

Setting up the remaining object transformations in the OCDM (Object Centric Data Model) is the final technical bridge that connects your raw data to the Transformation Hub.

See: Configuring the remaining object transformations