What needs improvement with SnapLogic Intelligent Integration Platform (IIP)?

I feel SnapLogic can be improved, particularly on the user interface side. While it is good, I believe we can improve the GUI further. This improvement would help newcomers by making the interface more user-friendly. This is my suggestion at this time.

SnapLogic can be improved by not keeping some of the connectors that would be very useful as a premium connector. I handle monitoring and alerting for my SnapLogic pipelines by noting that the issue with SnapLogic is that you have to be an environment admin to be able to see the monitoring. This makes it quite difficult to do it from within the software. We have to bring the alerts out into a SQL database and report from there.

I do think some of the documentation could be improved as it can be a bit hard to parse, and sometimes there are simply not as many examples of things or ways to use some of the snaps as there could be. The interface recently got an upgrade which was very needed because before it was very dated and a bit clunky, and it definitely looks a lot better now, and the speed has never really been an issue. I think the documentation issue is what keeps SnapLogic from being perfect for me, along with some instances where snaps for things such as joining tables or filtering things do not work exactly how one might think they do intuitively.

SnapLogic can be improved by generating SQL queries within SnapGPT, including the variables, as it would be very useful because lately, I have been using other AI tools such as Claude or ChatGPT to generate SQL queries. If SnapLogic SnapGPT can do that efficiently, then that would be very helpful. It would be easier if there were a support chat option within the pipeline so that we do not have to raise a ticket on the portal to explain what is happening and then grant access. If by default, in the test environment and dev, not in prod, we could add a chat option where a live chat person can actually be contacted within SnapLogic itself, that would be very helpful.

Although SnapLogic is already a very good tool, it can be improved by making the GUI part, particularly the user interface, more usable, which would be more helpful for users. Apart from that, I think it is fine and good, and once we use it more, I will provide feedback on other things as well. As of now, I do not have any other improvements for SnapLogic that come to mind, but once I think of something, I will surely update.

Regarding improvements for SnapLogic, I feel the new GUI should be more readable for my team, as we find ourselves needing to zoom in and zoom out when there are too many things on the screen. I personally believe that if they enhance the GUI effect, it would be easier and handier for users. The GUI part is the only improvement I feel is necessary for SnapLogic; other than that, I find it awesome.

I do not have much idea on how SnapLogic can be improved, but UI-wise, if the user interface is improved to be more user-friendly, it would be more helpful.

I do not have much idea on how SnapLogic can be improved, but from a user interface perspective, if it were improved in a more user-friendly way, it would be more helpful. I do not have any suggestions other than that regarding SnapLogic.

SnapLogic can be improved, but as a product, it is a mature product now compared to what it was four years ago, and the team is improving with every release, so I am satisfied with that. Even if it is a small thing, I have asked them to create a new public API to create pipeline versions programmatically, rather than creating it manually, as that will help us in our CICD process.

To improve SnapLogic, the error messaging functionality needs enhancement; when there is an error with a pipeline, sometimes the errors are a little generic. Some sort of recommendations on how to fix these errors would be more useful to the team. A little more in terms of testing features and unit testing functionality would also enhance our experience, but generally, we are very happy with the product. I prefer that many of the training courses for support be much more publicly available so that anyone can train up on the platform without having to access SnapLogic University.

The only thing I do not prefer at the minute about SnapLogic is when I go into the monitor, it can be a bit slow, so when I am trying to diagnose why something went wrong and I am searching, it can take a bit of time. SnapLogic could be improved in the monitor performance area.

When we face errors in the existing scheduler run, we cannot trace the logs. Adding more logs in the existing Snaps could make it much easier to debug errors. If more logs were added to the existing Snap, users could debug errors and view log information more effectively.

SnapLogic can be improved by incorporating an AI system in the Expression Builder that learns from what has already been done in the current project, allowing for auto-suggestions. Regarding SnapLogic's AI capabilities, I believe its governance and security are good, but the actual pipeline design is not production-ready. The accuracy and reliability of SnapLogic's AI output is around thirty to forty percent, with the remaining work needing to be completed by the developer. If vague instructions are provided, approximately ten to twenty percent of the work can be handled using SnapLogic's AI, but the remaining tasks should be completed through developer intervention.

Regarding how SnapLogic can be improved, I think the Snaplex page can be improved without any downtime. There are some updates with SnapLogic that are not very stable before the release. This can be improved so that there will be no downtime impact for us.

We want to get to grips with some of the automated testing functionality in SnapLogic, but we have not had the time to do that yet. The main frustrations for us with SnapLogic have not been the technology, but the usual things of stakeholder capacity constraints and other hold-ups to the project. One improvement that would be beneficial is better visibility of SnapLogic's environmental credentials.

I think SnapLogic can be improved by implementing more seamless logging of information. Currently, this is done through an error, but it would be best to have logging available on each snap that you can turn on and off, allowing you to configure a logging mechanism for where it logs. By having each snap available for logging, you can log all the information instead of creating a separate pipeline for logging. Additionally, I suggest caching for snaps that are recursively called, particularly when logging in, authenticating, doing actions, logging out, and then repeating the process, which would significantly speed up operations, especially when querying an Active Directory because retrieving many members in Java takes about five seconds, whereas in SnapLogic, it takes a minute and a half for the same operation. Regarding the new dedupe snap, I think the default setting should be changed from the current 80% match to an exact match, allowing for changes afterward, as I ran into issues during regression testing where a minor difference led to duplicates being flagged unintentionally.

The ways SnapLogic can be improved depend on specific requirements and business needs, so I leave it to each individual business to determine its usage accordingly and weigh the pros and cons.

I see very few areas where SnapLogic needs improvement. There are some very fringe cases we have had to abandon due to minor complexity and time pressures, such as the ability to read a PDF and isolate tagged data areas on that PDF to extract data, which we did not find very easy to start with. However, we had the limitation of needing to turn this around in a matter of days, so we did not have time to investigate further. Other than that, I find it very difficult to identify areas for improvement; I think it is pretty industry-leading as far as these tools go. Comparing it to other products, I believe the return on investment has been met within a year and then some, whereas previously we wasted a lot of money trying to deliver the same things. Therefore, I have no real notes at this point, but I think consistent evolution is essential, and I look forward to seeing what they do next. Support has been exemplary.

One thing that comes to mind about SnapLogic is that the product is always improving, which is a great thing, but the changes in the UI and the way things keep moving around mean that a level of stability would help achieve a higher adoption ratio. The changes in the UI have frustrated a few people, which is why a nine for SnapLogic is justified. Additionally, some of the snaps could do with greater functionality. For example, the SOAP snap could be opened up to allow broader usage. Regarding SnapLogic's AI capabilities and its governance and security, as you determine the model that it uses, this is very much on the developer or implementer to provide that level of control. SnapLogic is open to lots of models and works with any AI model out there, and that exposes a risk. This creates a risk that you could provide your own sensitive data out to a public model. Therefore, it is very much on the developer to make sure that security and the level of data retention is kept in-house. Regarding SnapLogic's AI capabilities, the accuracy and reliability of output is subject to hallucinations, just any AI model. The accuracy is no better or worse than any other platform. In some ways, it does help with the prompting and helps make a better prompt, which will give back better data, but it is no better or worse than ChatGPT.

From our development perspective, we have requested SnapLogic to enhance their SnapGPT to be friendlier, improve documentation capabilities, and enable more Cursor-based type development. While not all developers are fond of the current environment, SnapLogic has been responsive to our requests for improvement, often providing fast solutions for testing and implementation. Additionally, we wished for a better implementation of the GitHub integration, as the existing method resembles older practices, where pushing a pull request involves pushing an entire package. Fortunately, they have implemented new features that allow us to be more flexible in this regard, but we still desire the ability to manage multiple folders more efficiently rather than having to create a separate repository for each folder.

Areas for improvement for SnapLogic include enhancing the documentation, especially by providing more complex examples in each Snappack, to cover various use cases that different team members may encounter. Another improvement I suggest is enhancing the monitor page on the dashboard to allow quicker and more efficient access to historical data, as it currently becomes slow and sometimes hangs when accessing older data.

More native support, particularly around the Agent Creator AI agent tool, would be beneficial. Expanding to have native Anthropic support would be beneficial for our organization specifically. More native support for other large-scale LLMs such as Anthropic would be helpful. Additionally, more training to address the learning curve would be valuable. However, there is a good amount of information in the knowledge base, and Snap GPT has been extremely beneficial.

SnapLogic can be improved. My only initial suggestion is that the AI agent is a little overly friendly. That is the main thing for now regarding needed improvements. There is some confusion in the documentation, but the overall product seems very good, and those are the additional improvements I would like to see in SnapLogic.

I think SnapLogic could be improved if the Snaplex has a way to change for people that want to write code, or to convert code to the Snaplex. There should be a way of switching the Snaplex into a base code so that you can add to the code and then save it, which would then be converted into logic on the front end. Having an alternative code injection into each Snaplex would be beneficial. For instance, in the Dynamics search Snaplex, sometimes you might want to search and filter by other entities. Right now you need to connect other entities together to accomplish that, but this should be possible if you have a way of injecting code and making SnapLogic run through the code and calling both entities together and doing the filter and pumping out results to be used, rather than each Snaplex doing only one thing.

SnapLogic currently offers SnapGPT with more capabilities compared to earlier versions, but there is still room for improvement compared to other AI tools, particularly in areas such as viewing historical data and automatic file reading which would be very useful. The interface still has options for improvement. While it has been enhanced in recent versions, it is often difficult to identify snaps when developing large pipelines, requiring a lot of zooming. A simpler option to see the snaps would be beneficial. After execution, it is challenging to know how much data has been processed, and there is a need for better AI integration since it lags behind other tools.

I think that the biggest improvement needed for SnapLogic would be the learning curve. Without the use of the GPT, I think we would have really struggled as a business to adopt it. I think it is essential to provide more training opportunities that are offered as part of the package that comes with buying the tool and having the contract. When we asked about having learning materials and training materials, it came at an extra expense on top of the existing price for the tool. In reality, if you had a more mainstream tool such as a Databricks or a Microsoft tool, that documentation and training would be public for you to access because there would be many things on Reddit or other platforms that people have posted. I know that Microsoft does offer free training material. I think there would be wider availability of training resources that do not rely on the GPT to support it as part of your package effectively.

There should be documentation for advanced integrations that would definitely help beginners. When complex data migrations are involved, if the documentation is provided in SnapLogic, it would definitely ease new joiners and beginners to look into that and build those complex integrations. One thing is that we are using Claude AI. To connect to Claude AI, there is an MCP in place in SnapLogic, but the documentation, examples, or use cases would definitely be helpful for us to use Claude more efficiently in relation with SnapLogic.

SnapLogic could improve its notification system. When a pipeline fails, the notification sometimes comes back as not very useful. I had a recent case where it just told me that a snap had failed unexpectedly without providing any reason, which is not helpful for troubleshooting, especially on the live system. To resolve this, I had to manually validate the pipeline to find the issue, which allowed me to see the data running into those individual snaps and what the error was. I would like to see if the execution can show the data flowing into those individual snaps and provide the same kind of error that I receive when validating, as that would be much more useful. I would give SnapLogic a higher rating if the error handling and notification were more specific and user-friendly to read. Apart from that, I do not think there is anything else that I can identify.

There are a few ways SnapLogic can be improved, as there are some UI quirks that I have personally noticed. For example, we use a lot of SQL queries in our Snaps. Sometimes they are very long and complex, and it is a little difficult to work with the SQL text files in those Snaps because they do not have a lot of text editing capabilities. They do not allow you to add new lines or line breaks of any kind, so often I end up using another text editor and pasting long text snippets of SQL queries into the Snap. That is a little frustrating. In addition, I would say they are going through, or they might be at the end of, a pretty significant UI overhaul of their designer app, and there are still some issues occasionally or buggy behavior when you are dragging segments of pipelines around. Sometimes they collide or they think they are colliding when they do not appear to be visually. Other than that, every once in a while I have issues with their JavaScript expression library and what is allowed to be used there and how it evaluates or shows me previews of the results. There are occasional bugs there. Overall though, I have been impressed at how responsive their team is to our issues and they are really willing to hear our feedback and look for ways to improve.

They can enhance the error handling and debugging part. Troubleshooting complex pipeline failures can be time-consuming. We are spending a lot of time on error handling. More detailed error messages and root cause analysis tools can be added, which will definitely improve the developer experience. In the Ultra real-time integrations, we can monitor the last execution history of only 100 runs. That can be increased, which would be one of the platform improvements that can really be taken. However, they are doing very well because lots of ChatGPTs and AI assistants have been added in the last two years, which makes a very good effect. SnapLogic is the only platform that provides this kind of visibility to the developers. Anyone, even if they have low experience and are starting their IT careers, can directly jump in and learn SnapLogic. The documentation is very easy to learn. Anyone, even a layman, can refer to that documentation and go through its Snap-pack to understand what configuration has to be done to use this Snap-pack. This makes SnapLogic definitely exceptional in the market. You won't find such comprehensive documentation in other iPaaS tools. The draggable packs truly demonstrate its power in usability. Governance and security are also well in place in SnapLogic, but there are areas for improvement. They can add more granular role and permission controls that provide greater flexibility for large enterprises. For example, if you have to provide access to 70 users in one shot, that can be improved. More improvements in policy enforcement capabilities are possible as well. SnapLogic can improve the data lineage part to achieve better end-to-end visibility into data movement. Also, during validation, we can only see up to 2,000 records currently. They can increase that from 2,000 to 20,000. They can put more visibility on costs and resource visibility, with better reporting on platform usage, processing consumption, and cost optimization opportunities.

One thing I do not like about SnapLogic is some of the pre-built snap packs. If I want to integrate with a new system, I have to pay to get access to those. There have been a couple of instances of just different account types that I was not able to get working within SnapLogic and had to use a third party to get that data. Generally having to pay more to get access to the full feature set is a downside. Regarding SnapLogic's AI capabilities, I find that the AI capabilities for the most part are locked behind pay, and I have not purchased many of them. I do use SnapGPT occasionally and know some other teammates who have recently gotten access and have not used the platform before tried that, but as we reviewed the pipelines that it built, they were not exactly great and we had to go through and fix a lot of things for them. It is nice when I am developing and trying to figure out an expression, as it is generally quite useful, but I cannot really speak much to the security and governance portion of it. Regarding SnapLogic's AI capabilities, I think its accuracy and reliability of output are quite good with the expressions, but in my limited experience, the pipeline builder portions of it have not been great.

SnapLogic definitely needs some kinds of improvements as per the current market and current AI world and current technology. At this moment, I can say there is one feedback on how SnapLogic can improve. There is a very small example: in SnapLogic, if we have to whitelist so many IPs, then you have to go one by one and add IPs manually. There should be some kind of a mechanism so that it can take input from any CSV files or something so that it can do bulk uploads. The IP whitelisting is the area that SnapLogic definitely has to improve. It is a bit painful because if you want to whitelist some Salesforce IPs, Salesforce provides complete IP ranges that you have to go through manually. Sometimes if you mistakenly select something, then all your existing IPs that you have added are gone. I have faced this issue personally, so definitely SnapLogic has to improve in that area. IP whitelisting is currently the top area on my mind for improvement. I don't think of any other areas that need improvement right now.

We tried to leverage SnapLogic Intelligent Integration Platform (IIP) with the AWS platform, but utilizing SnapLogic Intelligent Integration Platform (IIP) towards the AWS platform has been a little complex when compared to an Azure private cloud.