Change value action in Constellation 25

User Experience
1

I need to implement a feature and I’m not sure how to do it in Constellation 25.

In the case type, I have an embedded list of existing Data type. This list initially has no records, and the user who has to enter them manually. One of the properties of this Data type is a Picklist of 3 elements, and the user can select one of them. If they select the first record, only some fields are displayed; if they select the other, other fields are displayed. The problem is that I don’t know how to clear the values ​​entered in the previously selected fields.

In the Traditional UI, this could be achieved with the Change Value action and clearing the entered values ​​in a data transform. However, Constellation doesn’t offer anything like that.

Any suggestions would be greatly appreciated.

2

The Constellation approach is to use form refresh settings so that when the picklist changes, pyRefreshData runs and clears the no-longer-relevant properties on the current embedded page.

For your embedded data row-

  • Use visibility conditions to show the relevant fields based on the picklist value
  • Add a form refresh trigger on that picklist field so changing it runs refresh logic
  • In the refresh data transform you can clear the fields.

Because this is an embedded list, make sure the logic is applied in the data class of the embedded property so the current row’s properties are the ones being cleared.

1 Like
3

The recommendation to achieve this requirement with the following steps.

  1. Modal dialog for your Add/Edit records
  2. Configure the View using (Data Type → Actions → Update Details Action → Configure View)
  3. Form Refresh settings on the flow action rule for your data type instance
  4. Visibility conditions based on your business rules on Step2
  5. if you need ot prefill values based on the selection, then use form Refresh Settings to pre populate
1 Like
4

Is it necessary to clear the values “on change”?

@RameshSangili and @RaviChandra have outlined the Form Refresh setting as one way to do this BUT you could also implement this. If you are on Infinity '25, it supports Embedded Data tables support Views or Actions. You could clean this up in post processing - slightly less problematic in that you don’t get stuck in a huge event driven UI (aka “action sets”) that has conflicting logic or calls to the server.

Most likely Form Refresh settings will be your solution but worth considering post-processing on the flow action too.

5

First of all thanks for your response.

I can see that in the embedded table there are two options for Add/edit: View and Action. What is the difference? Action only allow the Flow actions and View any view, even flow action view. So, if you choose View option and select any view, there is not pre/post processing. Right?