We've made some big improvements to the Record Type creation experience. With our new simpler, more intuitive, navigation we've made it easier than ever to create and configure a Record Type.
Developers now have direct access to the things they care the most about. With individual page navigation, you'll spend less time searching and more time focusing on building amazing records.
The list of record types in Tempo now has search functionality and a new look and feel. The list shows up to 200 record types with greater density than before. Users can quickly find their record type in a big list by searching, and the list scales to support application growth over time. Additionally, developers can choose an icon to better describe their type of record.
We've increased your options to display progress with a new component, Gauge Field. While the Progress Bar works great when you want to display it across the top of the page or in a grid, the Gauge fits in more compact areas and attracts attention with its ability to set a color, size, and inner text.
You can now configure any attended activity to capture the geographical location from where users submit the associated activity form. When a geolocation-enabled form is submitted from the Appian for Mobile Devices application, user location is automatically included along with the form. This location information can be used for a variety of purposes like constructing audit trails, generating regulatory compliance reports, and performing retrospective verifications. To protect user privacy, a banner is displayed on top of all geolocation-enabled forms informing them that their location is being requested.
This release gives you tighter control over the look and feel over many of your UIs. We've added much-requested larger rich text sizes which work great for displaying prominent icons and emphasizing text, as well as a rich text size between our current medium and large sizes to help you get the look just right.
For column layout, we've added width options between our existing sizes so you can choose the size that works best for your content We've also added a very thin column width to create icon side navigation designs. Get started with our new Icon Navigation pattern.
Bar and column charts have joined line chart with the ability to set a minimum and maximum y-axis display value. Use this to always show up to 100 percent or to ensure target reference lines are always displayed.
As a bonus, you can now turn off the border on your card layouts. This comes into play when designing card layouts that touch or when working with dark colors.
We've continued to make improvements to the rich text design experience. Now you can configure web links and images using a visual designer, in addition to the styling controls we released in 19.2.
In this release, we are adding a new way to populate data in a read-only grid using the guided design experience that debuted in 19.2. Now, in Design Mode, the data parameter of the read-only grid has a new option to Choose rule. With this option, you can use the rule picker to select an expression rule to populate the grid. You can even use a handy dialog to easily configure the inputs to your chosen rule as needed. And, of course, Appian will automatically generate formatted columns based on the data.
In this release, we are introducing new connected systems to popular Microsoft services. You can now quickly and easily integrate with Microsoft SharePoint and Dynamics CRM 365. Create, modify, and query Dynamics and SharePoint data using a convenient, guided experience to integrate Appian with your Microsoft suite. There is support for both per-user (authorization code) and service account (client credentials) authentication, so regardless of your authentication preference, you are good to go.
Web APIs now accept document uploads as binary request bodies. This means that external systems can push documents to Appian. Each API call can then pass the newly uploaded document into a process for routing, task assignment, and more.
Both integrations and web APIs can now send and receive documents as binary. This opens up a world of possibilities for Appian document management.
Creating Web APIs is even easier! You can now start by selecting a Web API template right away and we’ll populate the properties and definition automatically.
If you don’t want to use any of the given templates, you can always choose Create from scratch and define it yourself.
Dealing with dates in JSON strings has never been easier. The newly evolved a!fromJson() function has the ability to identify ISO dates and datetimes in JSON and automatically convert them into Appian dates and datetimes. This also works for new integrations with Response Body Parsing configured.
The function has also been improved to better handle 64-bit integers. When a JSON string contains an integer that's too large to fit in 32 bits, a!fromJson() will convert that field to a string rather than setting it to null.
For integration objects, you can now define a multipart/form-data request body using an expression. This flexibility is especially helpful when calling web services that accept a dynamic number of documents or have optional form parts.
We want you to have a complete experience when tracking changes in Appian. With this release we've added support for comparisons between versions and across environments for Decisions and all types of Connected Systems and Integrations (even those created using plug-ins!). Additionally, you can also compare security configurations across environments for all object types and we've added more comparisons for process model properties and nodes.
This complete object comparison experience will enable you to perform thorough change reviews and better prepare for deployments!
Appian is committed to web accessibility, and in this release, we've added another way to increase comprehension for screen reader users. Now you can add alternative text to branding logos on Sites and Tempo so users know which logo they're viewing. Configure this setting in the Administration Console for Tempo or in Site branding configurations.
With the Integration SDK, you can now build connected system plug-ins that can download documents from external systems. In fact, we use this capability in our own SharePoint Connected System, and we wanted to expose this capability to you as well.
Keeping information about users and their roles in your organization up-to-date in all of your systems can be a daunting task. Appian now makes it a bit easier by looking at incoming SAML assertions during sign-in and updating Appian user profiles and group memberships accordingly. This guarantees that if one of your users changes roles, that change will be automatically reflected in Appian as soon as they next sign in. This applies when users are created via SAML sign-in as well, allowing the newly created user to get started with the right levels of access in Appian for their role.
Make it clear to users when they're viewing secure, classified, or test data by displaying a banner atop every screen in Appian, including the login page. Administrators can configure the banner text, color, and text color.
Starting in 19.3, export packages (.zip) will be automatically cleaned up after they've reached a certain age. By default, the retention period is 30 days. Specify how much export history you want to keep to manage your disk space more effectively.
Rule performance metrics and import history in the Admin Console is now persisted across Appian upgrade or hotfix process. With this, you will be able to compare rule performance before and after an upgrade or hotfix.
Appian Cloud now supports dynamic routing when integrating with customer networks by using the Border Gateway Protocol (BGP).
This new feature greatly improves VPN tunnel resiliency by automatically rerouting traffic in case a failure in the tunnel or one of the nodes is detected.
For customers using Appian Cloud High Availability (HA) or those implementing custom configurations involving multiple application servers, this feature simplifies VPN tunnel configuration.
For details, see Dynamic VPN Routing.
Appian Cloud now offers customers the option to store backups of their production sites in a secondary geographical region within the USA for disaster recovery purposes.
When Enhanced Business Continuity is enabled, customers have a guaranteed recovery point objective (RPO) of 4 hours in the event of a region-wide failure where the customer’s environment is hosted.
This option is additional to the existing backup policy which replicates customer production data across multiple availability zones within a single region.
This feature is only available to Appian Cloud customers enrolled on Appian Support and hosted in USA commercial regions. This feature needs to be purchased separately. Please contact your Account Executive for pricing details.
For customers with FedRAMP compliance requirements, the addition of GovCloud (US-East) region gives them more options.
Support for GovCloud (US-East) Region in Appian Cloud provides customers with sites hosted in GovCloud (US-West) with users in the east coast with improved communication speeds and experience, without them having to do any changes or additional work.
Note: this improvement is not applicable for customers with sites configured with VPN-only access.
Appian Cloud now supports hosting Appian Cloud sites in four new regions:
Customers can use these new regions to better serve their users and operations globally.
Customers in need of hosting new sites in these regions or wish to move their existing sites to one of them should contact their Account Executive.
For a full view of all available regions and other information please visit the Appian Trust Center.
AN-137647 - High
The following functions or components have newer, improved versions in this release. Existing, old versions of these components in your applications will continue to function normally but will be renamed on update to indicate that they are older versions. As always, make sure you are using the right version of the docs for your version of Appian. See Function and Component Versions for more information.
New version allows fields in JSON strings that contain ISO dates and datetimes to be automatically converted to Appian dates and datetimes.
In addition, fields in JSON strings that contain integers that are too large to fit into 32 bits will be converted to strings instead of being set to null.
The features listed below are deprecated and will be removed in a future release of Appian. Do not begin using deprecated features, and transition away from any prior usage of now deprecated features. Where applicable, supported alternatives are described for each deprecation.
The ability to connect with Dynamics using the Dynamics connector functions a!dynAssociate, a!dynCreate, a!dynDelete, a!dynDisassociate, a!dynRetrieve, a!dynRetrieveMultiple, and a!dynUpdate has been deprecated and will be removed in a future release of Appian. Use the Dynamics connected system to integrate with Dynamics instead.
The ability to connect with SharePoint using the SharePoint connector functions a!shpCopyDocumentFromAppian, a!shpCopyDocumentToAppian, a!shpInvoke, and a!shpInvokeWriter has been deprecated and will be removed in a future release of Appian. Use the SharePoint connected system to integrate with SharePoint instead.
Previously, the 4,000-character limit for Record Type titles could be subverted by using the expression editor. In 19.3, you will not be able to save changes to a Record Type when the title exceeds 4,000 characters.
When a Related Action chains to a task form built using the (deprecated) Forms Designer, the task form is no longer displayed inline and the chain breaks. Instead of seeing it inline, you return to the record view or record list as normally happens when the chain ends and the task is available in the task list in Tempo.
On This Page