TIBCO Integration (including BusinessWorks and Flogo)
Likelihood to Recommend
Salesforce
Dataloader is an incredible asset for a large organization or an organization that has a robust Salesforce environment. Specifically, Dataloader has allowed our sales team to focus on driving sales while our operations team can load the data they need in a manner that allows for robust reporting and tracking on our sales process. Organizations with less robust Salesforce environments or Salesforce environments in which many people are expected to maintain their own information likely do not need Dataloader.
In BusinessWorks it is quite easy to develop applications and monitor where as it is not similar with Scribe. The data which successfully processed in Scribe is quite difficult to view. I think the Scribe console tool should have better view for the data it has processed.At times we founds some of our sales orders are missing which are unable to update/insert in the DB, after investigation found the issue is in Scribe tool. A case has been raised 02129657 for the same and as per the guidelines from the Scribe support engineer we did changes in the shutdown interval to zero. ''update SCRIBEINTERNAL.SCRIBE.KSYNC set keyvalue= 0 where KEYNAME = 'SETTINGS.SHUTDOWNINTERVAL''. Later this change we started getting alert emails like ''Fatal error 325 occurred: Message processor shutting down - defined maximum memory usage (900MB) exceeded. Please contact Scribe support at support@scribesoft.com if this problem persists''. We found this issue is a critical one as the occurrences of it is decreased but still it is persist.
Extracting Salesforce attachments in original file format! I do not know of a tool that can do this better, or more efficiently! This is a huge benefit to companies that would like to extract attachments from Salesforce for tasks like data migrations.
Cross-object data extract within one file. You can pull data from related objects as long as there is a populated lookup from the object you are extracting, to another object (Child or Parent).
UI is simple and requires very little to no training. Given the acquisition of Mulesoft by Salesforce, I would not be surprised if DataLoader.IO is rolled out as the new global data loading tool for Salesforce.
The UI is easy to navigate and map flows are intuitive and easy to build upon after some basic training. However, a user should have some basic knowledge of writing nested statements.
Very responsive customer support.
The debug feature is a great tool for troubleshooting. You can easily identify where the issue is in your flow. At each debug step, it returns the expected value, and when there isn't the expected value, you know when to modify your flow.
At the moment, I can't find a way to rename jobs. This would be useful to organize what was previously created hastily by techs in a rush.
A preview of the job, especially upserts, would take a great deal of stress away from some of us (especially those who are not so confident in their ETL practice).
A native vlookup equivalent may be a welcome addition.
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.
It is easy to use and doesn't require a security token, so I enjoy using it. It also doesn't require any download or installation, which is sometimes a blocker to gettingthings done if the company has limits. also, the dataloader.io is easy for other people to pick up, so others can have visibility into the data jobs that have occurred
We are deeply entrenched in using Tibco Scribe capabilities, and we are only expanding our usage. It would be one thing if we used it only for a one-time data load, but we have several Scribe maps running constantly, keeping business-critical data up to date. And the ease of use for the occasional, mass data update or upload is simply icing on the cake. I'm a big Microsoft fan, so there is potential down the road to convert our Scribe data integrations to Microsoft Flow (or Power Automate as it is now called). But for now, the functionality just isn't there with Flow (Power Automate), plus the work involved to change all our current integrations would be a large undertaking. So for now and the foreseeable future, Scribe will remain our data integration tool of choice.
It is an intuitive application to use. Within a few clicks, you can be signed in to your org and ready to perform tasks. Data imports/exports/updates are streamlined so you can quickly start and configure your jobs. These can run in the background while you set up new tasks. Job history and tasks currently running on are on your home screen.
As mentioned in the previous sections, setup and maintenance is extremely easy. We don't have many issues for which we need support and there is no need for deep technical skills to use Tibco Cloud Integration platform. The solution provides everything we need for our specific use case, being the replication of our Microsoft Dynamics 365 CRM data to our on premise database for reporting.
We have not had any issues with TIBCO not being available when needed. I have only had to contact support less than 5 times in about 5 year time frame due to syncing issues or a problem with the agent. Support is very quick to respond as well as very helpful.
TIBCO Cloud Integration (including BusinessWorks and Scribe)'s performance of the user interface are not to be complained about. The user interface is swift and is a pleasant user experience. The replication jobs take some time to finish but that is because the number of records to be updated/created on a daily basis is quite big. I did split up the jobs between highrunners (entities with a lot of changes) I update on a daily basis and quite stable entities that I update weekly. That solved my issue of a way to long replication.
Customer support might be where Dataloader.io saves money. Most of the competitors offer 24/7 live support but Dataloader.io only offers support via email and the community. Those types of support work fine until you need an answer right away. Some questions can't wait until the next business day or business hours for a reply.
For creating new process, you have lots of palettes to do every develop you need. For created process it is easy to understand even if you have ever seen before it. You can analyze your process in all their detail. User Experience is positive for beginner and expertise people. Just debug mode is still raw, but better in TIBCO BusinessWorks 6.x than TIBCO BusinessWorks 5.x .
Before using TIBCO Businessworks, I participated an official training with a specialized instructor. In this training, I learned what I needed to know to build some applications or web services and how to manage its. It was been very important to me. I understood many technical stuff to familiarize with this powerful platform. I can advice TIBCO Educational Services.
If we don't design the process correctly, it can do lot of damage (like deleting files or data etc.,) and might assume product issue rather than a design flaw. So it is always recommended to do thorough unit testing , QA and a design review even for a small process to avoid major problems.
I have used salesforce inspector also for operations like import and export of data from custom objects but it doesn't work well when you have data in huge numbers. Instead of using Salesforce Inspector, one should go for Dataloader.io if the number of records is huge to be dealt with.
Used TIBCO for migration of our data for our learning management system.TIBCO, succesful Content ,data migration(courses, classes, registrations, transcripts etc.) ,User migration(Internal users and Partner migration)and Report migrationIntegrations with different applications Workday,Single Sign-On,CertTracker,Okta,Partner contact sync and Questionmark is succesful.LOD: Learn on demand is a third party vendor application where all Virtual classes are delivered by the vendor application. Learning management system sends the class and registration events to learn on demand via real time web service call through TIBCO
We could easily add multiple agents and new systems. This had no impact on the performance. We had some issues because flows cannot be splitted and called by each other. So you have lots of flows which are the same. It would be great if this was improved. Also transferring values via variables between flows seems to be impossible. You can only use global lists with dictionaries.
HUGE time saving. When we need to clean or review data, we used to have to do it line by line. This can do the work within excel and make cleanup/management an afternoons work as opposed to a week.
Rollback what you did/change/deleted is relatively simple if you remember to back up the data you are manipulating.
