KB-1963 Button confirmation message does not reflect input value when refreshAfter=UNFOCUS

Parmida Borhani — Thu, 27 Jun 2019 04:06:00 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 6/27/2019 4:06:00 AM

Symptoms

When clicking a button immediately after inputting a value in a field, a conditional confirmMessage based on that field will not properly reflect the inputted value if refreshAfter="UNFOCUS".

Cause

confirmMessage evaluations complete before input field re-evaluations when refreshAfter="UNFOCUS", so this behavior is expected.

Action

Set refreshAfter="KEYPRESS" to ensure that the input field is evaluated before the confirmation message.

A product use case to change this evaluation behavior has been logged to the Appian Product Team for consideration.
Kindly note it is not Appian Support’s policy to disclose how or when a product use case will be implemented.

Workaround

If refreshAfter="KEYPRESS" cannot be used, it may be possible to set a conditional refreshAfter value based on the use case.

For example, if the confirm message is conditional on a null input value, then the following refreshAfter settings may be appropriate: refreshAfter: if(isnull(local!saveIntoVar), "KEYPRESS", "UNFOCUS").

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: June 2019

Tags: interfaces, design, SAIL, product use cases, open use cases

KB-XXXX Button confirmation message does not reflect input value when refreshAfter=UNFOCUS

Daniel DeVeau — Wed, 26 Jun 2019 14:29:48 GMT

Revision 10 posted to Appian Knowledge Base by Daniel DeVeau on 6/26/2019 2:29:48 PM

Symptoms

When clicking a button immediately after inputting a value in a field, a conditional confirmMessage based on that field will not properly reflect the inputted value if refreshAfter="UNFOCUS".

Cause

confirmMessage evaluations complete before input field re-evaluations when refreshAfter="UNFOCUS", so this behavior is expected.

Action

Workaround

If refreshAfter="KEYPRESS" cannot be used, it may be possible to set a conditional refreshAfter value based on the use case.
For example, if the confirm message is conditional on a null input value, then the following refreshAfter settings may be appropriate: refreshAfter: if(isnull(local!saveIntoVar), "KEYPRESS", "UNFOCUS").

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: June 2019

Tags: interfaces, design, SAIL, product use cases, open use cases

KB-XXXX Button confirmation message does not reflect input value when refreshAfter=UNFOCUS

Daniel DeVeau — Wed, 26 Jun 2019 14:29:26 GMT

Revision 9 posted to Appian Knowledge Base by Daniel DeVeau on 6/26/2019 2:29:26 PM

Symptoms

When clicking a button immediately after inputting a value in a field, a conditional confirmMessage based on that field will not properly reflect the inputted value if refreshAfter="UNFOCUS".

Cause

confirmMessage evaluations complete before input field re-evaluations when refreshAfter="UNFOCUS", so this behavior is expected.

Action

Set refreshAfter="KEYPRESS" to ensure that the input field is evaluated before the confirmation message.
A product use case to change this evaluation behavior has been logged to the Appian Product Team for consideration.
Kindly note it is not Appian Support’s policy to disclose how or when a product use case will be implemented.

Workaround

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: June 2019

Tags: interfaces, design, SAIL, product use cases, open use cases

KB-XXXX Button confirmation message does not reflect input value when refreshAfter=UNFOCUS

Daniel DeVeau — Wed, 26 Jun 2019 14:29:01 GMT

Revision 8 posted to Appian Knowledge Base by Daniel DeVeau on 6/26/2019 2:29:01 PM

Symptoms

When clicking a button immediately after inputting a value in a field, a conditional confirmMessage based on that field will not properly reflect the inputted value if refreshAfter="UNFOCUS".

Cause

confirmMessage evaluations complete before input field re-evaluations when refreshAfter="UNFOCUS", so this behavior is expected.

Action

Set refreshAfter="KEYPRESS" to ensure that the input field is evaluated before the confirmation message.

A product use case to change this evaluation behavior has been logged to the Appian Product Team for consideration.
Kindly note it is not Appian Support’s policy to disclose how or when a product use case will be implemented.

Workaround

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: June 2019

Tags: interfaces, design, SAIL, product use cases, open use cases

KB-XXXX Button confirmation message does not reflect input value when refreshAfter=UNFOCUS

Daniel DeVeau — Wed, 26 Jun 2019 14:27:13 GMT

Revision 7 posted to Appian Knowledge Base by Daniel DeVeau on 6/26/2019 2:27:13 PM

Symptoms

When clicking a button immediately after inputting a value in a field, a conditional confirmMessage based on that field will not properly reflect the inputted value if refreshAfter="UNFOCUS".

Cause

confirmMessage evaluations complete before input field re-evaluations when refreshAfter="UNFOCUS", so this behavior is expected.

Action

Set refreshAfter="KEYPRESS" to ensure that the input field is evaluated before the confirmation message.

A product use case to change this evaluation behavior has been logged to the Appian Product Team for consideration. Kindly note it is not Appian Support’s policy to disclose how or when a product use case will be implemented.

Workaround

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: June 2019

Tags: interfaces, design, SAIL, product use cases, open use cases

KB-XXXX Button confirmation message does not reflect input value when refreshAfter=UNFOCUS

Daniel DeVeau — Mon, 24 Jun 2019 18:55:30 GMT

Revision 6 posted to Appian Knowledge Base by Daniel DeVeau on 6/24/2019 6:55:30 PM

Symptoms

When clicking a button immediately after inputting a value in a field, a conditional confirmMessage based on that field will not properly reflect the inputted value if refreshAfter="UNFOCUS".

Cause

confirmMessage evaluations complete before input field re-evaluations when refreshAfter="UNFOCUS", so this behavior is expected.

Action

Set refreshAfter="KEYPRESS" to ensure that the input field is evaluated before the confirmation message.

An enhancement request to change this evaluation order has been submitted under product use case #944.

Workaround

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: June 2019

Tags: interfaces, design, SAIL

KB-XXXX Button confirmation message does not reflect input value when refreshAfter=UNFOCUS

Daniel DeVeau — Sat, 22 Jun 2019 15:37:31 GMT

Revision 5 posted to Appian Knowledge Base by Daniel DeVeau on 6/22/2019 3:37:31 PM

Symptoms

When clicking a button immediately after inputting a value in a field, a conditional message/validation based on that field will not properly reflect the inputted value if refreshAfter="UNFOCUS".

Cause

confirmMessageevaluations complete before input field re-evaluations when refreshAfter="UNFOCUS", so this behavior is expected.

Action

Set refreshAfter="KEYPRESS" to ensure that the input field is evaluated before the confirmation message.

An enhancement request to change this evaluation order has been submitted under product use case #944.

Workaround

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: June 2019

Tags: interfaces, design, SAIL

KB-XXXX Button confirmation message does not reflect input value when refreshAfter=UNFOCUS

Daniel DeVeau — Sat, 22 Jun 2019 15:32:25 GMT

Revision 4 posted to Appian Knowledge Base by Daniel DeVeau on 6/22/2019 3:32:25 PM

Symptoms

When refreshAfter="UNFOCUS" and a button is pressed without unfocusing the input field, the button confirmMessage does not display properly based on the last inputted value.

Cause

confirmMessage evaluations complete before input field re-evaluation when refreshAfter="UNFOCUS", so this behavior is expected.

Action

Set refreshAfter="KEYPRESS" to ensure that the input field is evaluated before the confirmation message.

An enhancement request to change this evaluation order has been submitted under product use case #944.

Workaround

If refreshAfter="KEYPRESS" cannot be used, it may be possible to set a conditional refreshAfter based on the use case. For example, if the confirm message is conditional on a null input value, then the following refreshAfter settings may be appropriate: refreshAfter: if(isnull(local!saveIntoVar), "KEYPRESS", "UNFOCUS").

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: June 2019

Tags: interfaces, design, SAIL

KB-XXXX Button confirmation message does not reflect input value when refreshAfter=UNFOCUS

Daniel DeVeau — Sat, 22 Jun 2019 15:31:55 GMT

Revision 3 posted to Appian Knowledge Base by Daniel DeVeau on 6/22/2019 3:31:55 PM

Symptoms

When refreshAfter="UNFOCUS" and a button is pressed without unfocusing the input field, the button confirmMessage does not display properly based on the last inputted value.

Cause

confirmMessage evaluations complete before input field re-evaluation when refreshAfter="UNFOCUS", so this behavior is expected.

Action

Set refreshAfter="KEYPRESS" to ensure that the input field is evaluated before the confirmation message.

An enhancement request to change this evaluation order has been submitted under product use case #944.

Workaround

If refreshAfter="KEYPRESS" cannot be used, it may be possible to set a conditional refreshAfter based on the use case. For example, if the confirm message is conditional on a null input value, then the following refresh settings may be appropriate: refreshAfter: if(isnull(local!saveIntoVar), "KEYPRESS", "UNFOCUS").

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: June 2019

Tags: interfaces, design, SAIL

KB-XXXX Button confirmation message does not reflect input value when refreshAfter=UNFOCUS

Daniel DeVeau — Sat, 22 Jun 2019 15:31:31 GMT

Revision 2 posted to Appian Knowledge Base by Daniel DeVeau on 6/22/2019 3:31:31 PM

Symptoms

When refreshAfter="UNFOCUS" and a button is pressed without unfocusing the input field, the button confirmMessage does not display properly based on the last inputted value.

Cause

confirmMessage evaluations complete before input field re-evaluation when refreshAfter="UNFOCUS", so this behavior is expected.

Action

Set refreshAfter="KEYPRESS" to ensure that the input field is evaluated before the confirm message.

An enhancement request to change this evaluation order has been submitted under product use case #944.

Workaround

If refreshAfter="KEYPRESS" cannot be used, it may be possible to set a conditional refreshAfter based on the use case. For example, if the confirm message is conditional on a null input value, then the following refresh settings may be appropriate: refreshAfter: if(isnull(local!saveIntoVar), "KEYPRESS", "UNFOCUS").

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: June 2019

Tags: interfaces, design, SAIL

KB-XXXX Button confirmation message does not reflect input value when refreshAfter=UNFOCUS

Daniel DeVeau — Sat, 22 Jun 2019 15:31:00 GMT

Revision 1 posted to Appian Knowledge Base by Daniel DeVeau on 6/22/2019 3:31:00 PM

Symptoms

When refreshAfter="UNFOCUS" and a button is pressed without unfocusing the input field, the button confirmMessage does not display properly based on the last inputted value.

Cause

confirmMessage evaluation completes before input field re-evaluation when refreshAfter="UNFOCUS", so this behavior is expected.

Action

Set refreshAfter="KEYPRESS" to ensure that the input field is evaluated before the confirm message.

An enhancement request to change this evaluation order has been submitted under product use case #944.

Workaround

If refreshAfter="KEYPRESS" cannot be used, it may be possible to set a conditional refreshAfter based on the use case. For example, if the confirm message is conditional on a null input value, then the following refresh settings may be appropriate: refreshAfter: if(isnull(local!saveIntoVar), "KEYPRESS", "UNFOCUS").

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: June 2019

Tags: interfaces, design, SAIL