Episode 23: 7 Years of Process Reports

In our latest episode my co-hosts, Sandro and Marcel, and I delved into our personal experiences with process reports within the Appian platform. Sandro shared his journey of initial struggles and eventual breakthroughs in understanding and utilizing process reports effectively. Throughout the discussion, we highlighted the challenges we’ve faced with process reports, including their complexities and limitations compared to other Appian objects. Despite these obstacles, we emphasized the importance of mastering process reports and the value they bring to Appian applications. We encouraged our listeners to explore and embrace process reports, despite their complexities, and to share their feedback and experiences with us. We hope to foster a community of learning and improvement in the realm of process reporting functionalities within Appian. Join us on our journey to unlock the full potential of process reports!

The Dark Secret of Business Software

Ah, business software! The lifeblood of any organization’s operations. But let’s face it, folks. Most business software is an abomination to user experience (UX). It’s clunky, outdated, and often downright frustrating to use. A Horrible User Experience I’m not talking about the occasional “oops” moment when a feature doesn’t quite work as expected. I’m talking… Read More The Dark Secret of Business Software

Episode 22: Interviewing Joshua Fischer

In this episode of Appian Rocks, I had the pleasure of hosting Josh Fischer, the leader of the Appian practice at Blue Ark, a woman-owned small business focused on federal government projects. Our conversation began with Josh’s journey into the world of information technology, starting from his time at the State Department to his service in the Navy, where he honed his skills in computer systems and information technology.

Josh shared his initial exposure to Appian while working on significant projects for the Federal Communications Commission and the Food and Drug Administration. He reflected on how Appian’s training and documentation have evolved over the years, noting the shift from basic PDF guides to comprehensive video training sessions. We discussed the challenges faced by new developers in adapting to the platform’s growing complexity, particularly with the introduction of features like data fabric and records.

As we delved deeper into Appian’s capabilities, Josh highlighted his experience with the Live Build Challenge at Appian World, where he learned the importance of balancing speed and best practices in development. He also shared insights into the evolution of Appian’s features, including the transition from process-centric to data-driven applications, and the significance of modular design in handling complex data processing tasks.

One of the key topics we explored was the challenges of working with large datasets and the limitations of Appian’s current data sync records. Josh emphasized the need for efficient data processing, especially when dealing with millions of rows of data from various sources. He expressed excitement about the upcoming Apex execution engine, which promises to enhance performance but also raised concerns about potential latency issues compared to traditional database processing.

Throughout our discussion, we touched on the nuances of Appian’s documentation, the importance of understanding the differences between on-premise and cloud implementations, and the need for better visibility into related action security. Josh’s passion for Appian and his commitment to optimizing processes shone through, making for an engaging and informative episode.

As we wrapped up, we acknowledged the ongoing evolution of Appian and the community’s role in shaping its future. Josh’s insights and experiences serve as a valuable reminder of the importance of adaptability and continuous learning in the ever-changing landscape of technology.

Episode 21: Low-Code is not Color by Numbers

In this episode of the Appian Rocks podcast, I, Stefan, along with my guests Sandro and Marcel, delve into the often misunderstood realm of low-code development. We kick off the discussion by addressing a common misconception: that low-code tools are only suitable for building simple applications. This notion stems from the marketing strategies surrounding low-code platforms, which often emphasize ease of use and accessibility for citizen developers. However, we argue that this oversimplification can lead to underestimating the complexity involved in creating robust applications.

We explore the idea that while low-code platforms like Appian can streamline development processes, they do not inherently reduce the complexity of the applications being built. In fact, the potential for complexity increases as developers leverage low-code tools to create intricate systems. We emphasize that effective low-code development requires a solid understanding of software design principles, regardless of the absence of traditional coding.

Throughout our conversation, we highlight the importance of proper planning and design in low-code projects. We share anecdotes from our experiences, illustrating how underestimating the effort required for enterprise-level applications can lead to project challenges. We also discuss the role of citizen developers, noting that while they can contribute to projects, they may not possess the necessary skills to manage complex use cases effectively.

Ultimately, we conclude that low-code does not equate to low complexity. Instead, it offers a different approach to software development that can enhance efficiency and collaboration when used correctly. We encourage developers from all backgrounds to embrace low-code tools while maintaining a focus on thoughtful design and architecture.

Episode 20: Interviewing Joe Longworth

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.