Ability to expose receive location or service with REST to support GET, POST and swagger support. And perhaps a Wizard type of tool like BizTalk WCF one to create a RESTful endpoint in BizTalk.76 votes
We hear ya! This is in the works.
Zero messagebox low latency scenario's45 votes
Enable the ability to repair and resubmit suspended or failed messages. This can be done using the ESB Toolkit, but it would be best if this was a feature available natively within the BizTalk admin console.42 votes
Possibility to create custom Shapes. Just like we do for the Pipeline components.
So we can add Generic stuff (logging,....) in a shape and reuse it. Instead of writing always the same .NET code, also maintaining that shape or all the expressions with the custom code ( I don't need to say more.... )36 votes
This is great feedback, we will take a look at the possibility to add this functionality
Better support for BAM (Business Activity Monitoring) in terms of better out-of box support for development toolset (no Excel-AddIn to create observation model), update portal to view (out-of-box support to may be PowerBI for on-premise SQL Servers- BAM db), simplified database structure and easier to manage db and infrastructure35 votes
Great feedback, and I agree the tooling around it is a little bit painful today.
There are lots of improvements that would be great for BizTalk delivery teams to take advantage of.35 votes
We are looking into providing this support for BizTalk Server 2016
We can use WCF Service Publishing Wizard to generate a REST endpoint - (while publishing the service endpoint using WCF Service Publishing Wizard, we can set the transport type (adapter name) for service endpoint as "WCF-WebHttp"). It would be nice to add swagger support to the exposed end point.
Also it would be nice to consume to a service using Swagger as used to do with WSDL/SOAP34 votes
We are working on this leveraging Azure API Managements SOAP to REST functionality. We will keep you updated! I have also put this in the backlog to have as a native support in BizTalk
Enhance orchestration subscription filters to use the same model as send ports, whereby the filters can be edited at run-time.
Changing the orchestration filters at present requires a “code change” and redeployment, which increases the risk associated with making the change. This is also an inconsistent approach, when compared to the way in which filters are managed for send ports.33 votes
Most of the native adapters include support for SSO Affiliate Applications which make re-installations a lot easier since one does not have to set passwords manually. For some reason, native SFTP adapter does not currently have support for this feature and from administrations point of view, this is a problem.30 votes
Thanks for this, we are looking into this issue.
Currently testing out of the box is limited to schema and mappings. To have similar capability for pipelines and orchestration that would increase productivity.29 votes
BizTalk Development tool-set in Visual Studio hasn't been improved much for long time now. Nino's BizTalk NoS Addin included various feature to improve the development experience for BizTalk in specific. Similar features, specific to BizTalk development could be added to Visual Studio out-of-box.
One simple example which is been long pending even after various request is to have resize, color code feature request for the Expression editor in Orchestration designer. They might trivial, but improves the development experience a lot.26 votes
Today in BizTalk, it is not possible (out-of-the-box) to read a context property inside a map.
It could be very useful to have a functoid to read the message context.25 votes
1. Audit every change to the system (stop/start endpoints, deploy, configure ports/locations, change business rules...)
2. Audit the user who terminates an instance:
Whilst BizTalk360 offers auditing capabilities, it can only audit activities that users perform via BizTalk360. It does not capture actions performed via other routes (Admin Console, Scripts, etc).24 votes
While exporting the binding, we could only export the bindings for the selected ports/orchestrations.23 votes
There are several use cases where we need to apply a map then apply a second map on the target message of the first map.
In order to do that we need to implement an orchestration or use the ESB itinerary.
It could be good to have this feature out-of-the-box: if multiple maps are associated with a port and if the source message of a map is the destination message of a previous map, then the second map is also applied.21 votes
How many times do you have to remove a full Application or many applications just to update a schema or map?
The ESB toolkit largely removes this by using the strong name of assemblies in the rules / text.20 votes
When you change the column order, sort order, column width
When you change a port and coming back to the overview screen it's back to the default screen.
So if it could be possible to remember the previous screen.20 votes
with the scope of the integration need expanded from on-premise to cloud, tracking the technical and business process and viewing these tracked data in one consolidated place is paramount. Out-of-box support to track and moniro the on-premise (BizTalk/ BAM) and colud (Azure LogicApp’s)19 votes
As the inability to form a multi server group is currently the defining decision point for customers to choose Standard or Enterprise, the 5 application limit is now a reason for pour deployment and development choices.
By removing the limit the most significant distinction between versions is still there and developers no longer have to custom-script fine grained deployment on standard edititions.
Also, a customer upgrading to Enterprise edition does not have to revisit deployment and development standards as they now should align.18 votes
- Don't see your idea?