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.
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.
Update one of the process models to use a new data type, so that the same datatype is not shared among both models.
This article applies to all versions of Appian.
Last Reviewed: April 2019
© 2022 Appian. All rights reserved.