In our previous blog posts, we’ve covered the core components, orchestration capabilities and automated analysis and ChatOps features in our in-house Security Orchestration, Automation & Response (SOAR) application. In this final blog post, we will briefly cover one of the system’s automated response capabilities that allow it to take action and respond to alerts without human intervention, and close out the blog series with two important lessons learned from implementing SOAR at Appian.

Not to get all gloomy about it, but the pandemic accelerated the largest declines in college enrollment in more than 50 years and slammed colleges and universities with $24 billion in COVID-related debt. In other words, COVID was a wake up call for higher education.

The world is entering a new age of technology. Low-code/no-code tools are already becoming a mainstay for many global teams. By going no-code/low-code, teams can now fill in the gap between the accelerating demands of application delivery and team skill sets. While these tools are nicely on their way to becoming mainstream for development, similar ones for test automation are pushing their way into the market.

Last year, my friends at Appian commissioned some research through the Economist Intelligence Unit (EIU), Financiers ridden with technical debt. The results were interesting: Research from The Economist Intelligence Unit, sponsored by Appian, finds that just over a third (34%) of IT decision makers believe that the reduction or elimination of legacy IT would do most to help their organisation achieve its automation objectives.

The financial services industry, like so many others, has undergone long-lasting changes in recent years. With the emergence of new technologies, new regulations, and unprecedented market changes, institutions have had to contend with unpredictability and rising consumer expectations. To effectively manage constant change, financial firms have to find a way to balance innovation and efficient process execution with risk.

You can spend hours scrolling down the rabbit hole of government IT horror stories, which makes the recent launch of the federal website for ordering free COVID tests that much more remarkable. The website worked, and it was surprisingly easy to use. But that success belies decades of underinvestment in digital transformation that has stifled public sector innovation and hardened the government's low-tech image. For example.

Seven years ago, we announced Linx 5, a release specifically designed to modernise and commercialise an internal tool we had been using with our enterprise customers for the previous 15 years. By all accounts, Linx 5 was a huge success with our customers and partners. With Linx 6, we’ve built on that success with new features, a streamlined UI, and a new diffable file format – something our customers have been clamouring for.

When COVID-19 hit, college students freaked out, universities went remote, and millions of students struggled with the impersonal functionality of Zoom—even with tropical backgrounds. But more than that, the pandemic exposed the shortcomings of legacy student information systems (SIS) that stymied university efforts to limit virus spread and help anxious students cope with pandemic stress. But sometimes it takes a crisis to start a revolution.

No code and low code test automation are becoming widely adopted and will help address the evolving challenges faced by businesses today. However, what is the difference between no code and low code? When is it useful for an organization to adopt? How useful are their capabilities? Will this dampen the need for skilled Automation Engineers, Software Development Engineers in Test (SDET), or traditional Quality Assurance (QA) Specialists?