2 - Writeback Overview

Your flight alert inbox analyst may want to take action based on the object data they encounter. In Foundry, an Action is a transaction that changes the properties of one or more objects. Say, for instance, your analyst clicks a button in your Workshop module to escalate an alert from Medium to High priority. You'll want that change propagated back into your Foundry datasets so your colleagues can be sure they're working with the latest data. The process of keeping editable Ontology data in sync with your enterprise data asset is called “writeback.” As you'll see in the next task, you will need to manually enable writeback on your object and link types before you can configure Actions that affect them.

The clickable diagram below illustrates the relevant dynamic whereby ontology edits made through your Workshop application are captured as a dataset back in Foundry. Your colleagues wanting to build analyses and pipelines on top of flight alert data should use Flight Alerts_edited rather than the original backing dataset. This model will take some getting used to, and we will continue to explore it throughout the track.

📚 Recommended Reading (~8 min read)

The instructions in this tutorial assume the foundational knowledge from this task and in these strongly recommended readings. Take the time to review them before moving on.

• Actions Overview
• Enabling Ontology edits