Symptoms
When setting a save into value for a rule input named ri!action, the value is not saved in the Interface Designer rule input.
The SAIL code resembles this:
saveInto: ri!action
Users will also see this behavior when using the Interface Designer to add and map a button to a rule input labeled as ri!action.
Cause
The "action" keyword disables the Interface Designer from saving the value properly. The actual function of the code works fine in process, just not in the Interface Designer. This issue has been reported to the Appian Product Team. The reference number for this issue is AN-109013.
Workaround
The most straight-forward workaround is to rename the rule input to something other than "action."
Another workaround to this issue is to use a!save like so:
saveInto: a!save(
ri!action,
save!value
)
This explicitly defines the target and the value to be saved.
Affected Versions
This article applies to Appian 17.4 and later.
Last Reviewed: November 2019