Skip to main content
Question

Pass reference columns to Process Flow on 'Activate Detail' (when grid is empty)

  • January 19, 2026
  • 1 reply
  • 25 views

Forum|alt.badge.img+1

I would like to propose an improvement (or ask for help) regarding the Activate Detail event when used as a Start Object for a Process Flow.

I want to use the Activate detail event to trigger a Process Flow. The goal is to fetch data from an external system/API and display it in the detail screen only at the exact moment the user opens that specific tab.

Currently, when the detail grid is initially empty (no records), the Process Flow triggers successfully, but the input parameters are empty. The flow does not receive the Primary Keys (PKs) from the parent/reference record.

Because of this, the Process Flow executes, but I have no context (Foreign Keys) to determine for which parent record I need to fetch the data.

This behavior seems inconsistent compared to a Table Task. When you execute a Table Task on an empty detail screen, the application does pass the PKs from the reference/parent record into the task.

I haven't found a way to retrieve the parent context in this specific scenario.

If I am missing a configuration setting to pass the reference columns to the flow on an empty grid?

Consider this idea to enable the Activate Detail event to receive the reference columns/parent PKs as input variables, even when the detail grid itself is empty.

1 reply

Forum|alt.badge.img

At the moment, it’s not possible to pass parameters directly to the Activate Detail Process action. However, you can still achieve the same result using a small workaround.

Use the Activate Detail Process action as the start action of your process flow. Then, add a Table Task on the parent table as the second step in the flow. This table task can have the parameters you need (for example, foreign keys), which will automatically be filled with values from the selected parent row.

If you set these parameters to hidden, no task popup will be shown to the user. This means users cannot modify the values or cancel the task. Once the table task is executed, the process flow parameters will be populated with the values from the table task parameters, allowing you to continue the process as intended.