Appian 16.1 Review

Appian 16.1 was released last month and jumped ahead a couple releases! No, that would be a lot of updates! Instead, Appian began to number their releases by year. January releases usually include plenty of incremental improvements but are smaller overall compared to the normally HUGE pre-Appian World release in April/May. So here are some of the coolest new features!

End-User Features

Grid-Style Record Lists — Long overdue, you can now configure the default Record list view as a grid instead of a feed-looking structure. Most users prefer the grid view, especially for large sets of records, and Reports were frequently used to display all records in a grid view with associated filters. These reports will probably still be used, but the record list grid is a welcome alternative.

Multi-Page Sites — I admittedly haven’t gotten a chance to use Sites (much less multi-page Sites) but they look great. There are always certain stakeholders (data entry personnel, customers, vendors, etc.) that only need a slim view of Appian functionality, and Sites fits that use case perfectly.

User and Group Browser Components — Provides a great visual component for navigating groups and selecting one or more users/groups. I think these components will slowly replace pickers for the optimal method for selecting users/groups since they’re more visual than the pickers’ autocomplete functionality.

Designer Features

Assertions for Expression Rule Test Cases — Assertions allow a designer to specify the conditions that cause a test case to pass. They seem like the next step in Appian building out their testing capabilities, which I love to see. The testing features are becoming more and more robust!

Default Filter Option — Designers can now specify a default filter in their Record list view (like status=active for instance). Despite being a small change, designers used to have to create multiple different records for showing subsets of typically used data, like ‘Active Requests’ and a separate record for ‘Completed Requests’. Now the default filter can be used.

Format Expression Button in Expression Rule Designer — The expression editor now has a button for formatting your beefy SAIL expressions! Sharp designers probably already knew about the keyboard shortcut (Ctrl + Shift + F), but the button makes formatting your expressions that much more obvious. Always a good thing.

Deployment Features

Search by UUID — The Designer environment now allows search by UUID, which is the best news your Deployment Lead has heard in a while! Appian’s import errors have always been almost comically vague, only giving a UUID for missing dependent objects. Previously there were some plugins that could be used to track down the missing objects by UUID but searching by UUID in the designer environment is a welcome improvement.

Inspect Data Stores improvements — Now if Data Stores can be imported but not published, it comes up as a warning instead of an error in the Import log. This error was always confusing to new Appian users, and I’m glad it’s now a warning.

Existing Object Rolemaps are Overwritten on Import — This long awaited change is another win for faster releases. Previously, the security of imported objects was merged with the privileges in the higher environment causing some confusing results. After import, the security of each object would then need to be inspected and changed. Now, the security roles of the lower environment override the higher environment, eliminating the extra manual steps. This is another improvement for object security management that’s been getting a lot attention in recent releases (thankfully).

Admin Features

Primary Data Source Terminology Change — Rather than “primary” and “secondary” data sources, the two standard databases are called “Appian” and “business” data sources. This terminology change is more informative and useful for sure but will require some extra steps during the upgrade process.

Data Source Configuration in /admin — Data sources can now be configured in the Admin Console instead of via configuration changes on the server! No app server restart required! Another huge time saver for administrators.

Those were my big takeaways from Appian 16.1, but there were plenty of other changes that can be found in the release notes.

Predictions for Appian 16.2: HUGE release before Appian World in late April. The /design environment becomes the default development environment, and the old designer UI is only available for process modeling and some obscure configurations. Large testing functionality announced as well.

Until then,