KB-2029 Unable to save value in Interface Designer when rule input is named "action"

Parmida Borhani — Tue, 26 Nov 2019 05:17:43 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 11/26/2019 5:17:43 AM

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

Tags: interfaces, rule input, SAIL, application design, Interface Designer

KB-XXXX Rule input "action" does not save value in Interface Designer

Parmida Borhani — Tue, 26 Nov 2019 05:14:18 GMT

Revision 6 posted to Appian Knowledge Base by Parmida Borhani on 11/26/2019 5:14:18 AM

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

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

Tags: interfaces, rule input, SAIL, application design, Interface Designer

KB-XXXX Rule input "action" does not save value in interface designer

Sean Kim — Mon, 25 Nov 2019 10:16:21 GMT

Revision 5 posted to Appian Knowledge Base by Sean Kim on 11/25/2019 10:16:21 AM

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

Tags: interfaces, SAIL, application design

KB-XXXX Rule input "action" does not save value in interface designer

Rebecca Jonas — Fri, 22 Nov 2019 20:43:41 GMT

Revision 4 posted to Appian Knowledge Base by Rebecca Jonas on 11/22/2019 8:43:41 PM

Symptoms

When setting a save into value for a rule input named ri!action, the value is not saved.

This can be seen in the interface designer trying to save a value into a rule input named ri!action. 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

Workaround

It is always best practice 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

Tags: interfaces, SAIL, application design

KB-XXXX Rule input "action" does not save value in interface designer

Sean Kim — Fri, 22 Nov 2019 14:39:29 GMT

Revision 3 posted to Appian Knowledge Base by Sean Kim on 11/22/2019 2:39:29 PM

Symptoms

When setting a save into value for a rule input named ri!action, the value is not saved.

This can be seen in the interface designer trying to save a value into a rule input named ri!action. 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. This issue has been reported to the Appian Product Team. The reference number for this issue is AN-109013.

However the actual function of the code works fine in process, just not in the interface designer.

Workaround

It is always best practice 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

Tags: interfaces, SAIL, application design

KB-XXXX Rule input "action" does save value in interface designer

Sean Kim — Fri, 22 Nov 2019 10:46:33 GMT

Revision 2 posted to Appian Knowledge Base by Sean Kim on 11/22/2019 10:46:33 AM

Symptoms

When setting a save into value for a rule input named ri!action, the value is not saved.

This can be seen in the interface designer trying to save a value into a rule input named ri!action. 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. This issue has been reported to the Appian Product Team. The reference number for this issue is AN-109013.

However the actual function of the code works fine in process, just not in the interface designer.

Workaround

It is always best practice 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

Tags: interfaces, SAIL, application design

KB-XXXX Rule input "action" does save value in interface designer

Sean Kim — Fri, 22 Nov 2019 08:48:14 GMT

Revision 1 posted to Appian Knowledge Base by Sean Kim on 11/22/2019 8:48:14 AM

Symptoms

When setting a save into value for a rule input named ri!action, the value is not saved.

This can be seen in the interface designer trying to save a value into a rule input named ri!action. The SAIL code resembles this:

saveInto: ri!action

Cause

The "action" keyword disables the interface designer from saving the value properly. This issue has been reported to the Appian Product Team. The reference number for this issue is AN-109013.

However the actual function of the code works fine in process, just not in the interface designer.

Workaround

It is always best practice 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

Tags: interfaces, SAIL, application design