Deployment of webAPIs

RE: Deployment of webAPIs

Dastagiri Dudekula — Tue, 10 Jan 2017 13:05:16 GMT

*@aayusha

RE: Deployment of webAPIs

Dastagiri Dudekula — Tue, 10 Jan 2017 13:03:42 GMT

@tom.ryan As per the Appian best practices, we create an application for each collection of objects that we intend to reuse across applications like Common Objects Library Appliction. In the similar fashion we can also create an application for Web API, so that we can import them along with its main application. In this way we can ensure the Appian objects existence in each and every dependent applications.

RE: Deployment of webAPIs

aayusha — Tue, 20 Dec 2016 09:04:29 GMT

Thanks Tom, I understand it will be in the application while I one is creating it.
However, many a times customer does ask to deploy very specific reports or functionality and at that moment one generally forgets about that.

For now, we have created a document to list out any use of webAPI.

RE: Deployment of webAPIs

Tom Ryan — Tue, 20 Dec 2016 08:21:09 GMT

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.