The solution's API management capabilities need improvement.

I would like the ability to offer a dedicated cloud version for security. Some of our customers are uncomfortable allowing their data to go to the cloud unless there is a dedicated service just for them in which their data is never co-mingled.

Looping through complex data structures can be difficult. There should be better documentation to address common scenarios.

It's pretty user-friendly. The only thing I would possibly change is the UI. It is still very 'Windows' looking.

I know with Salesforce updating the UI like they did, it slowed it down a lot.

I like the Dataloader.io interface and usability the best. It's just too slow.

• More pre-defined functions
• More connectors
• More samples for Jitterpaks

On the whole, we're quite pleased with it. There's nothing that comes to mind in terms of what I'd like to improve.

The initial setup can be a little bit difficult.

You need to have some development skills or hire a Jitterbit engineer to make changes. On the flipside, we only had several minor support incidents. It does not require full time, in-house, support personnel.

Sometimes we experience disconnections and I have to close all Jitterbit programs. I have to hit the "Jitterbit Cloud Data Loader Start Services" button to reopen and reconnect to the Salesforce organization. This issue can be fixed.

Sometimes additional connectors are needed.

There is also need for:

• Temporary/lookup tables that can be referenced for data, without having to use additional servers.
• Salesforce connectors that work with the Salesforce Streaming API.
• Additional data transformation capabilities like de-duping, denormalization, and normalization.

In the past few months, there have been some server downtimes during work hours that have affected some critical scheduled integrations. Jitterbit can improve in this area.

There were some bugs in the product. For example if you run a delete query and test, it deletes the actual data.

• Debugging: There should be a better way to track variable values during debugging. The need to print each log is frustrating when you encounter issues.
• There should be a way to inspect the files going to 'temp storage' on the studio.
• The variable search should be improved with the ability to click and go to the results in the search.
• The console monitor should be easier to filter. There are better ways to filter data than typing in the filters in the search bar.

At the time, the scheduling and error handling left room for improvement. The execution of scheduled tasks was less reliable than it could be.