Planview Hub vs. UiPath Integration Service

If used correctly in the hub/spoke model it can be very effective. If not implemented in this manner, it can lead to a lot of customizations to accommodate.

Incentivized

Areas where it would be appropriate:

1. If you want a really 'deep' integration with a third party software, and you want all the control over how it interacts with your software
2. If you want a totally white-labeled solution, that is totally invisible to your customers.
3. if you care more about a well thought out/useful API, rather than a pretty UI

Areas where it is less appropriate:

1. If you want a Zapier-esque hands-off integration for YOU.
2. if you want your customers to do more of the work, pay for it/etc.
3. if you're a really small business, it could be too expensive. But it depends on your individual contract with them.

Incentivized

• Allows for one- vs bi-directional field flow which is useful per segment
• Allows for the relationship mapping of Parent/Child cards
• Allows for customization of mapped fields

• Customer Support -- They have a knowledgeable team and are very responsive.
• Communication -- Most questions are addressed quickly
• Documentation -- The API documentation is well organized and easy to follow.

Incentivized

• I'd like to see more robust reporting capabilities available from the UI.

Incentivized

• There weren't really many cons to our experience. The only slight downside was the cost but they worked with us on that to make it work.

Incentivized

Planview TaskTop Hub supports our use cases. I think its continuous development goes in the right direction.

Incentivized

A great integration tool, which comes with a wide range of supported end tools. Planview TaskTop Hub works with an integration concept that maximizes the scalability and flexibility of integrations across more than just two tools. For example, from our experience, we started with the integration between Jama Connect and Jira. We were able to extend our integration concept to a new tool, Pro Cloud Server, by ourselves. The element was synced within 10 minutes.

Incentivized

We're hosting Planview TaskTop Hub by ourselves. The availability was good until now. A part of that, we have a strict plan for the quality control on any update of both Hub and End tools to avoid as much as possibily any disruptions.

Incentivized

Planview TaskTop Hub does generate traffic for some end tools. It is still in an acceptable range. For certain kind of retry to resolve issue in synchronizing relationships, an additional manual attention was required.

Incentivized

I was considering giving a rating between 9 and 10. Overall, the support has been very good so far. However, I have noticed that the members of the support team have varying levels of know-how about Planview TaskTop Hub. When a ticket about a complex technical issue reaches a member such as Christoph T., Sr. Customer Engineer, the analysis is done thoroughly, and a sustainable solution is provided. With other members of the support team, the experience might be different.

Incentivized

We've received a good, in-deep training from Christoph T. during the implementation phase.

Incentivized

The integration documentation was sufficient.

Incentivized

We had a very good collaboration with the enabling team from Tasktop in 2018. The enablement program was adequately structured, starting with building an integration concept based on use cases of the synchronized data. The training provided a good foundation for us to operate and maintain the tool. The tool administration and architecture were straightforward.

Incentivized

N/A - We have not used or evaluated other products similar to Planview TaskTop Hub

MuleSoft is also a similar product to Cloud Elements, but is not available as an option in this form.

Workato and MuleSoft are competing cloud API connector platforms that perform a similar function to Cloud Elements. We chose Cloud Elements over them because CE provided a more robust path to unifying the behavior of connected systems.

Zapier is a workflow automation tool that I feel draws erroneous comparison to Cloud Elements that I need to highlight. Workflow automation tools (Zapier, IFTTT, Microsoft Flow) do provide multiple integrations, but for simplistic scenarios where only a handful of explicitly described steps need accomplished. Cloud Elements is a platform for developers to deliver faster and with higher reliability than making integrations one-by-one in complex systems that solve demanding problems.

Incentivized

We don't need to deploy Planview TaskTop Hub in other units but we could extend the integration to cover the new data, new data type and new projects.

Incentivized

• It is a little expensive but seems to be acceptable costs for what it does.
• It allows us to integrate better the whole set of systems used in software development.

Incentivized

• We are able to build integrations in HALF the time we could build them from scratch.
• They allow our development team to spend more hours focused on developing our core product, not connections to other products.
• Their large catalog of services to connect to allows us to spend much less time researching other platform integration endpoints and increases our R&D speed a considerable amount.

Incentivized