We are exposing a startProcess smart service in a Web API object. OnSuccess we return an a!httpResponse() as follows.
According to the documentation on fv!processInfo in the startProcess smart service
fv!processInfo (ProcessInfo): Process properties of the process that was started (such as fv!processInfo.pp.id), properties of the process model (such as fv!processInfo.pm.name), and the values of process variables (such as fv!processInfo.pv.employeeId) once all initial activity-chaining is complete
Testing the Web API object in Appian the process variable is returned in the body of the response. However, when we tested this API with our external system and through CURL and PostMan a 200 status code is returned with an empty body.
My guess is that internally the async process is fast enough that the pv is set before the response is retruned, but testing the api externally the opposite occurs. Has anyone come across this issue before?
When you applied your Activity Chaining did you save and publish the process model? (it's amazing how many times this gets forgotten, the result being that the latest saved model looks like it's correct but the actual version being executed is the last published version!)
Yes this is not the issue, but thank you for the response.
Discussion posts and replies are publicly visible
© 2020 Appian. All rights reserved.