KB-2050 Script task outputs are the same despite different inputs when using load()

Parmida Borhani — Tue, 07 Jan 2020 01:47:20 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 1/7/2020 1:47:20 AM

Symptoms

When executing an expression or rule in a script task, and the expression uses the load() function, users observe that calling the same rule results in the same output despite different inputs. This behavior can occur if a rule uses the load() function to store the input in a local variable with the same name and store the output in a process variable.

Cause

This is expected behavior based on how Appian handles context within a script task.

Action

Upgrade to Appian 19.2 or later and use a!localVariables() instead of load(), as described in the documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: load function, local variables, script task, application design

DRAFT KB-XXXX Script task outputs are the same despite different inputs when using load()

Tom Ryan — Mon, 06 Jan 2020 22:13:45 GMT

Revision 9 posted to Appian Knowledge Base by Tom Ryan on 1/6/2020 10:13:45 PM

Symptoms

Cause

This is expected behavior based on how Appian handles context within a script task.

Action

Upgrade to Appian 19.2+ and use a!localVariables() instead of load(), as described in the documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: load function, local variables, script task, application design

DRAFT KB-XXXX Script task outputs are the same despite different inputs when using load()

Nicholas Van Dyke — Mon, 06 Jan 2020 21:44:15 GMT

Revision 8 posted to Appian Knowledge Base by Nicholas Van Dyke on 1/6/2020 9:44:15 PM

Symptoms

Cause

This is intended behavior based on how Appian handles context within a script task.

Action

Upgrade to Appian 19.2+ and use a!localVariables() instead of load(), as described in the documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: load function, local variables, script task, application design

DRAFT KB-XXXX Script task outputs are the same despite different inputs when using load()

Nicholas Van Dyke — Mon, 30 Dec 2019 21:30:30 GMT

Revision 7 posted to Appian Knowledge Base by Nicholas Van Dyke on 12/30/2019 9:30:30 PM

Symptoms

Cause

This is intended behavior based on how Appian handles context within a script task.

Action

Use a!localVariables() instead of load(), as described in the documentation.

Affected Versions

This article applies to Appian 19.2 and later.

Last Reviewed: December 2019

Tags: load function, local variables, script task, application design

DRAFT KB-XXXX Script task outputs are the same despite different inputs when using load()

Nicholas Van Dyke — Mon, 30 Dec 2019 20:14:28 GMT

Revision 6 posted to Appian Knowledge Base by Nicholas Van Dyke on 12/30/2019 8:14:28 PM

Symptoms

When executing a script task that uses the load() function, users observe that calling the same rule results in the same output despite different inputs. This behavior can occur if a rule uses the load() function to store the input in a local variable with the same name and store the output in a process variable.

Cause

This is intended behavior based on how Appian handles context within a script task.

Action

Use a!localVariables() instead of load(), as described in the documentation.

Affected Versions

This article applies to Appian 19.2 and later.

Last Reviewed: December 2019

Tags: load function, local variables, script task, application design

DRAFT KB-XXXX Script task outputs are the same despite different inputs when using load()

Nicholas Van Dyke — Fri, 06 Dec 2019 22:09:53 GMT

Revision 5 posted to Appian Knowledge Base by Nicholas Van Dyke on 12/6/2019 10:09:53 PM

Symptoms

When executing a script task that uses load(), users may observe that calling the same rule results in the same output despite different inputs. This behavior sometimes occurs if a rule uses the load() function to store the input in a local variable with the same name and store the output in a process variable.

Cause

This is intended behavior based on how Appian handles context within a script task.

Action

Use a!localVariables() instead of load(), as described in this documentation:

https://docs.appian.com/suite/help/19.2/Updating_Expressions_to_Use_a_localVariables.html

Affected Versions

This article applies to Appian 19.2 and later.

Last Reviewed: December 2019

Tags: application design

DRAFT KB-XXXX Script task outputs are the same despite different inputs when using load()

Nicholas Van Dyke — Fri, 06 Dec 2019 21:59:40 GMT

Revision 4 posted to Appian Knowledge Base by Nicholas Van Dyke on 12/6/2019 9:59:40 PM

Symptoms

Cause

This is intended behavior based on how Appian handles context within a script task.

Action

Use a!localVariables() instead of load(), as described in the documentation below:

https://docs.appian.com/suite/help/19.2/Updating_Expressions_to_Use_a_localVariables.html

Affected Versions

This article applies to Appian 19.2 and later.

Last Reviewed: December 2019

Tags: application design

DRAFT KB-XXXX Script task outputs are the same despite different inputs when using load()

Nicholas Van Dyke — Fri, 06 Dec 2019 21:52:11 GMT

Revision 3 posted to Appian Knowledge Base by Nicholas Van Dyke on 12/6/2019 9:52:11 PM

Symptoms

When executing a script task that uses load(), users may observe that calling the same rule results in the same output despite different inputs. This behavior sometimes occurs if a rule uses the load() function to store the input in a local variable with the same name and store the output in a process variable.

Cause

This is intended behavior based on how Appian handles context within a script task.

Action

Use a!localVariables() instead of load(), as described in the documentation below:

https://docs.appian.com/suite/help/19.2/Updating_Expressions_to_Use_a_localVariables.html

Affected Versions

This article applies to Appian 19.2 and later.

Last Reviewed: December 2019

Tags: application design

DRAFT KB-XXXX Script task outputs are the same despite different inputs when using load()

Nicholas Van Dyke — Fri, 06 Dec 2019 21:50:33 GMT

Revision 2 posted to Appian Knowledge Base by Nicholas Van Dyke on 12/6/2019 9:50:33 PM

Symptoms

Cause

This is intended behavior based on how Appian handles context within a script task.

Action

Use a!localVariables() instead of load(), as described in this documentation:

https://docs.appian.com/suite/help/19.2/Updating_Expressions_to_Use_a_localVariables.html

Affected Versions

This article applies to Appian 19.2 and later.

Last Reviewed: December 2019

Tags: application design

DRAFT KB-XXXX Script task outputs are the same despite different inputs when using load()

Nicholas Van Dyke — Fri, 06 Dec 2019 21:50:00 GMT

Revision 1 posted to Appian Knowledge Base by Nicholas Van Dyke on 12/6/2019 9:50:00 PM

Symptoms

Cause

This is intended behavior based on how Appian handles context within a script task.

Action

Use a!localVariables() instead of load(), as described in this documentation: https://docs.appian.com/suite/help/19.2/Updating_Expressions_to_Use_a_localVariables.html

Affected Versions

This article applies to Appian 19.2 and later.

Last Reviewed: December 2019

Tags: application design