Reviews (1-25 of 212)
- 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.
Not suited: Having many customers (being able to monitor them all effectively). Wanting a lot of customization. Wanting a lot of security. Wanting to minimize the amount of time it takes to go back and forth on integration solutions.
- On premise integration solution. It provides a way to integrate to any on premise solution with a secure connection to the cloud via the Scribe agent.
- It supports any kind of source connection. Which means it can be used to provide a solution for legacy products that do not have APIs that can be used for integration.
- It provides a fairly intuitive workflow for building integrations that lowers the technical overhead required to build an integration.
- It does not provide a great solution for high volume, multi-threaded integration problems.
- It does not handle a JSON source very elegantly requiring (last time I checked) a flat single level JSON structure.
- Building integrations can become a bit bulky. It needs to provide a solution to build integration workflows in smaller chunks.
- Error handling could definitely be improved.
It is not so well suited for modern integrations and in high transactional use cases. If there was a bigger marketplace it might make it more compelling.
- They have a large collection of existing connectors that allow for quick integration in almost every case.
- The UI for building maps is competitive with any top shelf ETL tool on the market.
- The ability to run maps in the cloud or on premise, or in a hybrid environment is incredibly enabling.
- The sandbox environment makes it easy to build and test maps before hitting a production environment.
- This should probably be higher up the list. But the error tracking and reprocessing of trans, and detailed error information and download ability is invaluable.
- There are connectors that are either missing or are using a subset of the API's functionality, though most of these can be overcome using their generic REST connector.
- Debugging is great. But is also some limitations that should be addressed.
- There are number of places where a developer is presented with error messages that need to be ignored, or in some cases can require the user to close their browser and reopen. Some of these could have been addressed since I ran into them.
- Notification services need to be extended to provide information to users externally without creating an account for them. This is particularly useful for SaaS integrators who are doing the work on behalf of their clients.
- The setup of both the sending as the receiving side is easy, you don't really need expert skills to set up the "technical" part.
- We don't need a complicated ETL tool to extract the data from the Cloud environment.
- The overall management of what needs to be synchronized is straight forward.
- Thanks to the specific SCRIBE fields in the receiving database we have a track of deleted records (for which we don't have anything in the CRM database).
- The synchronization is not fast and seems to do some unnecessary work.
- Selecting the entities to synchronize is quite tedious, you need to scroll through quite a big list (especially when you have a lot of custom entities) a filter would be welcome.
- You need to manually update the metadata of the sending connection to see newly created entities, it would be nice if you could schedule those tasks too.
- We already had quite some situations where MS changed things in the data model of CRM that caused issues in the sync tasks.
When you need more specific control (field level) of what needs to be synchronized, you need to look to a more specialized tool to do the data integration.
Scribe is great point and click tool, but also needs advanced knowledge for even mildly complex integrations
- Point and click configuration and solution development - no code speeds up deployments
- Easy procurement process with training
- On the fly changes and updates make implementations flexible and easy to update
- Excel and text file plugins, connections and clients need some work to improve ease of use and complex integrations
- The internal TIBCO sales/renewal/support/training teams need to break down silos and talk/work together to provide a better comprehensive service for users
- Price needs to be more competitive and lower along the lines with similiar product
- Easy to use UI - self explanatory formula builder with lots of built in examples saving time searching for it in a Knowledge Base
- Powerful range of out of the box connectors for popular vendors opening up lots of migration tools and integration options
- Extensive API for building integrations around existing apps such as CRM and ERP
- Not always clear how you will integrate on premise solutions with cloud solutions, it appears easy with the "on-premise" agent but sometimes lots of hidden infrastructure is needed in place to make it possible
- Ad hoc updates and corrections to cloud based data sets that do not provide SQL type bulk update tools.
- Regular scheduled data integration tasks that can run overnight or even hourly.
- Microsoft Dynamics 365 support is strong - allowing things to be done that Dynamics does not allow such as modifying order line items in a workflow.
- Data integration tasks can be triggered through API calls for near real-time updates and data synchronization between disparate systems.
- We can only work in Scribe for a couple of hours at a time before things slow to a crawl. Closing and re-opening your browser restores the speed.
- Triggering Scribe Jobs from Dynamics 365 could use better support via a D365 add-in solution from Tibco
- Testing and trouble-shooting Scribe jobs is slow and cumbersome. It would help to have a "window" into all fields in a record instead of just those that are explicitly used in a job.
- Tibco EMS is a very fast and robust solution to assist in processing a huge number of messages and guaranteeing a very high throughput.
- Ease of deploying a Tibco BusinessWorks project from development to production. It is almost zero deployment time.
- BusinessWorks designer is easy and intuitive to use.
- low code platform and therefore much reduced time to market
- TIBCO has a very strong innovation wing together with strong presence in the market
- With Tibco container edition,we can easily build cloud native integrations and take advantage of micro service architecture
- SFTP - currently TIBCO has no palette for performing SFTP operations. We have to write custom Java code which does the SFTP operations and then call the Java code from TIBCO.
- provision for a palette for performing smpp connections
Less Appropriate scenarios:
- Calling a target service which has no properly defined soap action and has generic schema APIs- this requires a lot of XSLT transformation and calling the target API using send HTTP request palette.This is quite complex and requires quite some skill in Tibco and may not be achieved by a junior developer
- Easy to implement and customize.
- The solution is fully integrated between SugarCRM and WCA.
- Fast and easy to debug.
- The placement of the GUI interfaces can be confusing.
- I'd rather have a split window screen (menu left and edit right) when editing a block property.
- Easy to use drag-and-drop integration design and testing in Scribe Online.
- Clear and visual indications of integration errors or failures.
- Best suited for one-off data migrations or high-volume complex integrations that could be broken into smaller chunks. Otherwise, speed suffers.
- It's not yet able to handle API to API integrations with ease.
TCI is a PAAS solution that helps customer to achieve important goals.
- Cloud solution (Paas).
- A simple method to implement agile solutions ensuring continuous integration.
- User-friendly implementation by using TIBCO Studio.
- Missing functionality: mutual authentication, missing of Oauth2.0.
- Missing monitoring of the performance of applications.
We use Scribe to transfer data between multiple systems. From our account/contract system to our CRM system, as well as from our CRM system to another database.
Scribe plays a major role in making sure we have data integrity across multiple systems. It allows to avoid manual updates of data between system, which is crucial when we have limited staff. This allows staff to focus on other job duties.
- The creation of integration maps is straightforward.
- The ability to schedule when solutions are run is of great value because we need to have systems updated in a particular order. Scheduling makes this easy.
- When errors do occur, the error messages give enough information to allow us to diagnose how we need to fix records as necessary.
- The system could be a little faster when navigating within maps. Sometimes there are delays while the page loads.
- There could be more examples of how to use Scribe in the documentation.
- I would suggest that Scribe provide suggestions when sending error messages eg Have you tried to refresh the metadata? This would save contacting support for some people.
Off the top of my head, I don't have any scenarios where it is less appropriate because if you want to move data between two systems, Scribe is one of the best options.
- Easy to use visual mapping blocks
- Able to schedule nightly integration runs
- Lots of controls like "if Else" and "looping" that allow you to create complex data creation and manipulation
- Unlike Salesforce, Dynamics has more restrictions on updating closed records like Cases, Opptys, etc. It would be helpful if there were pre-created maps available that helped with the data manipulation steps required to update these records.
- It would be helpful to have better error messages. Sometimes it was very hard to troubleshoot failures.
- Faster manipulation of data would be better.
- The field auto-link feature is extremely helpful for migrations. This allows users to save an incredible amount of time when their systems might have thousands of fields that need to be mapped.
- The UI when creating a mapping is very clear and easy to use. It took me about half an hour to learn how to set up mappings and link fields. This will allow more people to be able to use Scribe.
- The error logs for records that fail to transfer or migrate are very detailed. I appreciate that when a mapping runs, I can see exactly which records failed and why.
- The most detrimental missing functionality for me has been that Scribe Online cannot natively move Dynamics entityimage fields. We had to externally hire a resource to build an app for us instead of being able to use the Scribe instance we provisioned for our client.
- Under Execution History, I would love to see the name of my mappings. There is a lot of good detail in the Execution History list, but showing the mapping name would allow me to quickly at a glance see what mappings I've already run and which I haven't.
- I'd like to see it be a little easier to delete organizations. Having many clients with various organizations in Scribe, there are some orgs created by accident that I wasn't able to figure out how to remove without researching it.
- Centralised administration of all integration solutions. The ability to sign-in once and quickly administrate and develop across multiple sites is just great.
- Easy modification when changes are required. Customer requirement change all the time, with Scribe you simple make a small few changes. Integration changes no longer mean a full release, customer code etc.
- Support for many connectors - We haven't yet had a customer where a connector isn't available, the local agents are great where clients are still on premises.
- Easy Debugging - The validation means that most things just work, but when you do hit a problem the step by step debugger is so useful to quickly identify where the problem lies.
- We have one situation where we required to use REST and a bearer token. While Scribe used REST it didn't support bearer token. This needs to be added.
- History logs just disappear after a period. Sometimes you may only run a job every few months, could we just keep all logs. Also sometimes you make a mistake, as administrator could I just be able to clear any log if I need to ?
- Query runner - When we have clients with a local agent we often don't have access to their system (eg; SQL Server). We can build a integration to run a custom query and preview it, but it's clunky to do. Couldn't we have a query window so we could send native queries via the local agent and get test results.
- Set it and forget it mentality for constant replication
- Warnings of system interruptions or other issues quickly identify problems
- Modifying solution on the fly easy via dashboard
- A couple lingering support issues not resolved after months, have stopped trying and now "live with it"
- Not much else; when it works, works fine. Sometimes variable speed in synchronizing is frustrating but usually doesn't last and not worth engaging
- Fast - It only takes a few minutes for the data to be sent over to our other system
- User Friendly - Not hard to navigate or use
- Great Customer Service- Whenever we do have a problem they are quick to address the issue
- Notify us when updates are done. There was recently an update that affected our entire system and we were unaware. I had to reach out to our contact in order to find out.
- Simplies the process of reading data
- Increases productivity by passing the buck to purchased software versus in-house development
- Secures systems by setting up particular users to manage the system
- There are too many "Scribes". We have Scribe Insight and Scribe Online. Both require considerable ramp up time.
- With Scribe Online, we can only choose notifications based and organization names. We would like to also tailor notifications based on subject of email which in 2019 is unavailable.
- "View All" and "items per page" model always resets.
- It's extremely simple. I am a Salesforce admin, so not a dev/IT personnel and I can manage solutions and build maps on my own.
- It's transparent. I have an overview of everything.
- I can set it to any schedule that fits our org's needs.
- Integration solution doesn't perform well on bigger loads. Queues start piling up and records can't be processed.
- Support is not very simple to reach.
We are a consultancy company that recommends Scribe to our customers based on the project requirements.
Generally for integration between Dynamics CRM/365 and Dynamics NAV
- Fast and reliable connection & setup between platforms.
- Low skill requirement for the development of a migration, integration, or replication map.
- The Scribe Online platform has stability, availability, and performance.
- (Scribe Online)Troubleshooting and debugging require more features and decent logging of error messages.
- (Scribe Online)Advanced technical Scribe users expect more functions and tools for complex integrations.
Don’t use it when Enterprise failover requirements are in place. This is (almost) not possible.
- less cost prohibitive than other similar tools. most connectors are included with base cost
- fairly easy to learn and implement
- generous enterprise licensing model
- not strong with complex orchestrations (e.g. orchestrating realtime and batch sequencing)
- no option to extend integrations with scripting when declarative drag and drop blocks fall short of need
- doesn't support movement of files/media
- exception handling is not great
The product is not well suited for moving files. It's disappointing this product can't work with Salesforce files/attachments. It is disappointing this product can't download a file from an S3 bucket. I would request more capabilities around moving files in general be considered in their roadmap.
- Easy to access and manage since it is a cloud-based solution
- Easy to use and understand
- Provides good debugging and troubleshooting tools
- Available templates for existing integrations to help provide a good a starting point
- TIBCO Scribe scales very well with the requirements. Everything from small migrations to complex integration scenarios can be done.
- Adapters/Connectors for many, many systems available
- Cloud or on-premise solutions can be implemented
- System performance depends on source and target systems, but a little more flexibility in tweaking options here would be great
- I would like to see TIBCO Scribe Insight weighted with the same development priority as TIBCO Scribe Online. Especially concerning support of new software versions, new connectors, UI/design improvements etc.
- Price point - Lots of features for the price point -- perfect for mid-size companies.
- Excellent Support!
- Handles most situations well other than CSV files.
- Ease of use, being able to reprocess the errors, handles SF bulk processing well.
- CSV file handling -- difficulty using the CSVLOOKUP function.
- Can't put NULL as a value, for example, a Date. When using Jitterbit I can put NULL into a date field. So instead I have to check the condition first, and then make basically a duplicate of the map without the update of that one field.
- Similarly, can't update a lookup field unless I know that ALL rows have a value for that lookup field. Other integration tools handle this.
TIBCO Cloud Integration (including BusinessWorks and Scribe) Scorecard Summary
Feature Scorecard Summary
About TIBCO Cloud Integration (including BusinessWorks and Scribe)
TIBCO Cloud Integration (including BusinessWorks and Scribe) Screenshots
TIBCO Cloud Integration (including BusinessWorks and Scribe) Video
TIBCO Cloud Integration (including BusinessWorks and Scribe) Downloadables
TIBCO Cloud Integration (including BusinessWorks and Scribe) Integrations
TIBCO Cloud Integration (including BusinessWorks and Scribe) Competitors
|Basic||Starting from $400 per month, billed annually||number of connections|
|Standard||Starting from $1,500 per month, billed annually||number of connections; includes additional functionality|
For more details, see https://www.tibco.com/products/cloud-integration/pricing-plans
TIBCO Cloud Integration (including BusinessWorks and Scribe) Support Options
|Free Version||Paid Version|
|Video Tutorials / Webinar|
TIBCO Cloud Integration (including BusinessWorks and Scribe) Technical Details
|Deployment Types:||On-premise, SaaS|
|Operating Systems:||Windows, Linux, Mac|