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

Creating reusable interface components

In Appian, an interface is basically like any other expression, with the added benefit of the design mode in the interface designer. This also means that you can create your own reusable interfaces tailored to a specific need. Let's have a look at the interfaces we built and try to identify candidates for building an interface component.

This happens next

Create a new interface with the name IVP_C_ThisHappensNext. The letter C indicates that the purpose of this interface is for it to be used as a component inside other larger interfaces.

Add a rule input named text of the text type. Enter the following code snippet:

a!sectionLayout(
  label: "This Happens Next",
  labelIcon: "route",
  contents: {
    a!richTextDisplayField(
      labelPosition: "COLLAPSED",
      value: ri!text
  ...