Appian vs Winshuttle

• I have observed after version 17.1 we have a lot of good features in Appian that improve usability (UX). This adds real value in this competitive Digital space.
• You can understand business use case and convert it to a logical process automation.
• Process Modeller has improved a lot and providing smart services use adds more value.
• Service integration helps us to seamlessly integrate with third-party systems

Read full review

• "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.

Read full review

• Advanced functionality requires use of the Appian expression language. The more advanced the logic, the harder it is to build with the expression language. This means development expertise is more relevant if you need advanced functionality, which I imagine applies almost all the time. I would much prefer if they allowed some common language such as JavaScript out of the box.
• Debugging has proved difficult. It’s easy for developers to get the app to or feature to a “working” state but it needs robust alpha testing.
• Deployment can be tricky. When a solution gets big and there are many teams and dependencies, it needs a careful process to ensure things don’t break.
• Reasuability of Appian objects is both a pro and con. Reusing objects across apps may be more trouble than its worth because of creating heavy dependencies. Experience is helpful to strike the right balance.

Read full review

• 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.

Read full review

• Our objective to reduce customer effort when dealing with government by 25% was exceeded. In the process of applying for an alcohol licence renewal alone, we saw approximately 80% reduction in time and effort for the business customer - and that was just a prototype! Imagine the possibilities when this is taken into a live environment!

Read full review

• We've been able to automate several time consuming, high volume tasks so that our analysts could focus on actual data quality and not data entry.
• We've been able to create reports and forego custom IT configuration by using Query and Transaction to come up with our own solutions.
• We've been able to pivot our strategy more quickly by easily adjusting and updating master data when processes change.

Read full review