Agiloft vs. Drupal

Agiloft is great for storing contracts and being able to run reports on those contracts. Where is lacks is when there are amendments to the contracts which change information that you will run a report on. Since the data doesn't stack, if I wanted to run a report on any agreement with unpaid time off and there was unpaid time off added in the first amendment but removed in the second amendment, the first amendment would still hit the report even though the unpaid time off was removed in a later amendment

Incentivized

If you want to set up a basic Not For Profit (NFP) Membership system and content base, Word Press is easier than Drupal. However, if you have specific needs that require a fair bit of customisation then Drupal is the best CRM available. If the webmaster is confident with PHP and SQL, Drupal allows a lot of creativity.

Incentivized

• Categorizing data based on your specific business needs.
• Comparing documents and identifying risk.
• Workflow management and visibility into state of things.

Incentivized

• Drag and drop functionality is easy to use
• Easy to switch between straight text and HTML content
• Ability to easily have multiple environments so that pages can be built in b/c-stage before they are approved and published
• Solid user experience where it's clear how to navigate the platform

Incentivized

• I am not a fan of the color scheme.
• Many unnecessary integrations (Alexa).
• Logging details about contracts should be easier to customize.

Incentivized

• This is not an easy CMS to work with if you don't have a good understanding of website development. It isn't "plug-and-play" like Wordpress or Shopify.
• Over time, doing major updates to the system can be taxing, especially if you aren't well-versed enough in doing system updates in line with your "child" theme and code.
• The CMS can become somewhat cumbersome with server resources if not carefully optimized while you build and customize it to your liking.

Incentivized

The current functionality is excellent and we keep getting request for more. Leadership wants to make this a one stop shop.

Incentivized

The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.

As with our brains, we only use 10% of its capability. It can be as complex as you want it to be or as simple. The training requirements to use it have been minimal depending on the application. This is really a reflection as to how the workflow was configured

Incentivized

As a team, we found Drupal to be highly customizable and flexible, allowing our development team to go to great lengths to develop desired functionalities. It can be used as a solution for all types of web projects. It comes with a robust admin interface that provides greater flexibility once the user gets acquainted with the system.

Incentivized

Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).

Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.

Incentivized

Implementation was relatively easy and I have not had any issues with the support. UI change created some challenges for the end-users, but overall, it was a smooth experience. I hope the company will continue investing in the product and not consider it as something to not care about too much. I believe Agiloft does not make any other software, so I think the focus on it should not wane.

Incentivized

As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.

Incentivized

I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.

The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.

Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%

Incentivized

Prior to implementing Agiloft, we used ProLaw. ProLaw acts as an electronic library for all contracts across the company. We were able to get this to work for us but it was limited in what functionality it provided. Agiloft is far superior when it comes to tracking and contract generation. Both systems store the agreements; however, Agiloft does a lot of the work for us. It creates the agreements with the click of a button, manages user permissions, sends automated reminders without requiring setup. These are all things ProLaw either didn't have or had but required manual entry. I was not the one who selected Agiloft as our new system, but after using it I can see why it was chosen.

Incentivized

Drupal can be more complex to learn, but it offers a much wider range of applications. Drupal’s front and backend can be customized from design to functionality to allow for a wide range of uses. If someone wants to create something more complex than a simple site or blog, Drupal can be an amazing asset to have at hand.

Incentivized

Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.

Incentivized

• Agiloft has streamlined the requisitioning process and eliminated manual effort and repetitive low-value tasks.
• We now have a single source of truth for our SOC audits.

Incentivized

• Given the endless possibilities that Drupal can have, we tend to have great support going on when we get a website launched
• It has become much much faster and easier for us to launch a new project due to reusability
• Configuration management in Drupal helps greatly with CI/CD, saves us costs