I primarily use Appian for digital remittance, storing information, processing transactions, and regulatory reporting, and I mainly use it for the digital remittance register.

Whenever we receive an MT103 from our corresponding bank, we upload the messages into our Appian-based digital remittance register. Appian extracts data from different fields of MT103 or even MT202, and that information is cleaned and segregated into different fields and columns. After that, we process the remittance, and subsequently, after completing the transaction, we report it to our central bank. Appian generates the report, which is quite handy and useful. My team can interact with peer members while using Appian; for example, when a maker uploads a transaction, the checker reviews it. If there is any discrepancy or error, the checker can directly reject the transaction so that the maker can rectify and reprocess it. If everything looks good, then the checker can approve the transaction directly, making it quite time-saving and reducing errors while ensuring pure compliance.

Appian is quite smooth by nature. We have used other software and tools, but most often we used to get lags and disruptions; however, Appian is quite smooth and we did not notice any major issues. The best feature would be its reliability and smoothness. While using it, we can store data, extract data, download, and generate reports anytime, which makes it quite handy.

Remittance is a crucial part of my integral operation, so any disruption would majorly impact our clients. After switching to Appian, we never faced any disruption as it is reliable and we can generate data at any point in time, quite faster than other tools in my personal opinion. Regulators can ask for data from us at any time, and with Appian, we download data from our Appian tools to share it with them whenever they ask. I would share a real-life example: a customer's transaction processed more than a year ago. Suddenly the customer came back asking for all the details. In our previous tool, it was quite difficult to generate transaction details from over a year ago; however, while using Appian, we can pull up data using different key search fields, such as a customer's cell phone number, remittance tracking number, or MT103 reference number. We shared it with the customer instantly, and the customer was surprised we could provide all the details in such a short time. It added reputational value for our organization, thanks to Appian.

You have pointed out two major things: time-saving and reduction of error, which are key points while processing remittance. Previously, while using another tool, it was quite time-consuming to process remittance, but after switching to Appian, it can extract data from MT103, eliminating the need for manual data entry. The process has become fully automated. Previously we could process only five to ten transactions within an hour, but now, after switching to Appian, we can process about 100 transactions in an hour, making it 10 times faster. In terms of error detection, since Appian extracts data from MT103, the extraction rate is quite good, and the error rate is negligible, lower than 0.001%. We can share accurate, error-free data with the regulator, which is essential for us. Appian benefits us significantly. After receiving an MT103, we check what the remitter is, the amount, if it is under threshold for processing, and if it is from a high-priority remitter or client. Since Appian extracts data from MT103 messages and identifies top-level clients from the database, it can notify us to process their transactions with priority. Due to automated data extraction, there are fewer instances of error. In our previous tool, we reported regulatory data to the central bank manually and often received complaints about invalid purpose codes due to manual data entry. Appian handles this automatically, and after switching, our error rate has dropped significantly, resulting in positive feedback from the Central Bank of Bangladesh regarding our reduced error rates. This has greatly enhanced our organization's reputation.

Appian is fully on-premises, and we have our own system.

Appian can be improved by adding a geo-location tagging feature, which would be really helpful for identifying remitter addresses. If Appian can suggest the country based on that address, it would significantly decrease error rates in processing remittance. So far, Appian is excellent, but this addition would be a revolutionary improvement.

If Appian can handle geo-location tagging, it will increase our speed by 20 times. I suggest this improvement and hope for the best.

I have been using Appian for more than two years.

Appian is absolutely stable and reliable in my experience.

We have tested Appian during peak usage and off-peak times, and we have not experienced any issues such as lagging or system disruptions. It is running smoothly, and we hope it will continue to provide us with the same support and reliability in the future.

In terms of scalability, we have not encountered any major issues. Our volume has increased by 20% in the two years since using Appian, and it can handle the increased volume effectively.

While deploying Appian, we reached out to customer support, and their assistance was great. They were very helpful, friendly, and their professional attitude impressed us tremendously.

I would give Appian's customer support 10 out of 10 due to their next-level support.

We previously used different tools such as Finastra and Oracle for data extraction and report generation. After switching to Appian, we realized we made the right choice, as it is much faster and more helpful than those tools, including some Microsoft products we tried previously.

It was really easy to deploy Appian for our organization; it is user-friendly and we deployed it without any major difficulties. Our development team thoroughly enjoyed the deployment process, and we completed the entire system rollout within 15 days, which was remarkably fast.

I was part of our Appian deployment team, and we deployed it for our organization.

Appian has increased our remittance processing speed by 10 times. It allows us to process a large volume of remittance in a short time, improving customer service. Using Appian is saving us five full-time employees, which is significant since we currently have only four team members. The manual processing we used to require would necessitate an additional five employees, so Appian has truly been a miracle for us.

Compared to other tools, which I prefer not to name due to privacy, Appian provides value for money, is easy to use, has a straightforward setup procedure, and offers great support from the Appian team. Therefore, my overall experience has been quite impressive.

We evaluated some Microsoft products before choosing Appian, although I cannot name them due to an NDA. After thorough assessment and testing, we found that Appian was faster and would provide the most benefit compared to the other options we considered.

On a scale of 1 to 10, I would rate Appian a 7.5. If the geo-location tagging feature gets added, then it will be a 9.5.

I choose 8, because of its reliability, smoothness, error-free report production, and its data extraction capability.

The integration capability of Appian is quite good; we have integrated it with our core banking software, and the integration is fast and reliable. The API works exceptionally well, so in terms of integration, I would rate Appian 9.5 out of 10.

If I compare it with other tools, our team members really enjoy using Appian. It is straightforward and user-friendly, leading to positive feedback and making it highly recommended for new users due to its ease of learning and use.

Appian's security features are quite top-notch as it has a user verification system that verifies users before granting access to the whole system. In terms of regulatory compliance, it is quite helpful since it enables authentic and error-free reporting, which leaves us satisfied.

Appian's documentation is quite helpful; while deploying the system, it assisted us greatly. I would recommend these resources to other users and development teams considering deploying Appian.

Appian's automation capability is excellent; it extracts data automatically, and the scheduler runs smoothly, generating reports in a timely manner. Therefore, Appian is quite effective and helpful in terms of automation.

I highly recommend using Appian to others. My overall review rating for Appian is 7.5 out of 10.

I mostly use Appian for internal applications in the firm.

The most beneficial aspect of Appian is its data management capabilities and the process engine in general. It allows for a seamless transition from process-centric to data-centric operations. Additionally, the zero-code integration feature is remarkable, allowing for ease of data transfer and workflow enhancement.

I would like to see more enhancement in the user interface to allow more freedom in designing the sites and pages. The user interface should be updated for a more modern and appealing look.

I have been working with Appian for around fifteen years.

So far, I find Appian reliable and stable.

Appian is scalable, but it depends on how you build your applications. With a proper setup, Appian is scalable.

The technical support is generally good. Though I have had some issues in the past, overall, I consider it effective.

I have experience with Microsoft Power Apps and have seen OutSystems. However, most of my experience has been with Appian.

The initial setup of Appian was very easy.

No implementation strategy was used. We simply built different platforms like development, testing, UAT, and production.

Appian is very efficient, allowing us to build a lot of applications within a financial year, making it cost-effective.

The pricing of Appian is based on the number of users and generally ranges from 70 to 100 USD per user per month. I would like it to be more flexible, not solely based on the number of users.

As alternatives, I have worked with Microsoft Power Apps and have explored OutSystems.

I would recommend looking into data management, reporting, and process capabilities of Appian. Overall, I rate Appian as a nine.

I use Appian for creating applications, including BPM applications.

Appian allows us to manage the entire database. I can create tables, perform database-related activities, and create multiple tables. I can directly create foreign keys, connect tables, and manipulate data using expression rules. This feature replaces data workflow from on-premises.

Since I have just started using Appian for three to four months, I haven't explored every part of it, so there might be areas that need improvement that I am unaware of.

I have been using Appian for the last three or four months.

The deployment process is very easy. I create a package for the component I work on and deploy that package to another environment.

Appian is a stable product and works very well.

Initially, without much coding, I can easily handle five thousand records. However, for more than five thousand records, I have to manage with some coding.

Appian has a community where I can put my questions. I haven't had a chance to contact the support team directly.

My experience with the initial setup is normal as I didn't get a chance to work on it. I started directly with creating features after the initial setup.

I would rate Appian nine out of ten. I would definitely recommend it to others. Being an initial user, I haven't had a chance to explore it much. I rate the overall solution nine out of ten.

I am working with all of these products: Pega, Appian, and OutSystems. I use Appian as a process orchestrator for workflow and rule-based routing, and it is preferred when I am developing an enterprise-wide application. The application is mobile-friendly, allowing me to use it across any device, whether mobile, laptop, or desktop.

It is easy for me to define the process and create configurable workflows. Additionally, they have provided inbuilt integration points and services, which facilitates integration with external services.

If there is a very complex process that includes a lot of data transitioning and memory-centric processes, it consumes a lot of memory. For those use cases, Appian needs to optimize memory utilization. AI-related features should also be more integrated.

I have been in this ecosystem for quite some time. For Pega, it is 20 years, and for Appian, it is more than ten years.

I would rate the stability as eight out of ten. As a product, there are no issues. It depends on how it has been designed and how it has been configured.

Appian is scalable in its architecture.

Their customer service is responsive, and the team is very prompt for support. The response depends on the kind of partnership vendors have and their relationship with them. For step one issues, which impact most of the business on that workflow, I get quick support from the Appian team.

Whenever there is a production deployment, it involves the Appian development team. However, if other systems are also involved, representatives from the integration teams of different systems are needed as well.

There are two buckets. On the pricier side, both Appian and Pega are enterprise-level solutions, placing them on the slightly higher side.

However, the robustness of the products, their features, and their availability justify the pricing.

I have considered Appian, Pega, Uncorp, and Mendix as alternate solutions.

Overall, everything is eight out of ten.

I am a little bit biased towards Pega. Pega has a lot more standardized processes, which take less time to go to market compared to Appian. Appian provides a platform.

Appian is really helpful in automating different processes. Our clients use it for process automation and leveraging updated features like Appian Portal and Appian RPA. The main use case revolves around external application building in nature, making it comparable to other mobile app general interfaces, particularly those heavy in user interface and user exchange. Also, Appian Records integrates all systems, providing a consolidated view, dashboard, monitoring, and report.

Appian helps in consolidating systems within the client's network, correlating data points, and offering visual dashboards to get a real-time view of various factors. Clients can check the functional state of their current infrastructure and monitor it in real-time, which also relates to the financial side of operations with business reports and similar functionalities.

The valuable features include process automation, Appian Portal, and Appian RPA. Appian allows easy integration with other systems, offers a visual dashboard, provides real-time analytics, and is flexible to be used by non-technical users for automating simple process flows. Additionally, Appian's data fabric now helps in correlating data across various systems for consolidated monitoring.

From a reseller's point of view, subscription licensing could be improved to be more cost-effective, especially for new prospects and smaller investments. Appian has new subscription models, but they might not always be feasible for smaller customers. Competitive pricing on the external user side is good, but internal user pricing needs to be adjusted for better market reach.

I have been working with Appian for nearly six years.

In terms of stability, Appian is quite reliable. I have not encountered any major downtime in customer environments. Their support team has been effective, making the solution stable overall.

Technical scalability is generally good, maybe an eight out of ten, however, some clients encounter issues due to high costs, affecting their ability to scale effectively.

Customer service in the Philippines is rated around a seven due to response times and the lack of a direct support line.

The initial setup is generally simple and well-supported by the platform's flexibility and ease of use. My technical colleagues find Appian easy to learn, though they need to continuously adapt to new features.

Appian is promising yet the cost can be a barrier. The subscription cost is higher compared to competitors, which can hinder potential market expansion, especially for new prospects.

The main competitors for Appian are Pega and OutSystems. Appian is set apart by its RPA capabilities, though it is still catching up with the likes of UiPath.

Appian is a promising platform with significant functionalities, but it would benefit from more cost-effective pricing for smaller clients. The technical support could also be improved, especially in providing direct and faster response options.

I'd rate the solution nine out of ten.

The solution is used to automate internal operations. We had industrial and equity-based financial clients.

The product improved our operational efficiency. The deployment takes one or two weeks. The rollout takes two to three weeks.

The solution’s turnaround time for development is better compared to other tools. The solution enables fast development. The traceability of the processor is good. There is much more governance and regulations on the processers. The tool reduces the time of the processes by 30% to 40%. The solution’s low-code aspect has greatly impacted the development and deployment speed.

One of the major reasons we are using the product is that we can reuse the modules. The developers can reuse all the modules. It enables us to make subsequent developments in less time. The prebuilt modules can be deployed within two to three weeks. The tool is very flexible. Compared to other platforms, the Appian product team was agile in quickly customizing things for us.

It is difficult to set up the on-premise version.

I used the solution for more than three years.

The solution is very stable. I've never faced any downtime. The response time is also great.

It is easy to scale up the product for a large number of users. We can scale up to 100 users within 20 to 30 minutes. I rate the scalability a nine out of ten. Our customers are enterprise businesses.

The technical support is not excellent, but it is good.

The initial setup of the cloud version is quite easy. I rate the ease of setup of the cloud tool a nine out of ten. It is difficult to set up the on-premise version. I rate the ease of setup of the on-premise tool a five or six out of ten.

The tool is quite costly. It's not affordable to the general public and most companies. People would prefer a low-cost version that comes with reduced functionalities. The solution would be more accessible to the users if the vendor provided it at half the cost. I rate the pricing eight and a half out of ten. The price is quite high.

I haven't faced challenges with new implementations. If an organization has a long-term goal of automation and wants to explore automation, Appian is a good choice. The product is quick, agile, and very robust. It provides everything we need. It's not like the other platforms where we have to buy multiple things on top of the actual product. It is a holistic automation tool. Overall, I rate the solution a nine out of ten.

Appian is a good workflow solution. So, I use it for workflow and low-code application development.

Workflows can basically be embedded in any domain. For example, we use Appian as a workflow solution primarily in chunks. We have a couple of use cases that we have built.

From a personal marketing perspective, it basically supports the end-to-end building of an awesome product, wherein you can use it primarily for data orchestration, and then for building process workflows, and then for building approval workflows.

So, you can set it all together. You can bring in the data through Appian, and then I use this to integrate with different solutions, different products, and different platforms that exist in the company. It brings them all together. It can then be automated. We have a couple of new steps available to us.

For one of the clients, we've used this to build a complete end-to-end claim cycle, where we built a portal that integrates into various systems.

We get emails that get processed. From there, a claim is received. It goes through the entire claim designation lifecycle. It goes through different people, different approvals, and then finally, there's some integration with the payment system.

Once the claim is approved, the payment happens. And it is one seamless process. And then if any litigation is required, it can be directed to the finance team and so on. So, there is an end-to-end claim cycle that has been automated using Appian.

So, this is just an example of a workflow we've optimized using Appian.

From a feature perspective, Appian has quick development, given it's a low-code platform; you can quickly use it to build a solution.

And then, if we need to make changes, we don't need to do a lot of coding.

With low-code, we don't need a lot of coding, and then from the plumbing perspective, there is a complete CI/CD pipeline that exists within Appian that can be leveraged for open deployment.

We can manage versions, do field deployment, and manage all these smaller incremental changes that need to be done. It's self-sufficient, from my perspective.

From a product perspective, it's good. There are some restrictions with respect to using external components within Appian.

So, for example, if we do not have a particular feature available, there's a long cycle of getting approvals and all of that. That does not offer flexibility, which definitely can be improved on.

Another area of improvement is pricing.

I have been using it for two years now.

It is a stable product. I would rate the stability a ten out of ten. We have not faced any challenges with respect to the platform in the last two years.

Since it is on the cloud, it is easy to scale.

There are around 200 end users using this in our company. The usage depends on the end user.

Appian is scalable, especially from an integration standpoint. It offers low-code integration capabilities, eliminating the need for external integrators.

It comes with many components and connectors that facilitate system integrations.

The customer service and support are very responsive. We haven't faced many issues, but when we have, the support team has been very helpful.

The Appian community is strong and open. You can often find solutions or discussions relevant to your issues. Consulting with community members through platforms.

The initial setup is straightforward and easy to use.

Deployment is quick.

We did it in-house. It depends if you have the skills in-house, it can easily be done.

So, there are not many things that you have to do. The solutions can be built in Appian itself, there's a pipeline that exists. You just have to kind of tag the components that need to go into deployment and use them to deploy easily.

It is a little bit expensive when compared to other platforms, it is somewhat expensive.

The license is not very cheap. It's on the expensive side.

The licensing is on an annual basis.

Overall, I would rate the solution a seven out of ten.

I would recommend it, especially if you're looking to quickly develop workflow solutions with low-code integrations. Among similar platforms, I'd place Appian in the top tier.

It is a business process management platform. We used it while working on a loan origination process for a bank.

The product's most valuable feature is the low code aspect of development. We can develop an end-to-end VPN solution using a single platform. It is easier to focus on business cases and problems rather than consume much time in the development process.

The product’s pricing could be improved from the developers' perspective.

We have been using Appian for a year and a half.

I rate the software’s stability a nine out of ten.

We can resolve many issues with the help of their community and documentation or in-house trial and error.

The initial setup for the on-cloud platform is quite straightforward.

We can implement the on-premise version in-house. However, Appian helps us set up cloud-based clusters.

We purchase the software’s yearly license. The cost is calculated on a per-user basis. It might be expensive for small and mid-sized enterprises.

I recommend Appian to others and rate it a nine out of ten.