Forms

We do not recommend using Foundry Forms as this product is in sunset. Instead, for data entry or writeback workflows on Foundry, we recommend building user input workflows with the Foundry Ontology. Using the Ontology, relevant data structures can be represented as object types and the writeback interaction configured with Actions. There is no deprecation timeline yet for Foundry Forms, and this will not impact existing resources until further notice.

Actions provide more robust and granular control over the permissions associated with adding, editing, and deleting data, including respect for restricted views and configuring complex conditional permissions. Furthermore, Actions can be backed by Foundry Functions, allowing for more expressive writeback logic.

In addition to the built-in Form builder in the Actions configuration, Actions are natively supported in Workshop and Slate where complex data entry user experience can be crafted with the full suite of application building tools.

Actions also automatically generate API bindings for the Foundry API, where external applications write data into Foundry, and interface with webhooks, through which Actions can write data into external data systems or trigger other downstream effects.

There is currently no timeline for deprecating Foundry Forms, and existing implementations using Foundry Forms will be supported. New workflows are strongly recommended to use an ontology-based approach, and it is not expected that Foundry Forms will receive new features, enhancements, or non-security-related fixes.