Book Image

Low-Code Application Development with Appian

By : Stefan Helzle
Book Image

Low-Code Application Development with Appian

By: Stefan Helzle

Overview of this book

This book is an exhaustive overview of how the Appian Low-Code BPM Suite enables tech-savvy professionals to rapidly automate business processes across their organization, integrating people, software bots, and data. This is crucial as 80% of all software development is expected to be carried out in low code by 2024. This practical guide helps you master business application development with Appian as a beginner low-code developer. You'll learn to automate business processes using Appian low-code, records, processes, and expressions quickly and on an enterprise scale. In a fictional development project, guided by step-by-step explanations of the concepts and practical examples, this book will empower you to transform complex business processes into software. At first, you’ll learn the power of no-code with Appian Quick Apps to solve some of your most crucial business challenges. You’ll then get to grips with the building blocks of an Appian, starting with no-code and advancing to low-code, eventually transforming complex business requirements into a working enterprise-ready application. By the end of this book, you'll be able to deploy Appian Quick Apps in minutes and successfully transform a complex business process into low-code process models, data, and UIs to deploy full-featured, enterprise-ready, process-driven, mobile-enabled apps.
Table of Contents (22 chapters)
1
Section 1: No-Code with Appian Quick Apps
11
Section 3: Implementing Software
17
Section 4: The Code in Appian Low-Code

Decisions – simple logic in a visual designer

Let's have a brief look here at the decision you created for a dynamic assignment:

Figure 14.1 – Dynamic assignment decision

Here, we take the amount as input, and depending on a threshold we return one group or another. In general, a Decision object in Appian applies some logic to inputs and returns matching output. The limitation here is that we cannot define any dynamic runtime behavior such as data manipulation or database queries.

But we can configure a decision to do a bit more than just simple input-to-output mapping. Our options are presented here:

  • Hit Policy: Define that only a unique single row can match the first or multiple rows (Rule Order)
  • Logical Operator: Define in which way the input value should be compared
  • Multiple Inputs: Create one or more inputs to implement multiple condition logic
  • Multiple Outputs: Create one or more outputs to return groups of values...