How to design a general process model with integration service called by other Appian applications

Certified Senior Developer

Hi,

We have a process model that calls some integration SOAP services (that process is small and contains less than ten nodes).

That process needs to be called by different Appian applications (on same server), so we need to generalize this process model.

Today, we have 5 applications :

- SHARED_APP : commun rules and components used by each applications below

- APP1_APIs : APIs integration used by APP1

- APP1 : application 1

APP2 : application 2 (that application contains temporarly the Integration SOAP API describes above)

APP3 : application 3

How would you do to generalize this process model ?

- Creating this process model in the SHARED_APP application. Then the SOAP Integration service would be added there too.

  In this case, the 3 applications (APP1, 2, 3) would just need to call this general process model from SHARED_APP

- Creating this process model in a new application called SHARED_API. Then the SOAP Integration service would be added there too.

  In this case, the 3 applications (APP1, 2, 3) would just need to call this general process model from SHARED_API

- Adding the SOAP Integration service "only" (not the process model) in the SHARED application (or in SHARED_API).

  In this case, the 3 applications (APP1, 2, 3) each, would have to create the same process model, but the latter would call the common Integration API

  (just need to share the API key)

- Another one ?

Regards

  Discussion posts and replies are publicly visible

Parents Reply Children
No Data