Skip to main content
B
bernhar1k143337
January 16, 2026
Solved

Add Row Link Working when Testing Interface but not in Record List Action

  • January 16, 2026
  • 11 replies
  • 0 views

Hi,

I have several editable grids in my interface with an add row link. When I'm testing the interface in the rule editor, the link works just fine for all grids, but when I try to create a new record using the record list action, clicking the link does not do anything. 

The grids are implemented as follows:

a!gridLayout(
label: "Wachstumstreiber und Schlüsselerfolgsfaktoren",
labelPosition: "ABOVE",
emptyGridMessage: "Keine Wachstumstreiber angegeben",
headerCells: {
a!gridLayoutHeaderCell(label: "Wachstumstreiber"),
a!gridLayoutHeaderCell(label: "Schlüsselerfolgsfaktoren"),
if(
local!readOnly,
{},
{ a!gridLayoutHeaderCell(label: "") }
)
},
columnConfigs: {
a!gridLayoutColumnConfig(weight: 1),
a!gridLayoutColumnConfig(weight: 1),
if(
local!readOnly,
{},
{ a!gridLayoutColumnConfig(width: "ICON") }
)
},
rows: a!forEach(
items: ri!konzeptRecord['recordType!{e6823cb0-0826-4ba1-a489-d1b628fb0037}PEP Konzept.relationships.{6913d9a7-ad1d-43c7-b38b-1b504c3122bb}wachstumstreiber'],
expression: a!localVariables(
a!gridRowLayout(
id: fv!index,
contents: {
a!textField(
label: "Treiberbeschreibung" & fv!index,
value: fv!item['recordType!{c776f554-31f3-4e62-81e1-6aa317e7b18e}PEP Wachstumstreiber.fields.{c8ed9449-36ad-441b-814c-07401ead9ecc}bezeichnung'],
saveInto: {
fv!item['recordType!{c776f554-31f3-4e62-81e1-6aa317e7b18e}PEP Wachstumstreiber.fields.{c8ed9449-36ad-441b-814c-07401ead9ecc}bezeichnung'],
a!save(
fv!item['recordType!{c776f554-31f3-4e62-81e1-6aa317e7b18e}PEP Wachstumstreiber.fields.{69de833f-2a31-4249-853e-ae10a9ad327e}modifiedOn'],
now()
),
a!save(
fv!item['recordType!{c776f554-31f3-4e62-81e1-6aa317e7b18e}PEP Wachstumstreiber.fields.{15d5c187-0738-4597-9214-205de10141f9}modifiedBy'],
local!user
)
},
readOnly: local!readOnly,

),
a!textField(
label: "Erfolgsfaktor " & fv!index,
value: fv!item['recordType!{c776f554-31f3-4e62-81e1-6aa317e7b18e}PEP Wachstumstreiber.fields.{1da0fa42-aacd-47bb-92a9-e236e299e660}erfolgsfaktor'],
saveInto: {
fv!item['recordType!{c776f554-31f3-4e62-81e1-6aa317e7b18e}PEP Wachstumstreiber.fields.{1da0fa42-aacd-47bb-92a9-e236e299e660}erfolgsfaktor'],
a!save(
fv!item['recordType!{c776f554-31f3-4e62-81e1-6aa317e7b18e}PEP Wachstumstreiber.fields.{69de833f-2a31-4249-853e-ae10a9ad327e}modifiedOn'],
now()
),
a!save(
fv!item['recordType!{c776f554-31f3-4e62-81e1-6aa317e7b18e}PEP Wachstumstreiber.fields.{15d5c187-0738-4597-9214-205de10141f9}modifiedBy'],
local!user
)
},
readOnly: local!readOnly,

),
if(
local!readOnly,
{},
{
a!richTextDisplayField(
value: a!richTextIcon(
icon: "close",
caption: "Treiber entfernen",
link: a!dynamicLink(
value: fv!index,
saveInto: {
a!save(
ri!konzeptRecord['recordType!{e6823cb0-0826-4ba1-a489-d1b628fb0037}PEP Konzept.relationships.{6913d9a7-ad1d-43c7-b38b-1b504c3122bb}wachstumstreiber'],
remove(
ri!konzeptRecord['recordType!{e6823cb0-0826-4ba1-a489-d1b628fb0037}PEP Konzept.relationships.{6913d9a7-ad1d-43c7-b38b-1b504c3122bb}wachstumstreiber'],
fv!index
)
)
}
),
linkStyle: "STANDALONE",
color: "NEGATIVE"
)
)
}
)
}
)
)
),
selectionSaveInto: {},
addRowLink: if(
local!readOnly,
null,
a!dynamicLink(
label: "Treiber hinzufügen",
saveInto: {
a!save(
ri!konzeptRecord['recordType!{e6823cb0-0826-4ba1-a489-d1b628fb0037}PEP Konzept.relationships.{6913d9a7-ad1d-43c7-b38b-1b504c3122bb}wachstumstreiber'],
append(
ri!konzeptRecord['recordType!{e6823cb0-0826-4ba1-a489-d1b628fb0037}PEP Konzept.relationships.{6913d9a7-ad1d-43c7-b38b-1b504c3122bb}wachstumstreiber'],
'recordType!{c776f554-31f3-4e62-81e1-6aa317e7b18e}PEP Wachstumstreiber'(
'recordType!{c776f554-31f3-4e62-81e1-6aa317e7b18e}PEP Wachstumstreiber.fields.{9e1d833b-8ba3-4f64-8d1a-8424127456d6}createdBy': local!user,
'recordType!{c776f554-31f3-4e62-81e1-6aa317e7b18e}PEP Wachstumstreiber.fields.{3162e6bf-49d6-461a-9f7c-fdf157fd6472}createdOn': now(),
'recordType!{c776f554-31f3-4e62-81e1-6aa317e7b18e}PEP Wachstumstreiber.fields.{648787bd-6260-4f08-8d67-8dc9bf6f161d}mandant': local!mandant
)
)
),

}
)
),
shadeAlternateRows: true,

),

The rule input ri!konzeptRecord, into which the rows are meant to be saved, is passed down using the following call in the parent interface being used for the record list action:

rule!PEP_KonzeptMarktanalyse(
konzeptRecord: ri!konzeptRecord,
readOnly: ri!readOnly
),

I'd be happy for any pointers, as I find the inconsistent behavior between rule editor and actual call of the record list action very confusing.

Best answer by mikes0011
Does this also apply if the input form is attached to the start node

In that case it would need to be directly mapped to a parameter PV, instead of an ACP (since ACP's don't exist in start nodes).  But otherwise the same issue.

11 replies

shubhama926776
shubhama926776
January 16, 2026

In record list actions, rule inputs aren't automatically saved back to the record.

In your record list action configuration, add a writeRecords parameter or use onSuccess with a!save() to explicitly write ri!konzeptRecord back to the record after the interface interaction.
The add row link modifies ri!konzeptRecord in memory but doesn't persist without an explicit save operation in the record action context.

B
bernhar1k143337Author
January 16, 2026

But wouldn't I be able to at least see a row being added when filling out the form, i.e. at runtime, if the new row is saved in memory? Already there, the link just doesnt trigger an update to the record being edited. I also just tried adding 

a!writeRecords(
records: ri!konzeptRecord,
)

But that didn't solve my problem.

shubhama926776
shubhama926776
January 16, 2026

ri!konzeptRecord is likely null or not initialized in the record list action context.

mikes0011
mikes0011
Brainy
January 16, 2026

Traditionally if something modifies a Rule Input variable successfully in the Interface Editor but it seemingly fails to work when in an actual task, it means your task configuration probably isn't mapping the rule input to an ACP properly.  Can you show us a screenshot of your task configuration where the interface inputs are set?

B
bernhar1k143337Author
January 16, 2026

Sure will do, just remind me again: what does ACP stand for?

mikes0011
mikes0011
Brainy
January 16, 2026
what does ACP stand for

Activity Class Parameter.  In your User Input Task it will be one of the variables listed in "Inputs", and then in your Form configuration, needs to be mapped directly to a Rule Input. 

If a Rule Input value is left blank in the Form configuration, then any "save into" action performed on it (while viewing from an active task) will not actually get saved anywhere, and will seem to "automatically undo" from the standpoint of the task's active user.

Terms & ConditionsAccessibility statement