KB-1654 Refresh services in Call Web Service node causes inputs to change in different Call Web Service node

Jordan Horwat — Wed, 24 Apr 2019 13:44:09 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 4/24/2019 1:44:09 PM

Symptoms

Consider a scenario where there are two process models, PM A and PM B that each contain a Call Web Service node. Refresh services is called within the Call Web Service node in PM A. This causes an input in PM B to be updated to the same parameter as the input in PM A.

Cause

This is happening because the process models are using the same data type, but are attempting to define it differently. Types in Appian are defined by namespace and name. Since both process models use the same type in the same namespace, making changes to the type definition in one process model changes the type definition in the other.

This is the expected behavior. As mentioned in the Updating WSDL Data Types section of the Call Web Service Smart Service documentation, when the “Refresh Services” button is clicked, the WSDL will update all data types to match new WSDL definition.

Action

Update one of the process models to use a new data type, so that the same datatype is not shared among both models.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2019

Tags: CDTs, applications, process models, web services, application design

KB-1654 Refresh services in Call Web Service node causes inputs to change in different Call Web Service node

Jordan Horwat — Wed, 15 Aug 2018 19:28:51 GMT

Revision 7 posted to Appian Knowledge Base by Jordan Horwat on 8/15/2018 7:28:51 PM

Symptoms

Cause

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-104846.

Action

Update one of the process models to use a new data type, so that the same datatype is not shared among both models.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: CDTs, applications, process models, web services, application design

DRAFT KB-XXXX Refresh services in Call Web Service node causes inputs to change in different Call Web Service node

Sean Kim — Wed, 15 Aug 2018 11:23:39 GMT

Revision 6 posted to Appian Knowledge Base by Sean Kim on 8/15/2018 11:23:39 AM

Symptoms

Cause

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-104846.

Action

Update one of the process models to use a new data type, so that the same datatype is not shared among both models.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: CDTs, applications, process models, web services, application design

DRAFT KB-XXXX Refresh services in Call Web Service node causes inputs to change in different Call Web Service node

Sean Kim — Wed, 15 Aug 2018 11:22:34 GMT

Revision 5 posted to Appian Knowledge Base by Sean Kim on 8/15/2018 11:22:34 AM

Symptoms

Given a scenario where there are two process models PM A and PM B, when Refresh services is called in a Call Web Service node in PM A, an input in PM B using the same datatype is also updated to the same inputs as the input in PM A.

Cause

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-104846.

Action

Update one of the process models to use a new data type, so that the same datatype is not shared among both models.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: CDTs, applications, process models, web services, application design

DRAFT KB-XXXX Refresh services in Call Web Service node causes inputs to change in different Call Web Service node

Jordan Horwat — Thu, 09 Aug 2018 09:43:29 GMT

Revision 4 posted to Appian Knowledge Base by Jordan Horwat on 8/9/2018 9:43:29 AM

Symptoms

Cause

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-104846.

Action

Update one of the process models to use a new data type, so that the same datatype is not shared among both models.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: CDTs, applications, process models, web services, application design

DRAFT KB-XXXX Refresh services in Call Web Service node causes inputs to change in different Call Web Service node

Sean Kim — Thu, 09 Aug 2018 08:24:11 GMT

Revision 3 posted to Appian Knowledge Base by Sean Kim on 8/9/2018 8:24:11 AM

Symptoms

Cause

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-104846.

Action

Update one of the process models to use a new data type, so that the same datatype is not shared among both models.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: CDTs, applications, process models, web services

Refresh services in Call Web Service node causes inputs to change in different Call Web Service node

Sean Kim — Wed, 08 Aug 2018 15:29:21 GMT

Revision 1 posted to Appian Knowledge Base by Sean Kim on 8/8/2018 3:29:21 PM

Symptoms

Given a scenario where there are two process models PM A and PM B, when Refresh services is called in a Call Web Service node in PM A, an input in PM B with the same name is also updated to the same inputs as the input in PM A.

Cause

This is happening because the process models are using the same data type, but are attempting to define it differently. Types in Appian are defined by namespace and name. Since both process models use the same type in the same namespace, if you make changes to the type definition in one process model, those changes will be reflected in the other process model.

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-104846.

Action

Update one of the process models to use a new data type so that the same datatype is not shared among both models.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: CDTs, process models, web services

Refresh services in Call Web Service node causes inputs to change in different Call Web Service node

Sean Kim — Wed, 08 Aug 2018 11:29:42 GMT

Revision 2 posted to Appian Knowledge Base by Sean Kim on 8/8/2018 11:29:42 AM

Symptoms

Cause

This is happening because the process models are using the same data type, but are attempting to define it differently. Types in Appian are defined by namespace and name. Since both process models use the same type in the same namespace, if you make changes to the type definition in one process model, those changes will be reflected in the other process model.

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-104846.

Action

Update one of the process models to use a new data type so that the same datatype is not shared among both models.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: CDTs, process models, web services