Nintex offers a platform that helps companies discover, automate, and optimize business processes.
$480
Minimum 1,000 users per user
Winshuttle
Score 9.1 out of 10
N/A
Winshuttle is an SAP-focused data management and robotic process automation platform. It is designed to enable the building and adaptation of Excel and SharePoint-based interactive forms and workflows for SAP without programming.
We use Nintex to automate fundraising outreach at scale. It helps us send personalized emails to a large contact list, and we’d also like to automate follow-ups when there’s no reply. If you need highly customized solutions or clean, fully controllable code, I wouldn’t recommend Nintex. It has many features, but it’s not the same as building your own system from scratch. That said, it can save a lot of time for standard automation workflows.
Winshuttle is well suited to help any company who has data that needs to move from SAP to 'somewhere'. The output file can be Excel, Text, or Access. Query has been greatly expanded in its ability to use SQL statements directly in the product at the 'pre-download' point. For example, you want to have one column do calculations on the data that is being pulled out of SAP via the Query and placed in a specific cell - this can be done - right in the Query script and the result will be produced in your receiving Excel file. I have another small scenario I call 'On the fly" uses. When our asset team had to change their depreciation on a very large number of assets mid-year, Winshuttle Transaction was very helpful. The update would have taken DAYS and lots of shredded nerves to update.
Integrations with other services using various secure authentication methods, along with the seamless integration with SharePoint, are the icing on the cake. This makes it superior to other BPM tools available in the market.
Flexibility in application development - The diverse configurable properties offer multiple ways to utilise the controls and events, affording the flexibility to expand your scope and enabling the creation and use of processes in a myriad of ways.
The streamlined and efficient deployment process significantly accelerates release management, allowing for faster and smoother implementation of updates and new features.
The user interface of the pages offers a more refined and appealing look and feel compared to most other BPM tools.
"Training" I feel Winshuttle was extremely easy to learn' my team and I went to a week long training class on the uses of the software upon finishing the course we all became internal (company) support as well as expert functional users.
"Ease of use" once a user learns the basics processes of the software it is functionally very easy to use and if there are problems with in the processing that cannot be supported internally Winshuttle community and support quickly helped clear up those issues, "if they occurred"
"Processes data FAST" once the transaction is mapped and recorded the user can move through (process) large amounts of data very quickly, saving lots of time by eliminating manual steps.
"Data Error Correction" through the transactional processing of large amounts of data, nothing is ever perfect, usually during data migration process if a single line fails the process stops, the correction is made to the data and the process starts all over again. Winshuttle data migration process doesn't stop it will provide a list of exceptions upon completion of the data load. It does this by only processing the "good" data and when bad data is encountered it is skipped and an error message is created and added to the data sheet. With this process the user now only has to worry about exceptions that didn't load and also knows why the line failed so making correction are easier and faster.
If you are creating a process with parallel subprocesses, there's no way to see, in a single view in Nintex, all the steps for the subprocesses. You have to view each sub-process in its own view, so it's hard to see what's going on at a high level.
There isn't an easy way to filter the processes by another user (not yourself) in Nintex. There is a report that shows processes and objects by user, but that's not as convenient. This is something that I've seen in other tools (OpenPages by IBM) so I am surprised that it is missing.
Nintex doesn't really have a way to capture iterative processes (which we have a lot of). It's designed for linear processes.
The use of Winshuttle is particularly helpful with systems where data volumes are always very high. If data volumes are not an issue, the use of Winshuttle for cut-over activities might not result in a significant perceivable difference in time savings.
For businesses and sectors that rely on business processes that are complex and tedious with a lot of manual interventions, Winshuttle comes in real handy. However, in situations of fairly straightforward business cases, it would be hard to see perceivable gains from the use of Winshuttle.
At times, the use of complex business process with multiple fields from one transaction needs to be fed into the next for further processing, if the screen sequence changes based on each set of information, the processing could fail. However, these could be overcome by grouping similar screened transactions into one chunk and others into another.
We are currently investigating which collaboration platform best suits our needs. Chances are that we move to SharePoint Online and then we're going to also consider the microsoft power platform (power automate and power apps) to develop forms and workflows. Aspecially the pricing model for the cloud is currently a blocking factor to go for the Nintex solution in the Cloud.
Fantastic tool and honestly the best out there for the particular need. I cannot think of any reason we wouldn't renew as it truly offers the perfect solution to what is often a supremely difficult process. Also, I believe that from a cost perspective it is quite agreeable given the amount of benefit/ROI received
Based on the on-prem experience with this tool, I believe that they have a lot of potential to help the online version catch up to where the on-prem left off. Nintex developed their online version and it is not as fully formed or capable compared to the on-prem version, and the licensing model scales back what we would have liked to be an expansion or at least continuous improvement of existing flows. It is also not near as user friendly specifically to non-developers and has an uncanny similarity to Microsoft Flow in the online instance. Consistent with my reviews of the tool - I believe they have some good approaches to design thinking that, if translated well from on-prem to online, could make this a clear winner again.
- I have used Winshuttle Transaction and Direct and the interface is simple, intuitive and easy to understand. - Not much technical knowledge of SAP is required before loading the data. - Data can be loaded for any sheet of an Excel spreadsheet - Output messages from Winshuttle are very clear and can be used to as an input to other data loads that use these output data
The Nintex Process Platform has never crashed or had any availability issues during my usage. However there was an issue that was of my own making that caused a slowdown of the system. I had set up a process to run once a day and check for employees on a list that had certain parameters selected, and for some reason that I had to troubleshoot, the process instead ran constantly, which filled the cache quickly. I ended up having to dismantle that process so the system didn't crash.
Unlike any other process automation product out there. Not only is it a low-code, easy to use tool for building processes in environments like SharePoint or Salesforce, they have really started to expand their tool-set by offering tools to manage other things like process mapping, RPA, mobile,etc.
The support team works as fast as they can and they are usually fast to solver the issues. Sometimes they need more time to solve one of them because our workflows and so on are more complex than usual clients.
The winshuttle staff are some of the best in the business. I have been working with them for several years and always have had a positive interaction. There support staff are very knowledgeable. There product managers are very supportive as well and always open to hear feedback on how you like the product and any gaps that you would like to find a solution to better improve the products.
I used the Nintex training software, it was easy to watch and follow along. It didn't go too fast and was descriptive enough to understand what the steps needed were in order to produce efficient workflows and user friendly forms.
1.Start with Simple Workflows: Begin with basic workflows to gain user confidence before tackling complex processes. 2.Involve Stakeholders Early: Engage business users and IT early to align workflows with real business needs. 3.Comprehensive Training: Invest in user training to ensure smooth adoption and reduce resistance. 4.Leverage Prebuilt Templates: Use Nintex’s templates to speed up implementation and maintain consistency. 5.Iterate and Optimize: Continuously improve workflows based on user feedback and performance metrics.
Microsoft environment does not have the scalability of Nintex; it is perfect for small and medium-sized companies, especially in environments where Microsoft environment is almost entirely used. Although Microsoft offers options to connect to other applications, its platform lacks the development and robustness that Nintex provides. Nintex not only covers Microsoft environments but also Google and other important platforms.
Winshuttle works better with SAP than UiPath does in terms of performance and stability. The time to deploy a Process in Winshuttle is faster and less complex. It doesn't require coding skills as much as for UiPath. Winshuttle excels in batch input operations and also has a useful query reporting tool.
The scalability is really bottlenecked by the imagination of the user. I was able to make processes for my own personal usage, making my daily tasks easier. I was also able to make processes that affected hundreds of employees, making large standardization and efficiency gains. So either way, the system is used the same way, and I was the limiting factor.
People have woken up to the amount of overlap after mapping their processes.
People can be resistant to process changes. You need to have the support from above or support from the 'business' that you are process changing to be able to see the positive impacts.
Numbers talk. if you can get a general salary figure from your HR dept to show savings for 'employee bands', then when you present reports, they will be all the richer in data.
