Appian vs. JAMS

Appian works great for automating manual processes and integrating multiple systems through its toolset. It gives great flexibility for establishing rules for approvals, routings, escalations, and the like. Because of the low code toolset, it's very easy to deploy and make changes as needed as processes evolve and as the organization learns to utilize the system better. Minimal maintenance is required to support the applications build on the platform. Some of the automated testing integration with tools like Jenkins is limited so that may be an issue for some.

Incentivized

There's probably better schedulers out there. JAMS is good for an on-premises/classic IT implementation. JAMS is well-suited for use cases such as collecting a file from a shared location and uploading it to an API, running scripts on servers, and handling middleware tasks that process files or data between handoffs across different locations. JAMS is best suited to environments
with IT staff who can develop, test, implement, maintain, and troubleshoot
scripts; it does not use natural language processing (so it requires in-depth
knowledge of the scripting language in use), and it does not appear to offer
native dashboarding or reporting that is easily accessible to all users.

Incentivized

• Allows at a glance workflow documentation which assists in the need we have for information readiation.
• Drag and drop interface for workflow development greatly speeds our apps time to market.
• Using the advanced features of Appian, we are able to create working sites in a fraction of the time it would take to do so using "traditional" development.

Incentivized

• JAMS works well to organize jobs into logical folders with unique permissions for each folder
• JAMS makes it easy to set up alerts for job failures and other notifications
• Setting up scheduling times with normal human wording, such as Weekdays, or 2nd Tuesday of the month, etc.

Incentivized

• Search issues when type ahead and database search are used in the same field.
• Buttons implementation where user is require[d] to click on the button description - if clicks on the button outside that text - button will not work.
• Problems with using certain off-the-shelf performance tools like WebLoad or Neoload. That is because of different dynamic variables being used internally in Appian - which these tools are unable to correlate. We are still investigating using other tools like Jmeter to overcome dynamic correlation problem for performance testing.

Incentivized

• Would love to see JAMS become a SaaS type of product instead of needing to be hosted by ourselves
• having lots of jobs in the monitor area can lead to performance issues when running the client locally
• dashboard and reporting tools could be more user friendly and provide more functionality to help monitoring teams spot recurring issues easily

Incentivized

We recently renewed our license with Appian. We are convinced that its flexibility, relative ease of use, the support they provide, there mobile advancements and their general willingness and desire to see us succeed all contributed to our reason to renew our agreement with Appian

JAMS is a critical resource free up people to do other things and ensuring that processes and tasks are run consistently. We are also confident that procedures are run consistently and on time or as soon as the necessary data is available. With automated job failure notification, we are not required to check that jobs are running correctly.

Incentivized

Appian is a low code environment, because of this, a very good visual interface is required. Appian is providing a feature-rich dashboard [that] we can use for building the dashboards and other interfaces. Appian also provides patches and releases to enhance these features. A developer can start off development just by going through a basic course from the Appian learning community.

Incentivized

JAMS is very user friendly; you hardly need to do coding. The only thing that I would say a challenge is setting it up, but that's because you barely know the product yet and, in every processing, setting up is the difficult part. But once you've set it up and you are going to use it, you will really feel that it is worth to invest in this kind of software solution, it really does it job very well.

Incentivized

We didnt really encounter any downtime, no issues encountered during 2 years of use of JAMs also our client barely raise an issue with JAMS, mostly the issues is on the batch jobs that jams executes. So I would gave it a perfect 10, very reliable hardly encounters any error and bug

Incentivized

JAMS performance is very great, there are no issues raised with the performance, it just like nothing happens on the job after integration it gives you this monitoring capability, no reports and bugs raised on the performance, we didnt do integration with other software only database and with use of JAMS agent to different servers

Incentivized

Appian is one of the leading low code business automation platforms that support RPA, decision rules, case management, workflow automation, and machine learning all in a single bundle. But it is also harder to implement and replace the traditional business process.

Incentivized

I've never had to wait more than a day for a response to any email queries submitted. We had a very positive experience using support hours during out migration process from v6 to v7. We've also recently had a weeklong group training course where all attendees were positive about the learning outcomes, a shoutout to Jose who did both the migration and the weeklong course!

Incentivized

As analyst I participated in a developer boot camp. At times it was hard to keep up but most of the time it made sense. Trainer took the time to explain and slowed pace down to answer questions etc.

Incentivized

People that were involved in the POC found the training a lot easier to follow. I think most people would have preferred to just get the training material and run through themselves.

Incentivized

Very boring; hard to get through quickly, but rather effective in demonstrating the use of the platform.

Incentivized

It was really seamless. SaaS in the true definition of the word. We logged on and started using the product. Very easy.

Incentivized

I Was not part of the original Implementation, and the persons did that are no longer with the Organization. But I was part of the recent Upgrade process a year ago and I am the JAMS admin and was very pleased

Incentivized

Appian has enormously transformed and keeps on updating the product every quarter to meet the latest needs of the world with new innovations & technologies being integrated within the platform. What gives more pleasure than a product that keeps on continuous[ly] improv[ing]?

Incentivized

JAMS is WAY more advanced, it isn't a fair comparison. The history is easy to get through. It is easy to get alerts of complete to failed and with a log. Adding jobs is extremely easy that even my teammates who do not manange the software are able to set them up. With the new web component we are very excited for the future of JAMS advancements.

Incentivized

i didnt have any involvement in the sales process, however we purchased the product so it had to be decent.

The product is quite flexible. There are a number of features and functions that we use on a daily basis, and there are many features that are available that we have not yet needed or explored (like setting up jobs with the ability to do FTP or Sftp file transfers).

Incentivized

i didnt have any involvement in the sales process, however we purchased the product so it had to be decent.

• I believe it has negatively impacted our release dates. There may have been a misunderstanding as to the learning curve, even though it is "low code."
• The look and feel of the applications created using Appian have uniformity and it's easier to have "reuse" between applications.
• There is less developer control when it comes to features. I think this mainly has to do with the amount of plugins available. I would think there should be many more available plugins. But again, our use case is probably different than most others.

Incentivized

• Our company depends on the JAMS Scheduler in executing a large number of SAP Jobs. In never having had a true Enterprise Scheduler such as JAMS before now, we are very happy with the results.
• There a number of features in JAMS for setting up schedules and dependencies on other jobs. This helps our company achieve the necessary workflows for Job execution. This optimization saves on system resources and keeps Jobs flowing smoothly.
• We are very happy that JAMS is a robust solution with High Availability. This is necessary for Enterprise products, to reduce downtime, which we have not had as a result. This feature definitely saves our company money by reducing or eliminating unexpected downtime.