Time-intensive and wasn't tailored for our business use
June 11, 2019
Time-intensive and wasn't tailored for our business use
Score 4 out of 10
Vetted Review
Verified User
Overall Satisfaction with TIBCO Cloud Integration (including BusinessWorks and Scribe)
The integration team and one person on the engineering team mainly use Scribe. Scribe is used to automate data from our customer's ERP systems into our proprietary data platform. We want to automate our data on a consistent basis so that customers can use our data platform more, without manually going in there and uploading data.
- Scribe Labs documents our ETL work in a very concise manner.
- The User Interface has a nice-looking design.
- We can export files to Dropbox.
- Installing the agent is a quick and easy process for on-premise.
- The Net Change feature is good.
- Missing functionality: We like to run all the files available in the FTP when clicking the run button. Right now, we have to click the run button several times (or have multiple solutions) in order to run files from our FTP site one at a time.
- Generating column fields every time a file changes from the source in the FTP is very tedious. Working in integrations makes me have to go back and forth a lot of the time, and doing this is incredibly annoying.
- The security is horrendous. We installed an on-premise agent on the customer side, but we don't want them even touching the ETL tool at all. The only knowledge we are fine with knowing and being able to see is that they installed the agent, not the solutions themselves.
- Our company's connector would have to point to the dataset name rather than dataset ID. It was very frustrating because we change the dataset name a lot, and then we'd have to repoint it.
- It's very difficult to monitor the different integrations that go on because there isn't a consolidated dashboard.
- Whenever there was a Scribe outage, all of our customers were affected and didn't have integrations for a day.
- There wasn't a way to trigger a support ticket only for certain Scribe errors- no customization there, so there was no automated way to escalate certain tickets if need be.
- Going back and forth on generating field schemas for our FTP customers, was time intensive.
We are currently using SnapLogic and it's significantly better for our business usage. It's faster because we can just create an integration workflow and copy it with each of our customers. In Scribe, we'd have to generate a field schema, set up the same solutions, etc which is burdensome.
We have a lot more customization now with SnapLogic to create those support workflows. And, if there is an issue with our proprietary platform, then we can just shut off all the automated integrations in a click of a button. In Scribe, we'd have to go through every single organization (which represents a customer) and manually turn them off.
We have a lot more customization now with SnapLogic to create those support workflows. And, if there is an issue with our proprietary platform, then we can just shut off all the automated integrations in a click of a button. In Scribe, we'd have to go through every single organization (which represents a customer) and manually turn them off.
- In-person training
- Self-taught
We had a lot of different training sessions. They were awful. The first time we had in-person training, I felt like the guy was just trying to prove how smart he was, and wanted to go super quickly. The second time we had in-person training, it was a little better. However, two traits held in common for these trainings were that they didn't seem to customize it well for our business use-case. With our company, we have over 200+ customers on integrations. We want a way to monitor and there was no hope in the future to be able to do that.