Using Helper Logic Apps
  • 17 Feb 2020
  • 1 Minute to read
  • Contributors
  • Dark
    Light
  • PDF

Using Helper Logic Apps

  • Dark
    Light
  • PDF

In Logic Apps one approach I see lots of teams using is to create helper Logic Apps which encapsulate commonly reused logic. In this case you could create wrapper Logic Apps for our BAM connectors which accept a message and then send it to Serverless360 via our Connector. The result is that your Logic Apps which implement your business processes only need to call another Logic App to implement a BAM call.

This means that you could remove or change the dependancy on Serverless360 and the only place your entire Logic App estate would be affected would be in the common utility Logic Apps. You could just change these and everything else would work just as it has.

In addition to the encapsulation benefits the other good thing about this approach is that in the child logic app you could slightly modify the input message so that common properties could be required to be sent. One example I would use often would be to ensure that the calling Logic App name and run id are always passed through by defaulting these properties so that when doing a "Call Logic App" these properties are already set.


Was this article helpful?