Deployment of webAPIs

Certified Senior Developer
I have a tempo report which uses a webAPI in the interface (endpoint saved in a constant).
Now during the deployment, I forgot to deploy the webAPI to higher environment (which was observed during the UAT).

How do other practitioners keep track of webAPI which are used and should be deployed to higher environment?
Is there a standard Appian way of doing this?
OR
Do others also just document it for future purposes?

OriginalPostID-253429

  Discussion posts and replies are publicly visible

Parents
  • When initially creating the Web API through the /design interface, it will automatically be part of the parent application, so in the case where the whole application is being updated, then there shouldn't be an issue since the Web API will be included.

    In the case where the endpoint text is referred to, unfortunately there won't be a dependent/precedent relationship, so as you saw it won't be flagged as missing during import.
Reply
  • When initially creating the Web API through the /design interface, it will automatically be part of the parent application, so in the case where the whole application is being updated, then there shouldn't be an issue since the Web API will be included.

    In the case where the endpoint text is referred to, unfortunately there won't be a dependent/precedent relationship, so as you saw it won't be flagged as missing during import.
Children
No Data