In this episode of Appian Rocks, host Stefan is joined by Sandro, Marcel, and special guest Joe Longworth to discuss the pros and cons of using database tasks versus process tasks in the Appian platform. The conversation was sparked by a discussion on a Discord server where Joe shared his extensive experience with running large applications involving hundreds of thousands of users and tasks. Joe’s preference for database tasks over Appian’s built-in process tasks led to an in-depth discussion about the design considerations and challenges associated with each approach.

Joe explains that one of the main drivers for his decision to use database tasks is security and the complexity of managing Appian groups. In large deployments with tens of thousands of clients and numerous dimensions of security, using Appian groups can become unmanageable. Joe points out that assigning tasks to groups in Appian can lead to a situation where hundreds of thousands of groups are needed, making it difficult to manage users and their permissions. By contrast, using database tasks allows for more flexible and scalable management of task assignments based on attributes stored in the database.

Stefan and Marcel also share their perspectives on the topic. Stefan prefers using Appian tasks for their simplicity and built-in features, which are sufficient for many use cases. However, he acknowledges that for large-scale deployments or scenarios requiring complex security and task management, database tasks may be the better option. Marcel adds that while database tasks offer advantages in terms of scalability and flexibility, they also require more development effort and a higher level of technical expertise.

Joe provides insights into his background and experience with Appian, having worked with the platform since 2011. He currently leads a team that manages a large environment with around 10 million active tasks and a user base of 3,500 internal and 200,000 external users. Joe emphasizes the importance of scalability and performance in his decision to use database tasks, as well as the need to integrate with third-party systems and manage tasks completed outside of Appian.

The discussion also touches on the challenges of implementing database tasks, such as building custom features like task notifications and managing task reassignment. Joe highlights the benefits of database tasks, including the ability to restart tasks easily and the flexibility to aggregate and work on multiple tasks simultaneously. He also notes that database tasks can simplify the process of upgrading and changing processes, as they are not tied to specific process instances.

The episode concludes with a summary of the key considerations for choosing between database tasks and Appian tasks. Factors such as the number of tasks, the complexity of security requirements, the need for integration with external systems, and the distribution of tasks over time should all be taken into account. The hosts agree that while Appian’s built-in tasks are suitable for many scenarios, database tasks offer significant advantages for large-scale and complex deployments.

Overall, the episode provides valuable insights into the decision-making process for task management in Appian, highlighting the trade-offs and benefits of each approach. The conversation underscores the importance of understanding the specific requirements and constraints of a project to make an informed decision.

In this episode of Appian Rocks, host Stefan welcomes special guest Matt, a seasoned IT professional with nearly 20 years of experience, including a decade working with Appian. The two met at the last Appian conference in Washington, where they decided to have a more in-depth discussion about Matt’s career, his experiences with Appian, and his thoughts on the platform.

Matt introduces himself as a freelance consultant from Montreal, Canada, with a background in information technology. He shares his journey from working with PeopleSoft and Java web development to becoming a solution architect at a Crown corporation in Montreal. This role marked his first significant encounter with Appian, which the organization chose for a major modernization project. Matt describes the challenges of maintaining a complex technology stack and how Appian helped simplify operations, allowing the IT team to focus on modernization rather than just maintenance.

The conversation shifts to Matt’s appreciation for Appian’s low-code platform, which he found to be a game-changer compared to traditional open-source development. He praises Appian for its ability to streamline business processes and reduce the time spent on technical issues. Matt also highlights the intelligence and professionalism of Appian’s support staff and the company’s intentional, purposeful approach to product development, drawing a parallel to Apple’s focus on cohesive, well-thought-out solutions.

Stefan and Matt discuss the potential of AI in software development, particularly in the context of low-code platforms like Appian. While Matt sees value in AI as a co-pilot for developers, helping with tasks like refactoring and code optimization, he emphasizes that AI is only as effective as the instructions it receives. He believes that the true power of AI lies in its ability to assist developers who already have a clear understanding of their goals.

The conversation also touches on Appian’s new Process HQ feature, which leverages record events for process mining and transparency. Matt expresses some reservations about the need to intentionally record events, as opposed to having an automatic observability feature. He shares his current approach of recording various events to see what insights can be gained, but acknowledges that more experimentation is needed to fully understand the feature’s potential.

Matt shares two success stories from his career. The first is the modernization project at the Crown corporation, which has been running successfully for nearly a decade. The second is a current project involving a modular design approach, allowing for parallel development and easier maintenance. This project, though not yet complete, shows promise in terms of scalability and efficiency.

In terms of challenges, Matt recalls moments of frustration when seemingly simple tasks took longer than expected, highlighting the importance of perseverance and problem-solving in software development.

The episode concludes with Stefan and Matt expressing their enthusiasm for future conversations and collaborations, both within the Appian community and beyond. They look forward to continuing their discussions on various platforms and exploring new developments in the world of low-code and AI.

Overall, this episode provides valuable insights into the practical applications of Appian, the benefits of low-code development, and the evolving role of AI in the industry. Matt’s experiences and perspectives offer a compelling look at the challenges and rewards of working with Appian, making this a must-listen for professionals in the field.

In the latest episode of “Appian Rocks,” we had the pleasure of interviewing Mike Schmitt, a seasoned Appian evangelist with over 12 years of experience, making it a truly special episode.

Mike began his Appian journey in 2012 as a trainee at an Appian partner company. Starting at the ground level, he got his initial exposure by helping with QA for new releases and mobile app versions. Mike’s first major project involved building an HR onboarding and lifecycle management system for the Treasury Department, implemented in the then-new Tempo interface. He fondly recalls the transition from the legacy forms designer to the newly introduced SAIL forms, albeit the project’s timelines exposed him to both systems.

Mike’s background is quite eclectic. He graduated with a computer science degree from the University of Maryland but found his initial post-college years murky, working in various IT support roles—first as a bus driver, then a field service tech. His transition into software development was somewhat serendipitous, spurred by a frustrating encounter with a new manager. This prompted him to refresh his job profile, eventually leading him back into a development environment with Appian.

In describing his early development days, Mike emphasized the importance of practical experience. His initial foray involved a lot of hands-on learning, thanks to a supportive training environment. He described his first impressions of Appian as challenging, particularly with the older portal tasks and legacy interfaces. Nevertheless, the eventual proficiency led to his enthusiasm for the platform, influencing him to leverage Appian in various ways, including convincing his company of Appian’s potential for new tools.

Mike was candid about the highs and lows of his Appian journey. One of his early successes was developing a system for generating customizable Word documents for the Treasury Department, showcasing his knack for innovatively using Appian’s capabilities. Over the years, his experiences expanded, particularly through mentoring a junior developer at his current workplace. Mike stressed that despite Appian being labeled “low-code,” it still demands the diligence and detail-oriented nature typical of traditional software development.

The conversation also touched upon the evolution of Appian, from its early days to the modern incorporation of AI and other advanced features. Mike provided insightful critiques, elaborating on how newer features like user-facing report builders and AI components are potential solutions yet to find their principal problems. He shared a desire for more accessible proof of concepts, particularly for portals and AI capabilities, to better demonstrate their value.

On the topic of training and onboarding new developers, Mike emphasized the importance of foundational education, recommending a combination of online courses and instructor-led boot camps. He also underscored the patience required in dealing with Appian’s unique nuances and suggested not shying away from plugins, contrary to some restrictive practices he encountered.

True to his pragmatic approach, Mike concluded with practical advice for new developers and seasoned professionals alike: invest time, read the documentation, and engage with the community. His perspective offers a balanced mix of optimism for Appian’s benefits and a realistic view of its current limitations. Developers should apply a patient, open-minded approach to mastering Appian’s unique environment, and actively participate in the community for continuous learning and improvement.

Mike’s contributions to the Appian community, coupled with his rich experience and critical insights, make this episode a must-listen for any Appian enthusiast or professional. Through detailed anecdotes, practical advice, and a candid tone, Mike Schmitt offers invaluable lessons and perspectives that resonate with both novice and seasoned Appian developers.

While chatting on Discord, I had the idea to meet Mat and Mike at Appian World ’24 to discuss some ideas. Then we decided to turn this into a spontaneous podcast recording together with Josh. When then discussed the latest Appian features which were just announced in the keynote.

A huge “Thank You!” goes to Appian’s April Schuppel and Ben Dudley for organizing a quite room in the executive meeting area for us.

We discovered that the time was far too brief, and we’re eager to do more. Stay tuned!

In this episode, we discuss why software architecture is crucial for any non-trivial application. That has not fundamentally changed with low-code, but we still have to adapt our ways of developing software architecture to the building blocks available. Yes, this means that there are no micro-services in Appian. We also discuss Marcels recent experience with the documentation framework Arc42