Logic Apps
Logic Apps allow developers to design workflows that articulate intent via a trigger and series of steps, each invoking an App Service API app whilst securely taking care of authentication and best practices like durable execution.
If you have any feedback or ideas on Azure Logic Apps we’d love to hear it.
-
Business Rule Engine (BRE)
We want to have BRE which can be integrated in WebApp and will be isolated from implementation.
For e.g.
If Age > 40, do this
If travel date is nearer, give some discounts and so on.Logic Apps does not provide this, it would be good if this can be integrated as a service with lower cost.
218 votesThanks for the suggestion.
-
Specific for X12 Connectors - Agreements.
Current scenario : Only a single Control Version Number(ISA12) is supported for an X12 agreement. For example, If the control version number is set to "00401", then this agreement wont work for X12 messages for version number "00501". Current solution is to create a new agreement to resolve your version number issue.
What can be done ? : Sticking to the above mentioned example, Agreement can have capability of registering more than one versions such that all the required schema (version separated) can be registered on the same agreement rather creating individual agreements for specific version numbers.
Example : X12…
110 votes -
Provide a way to assign a dedicated static outbound IP to a LogicApp
At times there is a need to add the outbound IP address of a LogicApp in some form of whitelist / Firewall rules. The current list of outbound IP address's are shared by many customer's so configuring these IP address's in the whitelist is not sage . A feature to associate a static outbound IP address to a given logic app would help in such scenarios.
80 votes -
BizTalk Flat File Encoder: Convert a given flat file instance to JSON
A very common integration scenario is that a flatfile (csv) gets uploaded to a ftp server. The file contains e.g. informations about an order which must send to a LOB-system like Salesforce. It would be nice to use a Logic App therefor, together with a FTP Connector, BizTalk Flat File Encoder and Salesforce Connector. But it is not that simple today. As far as I can see so far, we would need need a BizTalk XPath Extractor in addition. So I wish like to see a BizTalk Flat File Encoder which supports json other than just xml. I think with…
77 votes -
Add "EDIFACT Fallback Settings” support in “Enterprise Integration Pack” and LogicApp
In BizTalk, there was “EDIFACT Fallback Settings” when BizTalk has not determined the agreement. Fallback Settings were not supported ever in Azure BizTalk Services.
We need that this capability be supported in “Enterprise Integration Pack” and LogicApp
71 votes -
Add the ability to throw an Exception.
You should be able to fail a Logic App on purpose. This way you can build enterprise integration patterns to check responses of other systems and let the Logic App fail if necessary.
63 votes -
57 votes
thanks for suggestion
-
HL7 Support in Logic Apps
t will be very helpful if you add HL7 accelerator to Logic Apps similar to BizTalk. This is a gap where we are not able to propose Logic Apps for our client.
56 votes -
Update Enterprise Integration Tools to Visual Studio 2017
There is no reason that the Logic Apps tools need to be tied to VS 2015 like BizTalk tools. If we are on the cloud and using Logic Apps, we are building our Logic App in VS 2017 and need the integration tools to keep up. These should be in lock step and compatible with the core logic apps development tools for VS.
50 votes -
Call C# methods or Azure functions inside an XSLT map
It would be great to have the possibility to call some .NET code inside of our maps (transform XML with an xslt map for example) in order to determine whether or not these nodes need to be created or to add some logic in it.
44 votes -
Healthcare Integration
Core to anything I think is needed is more vertical healthcare integration, thinking of custom SAML claims etc
HL7, HIPAA EDI support41 votesThanks for the feedback – we realize these are important capabilities.
-
Execute soql query
It will be great if we have an action to execute soql query in salesforce connector , Since salesforce triggers can poll for single salesforce object
38 votes -
Option to batch outgoing EDI
Many partners need the EDI messages sent to them as batched messages.
35 votes -
Control Transform XML action timeout
Logic apps "Transform XML" action calls an XSLT map in the Integration Account. For some big messages (over 40MB XMLs) we start getting timeouts in the logic app. The default timeout is 2 minutes in logic apps, and we can't change it for a "Transform XML" action. It would be useful to have a way to increase the timeout
Thank you
33 votes -
Sort and filter integration account partners and agreements
My integration account has a not-insignificant quantity of partners and agreements. Managing them is becoming difficult because I am unable to sort, filter, or search partners and agreements by guest or host partner name on the partners and agreements blades.
27 votes -
Master data management services?
Any consideration of providing MDM capabilities in Azure or perhaps Dynamics that leverage LogicApps or other Azure integration technologies? Some integration platform vendors like Dell Boomi iPaaS include MDM in their platform. I would suggest this capability would complete the Azure integration and data management landscape.
25 votes -
Dynamics 365 for Operations - cross-company parameter
Dynamics 365 for Operations - cross-company parameter for all actions
Currently there is only one action, "get-records" that allows this functionality. not having this option for any CRUD operations on a single record significantly reduces the usability of such a connector.
The connected account that is using these actions, will default to it's default legal entity. This need to be updated to allow the ability to update to companies (legal entities) outside of its default entity.
There is another idea: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffeedback.azure.com%2Fforums%2F287593-logic-apps%2Fsuggestions%2F18574642-dynamics-365-for-operations-cross-company-parame%23comments&data=02%7C01%7Cajwittenbrink%40URBANSCIENCE.com%7Ce40134982d7d4bd6113608d67681d1af%7Cc6fc1cad6c084aa19d2fc676abf70992%7C0%7C0%7C636826697301777889&sdata=rGbPjZzaHgiUnf6762yZpMHPrxQ%2Fubg1K8Ba5tB9Hqc%3D&reserved=0 that is along this line. However, MS Support suggested that I create a new one, that focuses on the…
24 votes -
Logic app connector for Dynamics 365/ CDS should support attribute change tracking
logic app connector to update record in Dynamics / CDS does not support attribute change tracking. if source and target values for are same it just overwrites the attribute value, resulting in creating multiple audit history records and could trigger plugins/workflows registered on specific attribute update. Ideally connector should ignore attributes with same value.
It would be helpful to have option in connector to enable change tracking or if entity change tracking is enable in Dynamics connector itself should take care of it.20 votes -
Increase maximum LogicApp Message size
I routinely deal with messages >100Mbs in size. In BizTalk this is not a problem, but in Logicapps we are having various problems with connectors, etc. where such messages are not accepted. We are trying to migrate existing solutions to Logic Apps and this size limit is severely impairing our ability to do so. I would suspect other might have the same problem.
20 votesWhat file size would you need to process?
-
Make a FHIR-specific parser, to parse HL7 FHIR in an intelligent and user friendly manner
Make a parser that can take FHIR-based content (which is JSON or XML based format) and parse this in a quick and user friendly manner, for example by using FHIRPATH. FHIR is a bit tricky to parse since it uses arrays extensively. (FHIR = HL7 v4)
20 votes
- Don't see your idea?