Search icon
Subscription
0
Cart icon
Close icon
You have no products in your basket yet
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Low-Code Application Development with Appian

You're reading from  Low-Code Application Development with Appian

Product type Book
Published in Apr 2022
Publisher Packt
ISBN-13 9781800205628
Pages 462 pages
Edition 1st Edition
Languages
Author (1):
Stefan Helzle Stefan Helzle
Profile icon Stefan Helzle

Table of Contents (22) Chapters

Preface 1. Section 1: No-Code with Appian Quick Apps
2. Chapter 1: Creating an Appian Quick App 3. Chapter 2: Features and Limitations of Appian Quick Apps 4. Chapter 3: Building Blocks of Appian Quick Apps 5. Chapter 4: The Use Cases for Appian Quick Apps 6. Section 2: A Software Project with Appian 7. Chapter 5: Understanding the Business Context 8. Chapter 6: Understanding Business Data in Appian Projects 9. Chapter 7: Understanding Business Processes in Appian Projects 10. Chapter 8: Understanding UX Discovery and the UI in Appian Projects 11. Section 3: Implementing Software
12. Chapter 9: Modeling Business Data with Appian Records 13. Chapter 10: Modeling Business Processes in Appian 14. Chapter 11: Creating User Interfaces in Appian 15. Chapter 12: Task Management with Appian 16. Chapter 13: Reporting and Monitoring with Appian 17. Section 4: The Code in Appian Low-Code
18. Chapter 14: Expressing Logic with Appian 19. Chapter 15: Using Web Services with Appian Integrations 20. Chapter 16: Useful Implementation Patterns in Appian 21. Other Books You May Enjoy

Best practices

The most important best practice is to create an entity relationship model before you start in Appian. It is not a problem to make minor changes, as you have seen, but without good preparation, you may have to recreate large parts of your CDTs and records.

The second best practice is the naming convention. In Appian, each field has a defined type. This type is visible in all places. Do not add the data type itself into the field name. Then, give the primary key field the same name in all CDTs. I use id for that. A field, referring to the primary key of another CDT, gets the name by following this pattern:

<nameOfOtherCdt>Id

Finally, keep the logic out of the database. From a pure Appian perspective, the database is just another integration, much like an integration with a SalesForce system or SAP. Try to implement most logic in Appian to reduce the complexity of your overall development.

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime}