This content is also available at learn.palantir.com ↗ and is presented here for accessibility purposes.
📖 Task Introduction
Once you’ve identified the Actions you want your end users to take through your application interfaces, the next step is to configure writeback datasets that can contain the data edits those actions will generate (e.g., priority on alert 123 is changed from medium to high).
Let’s start by creating a writeback dataset for your flight alert and passenger object types.
🔨 Task Instructions
Open your flight alert object type in the Ontology Management Application (OMA).
From the left-hand menu, click the Datasources menu item.
Click the green ⊕ Generate button in the Edits block to the right.
A Foundry explorer window appears suggesting a name and save location for your writeback dataset. By default, the writeback dataset name is the name of the backing dataset appended with _edited. The default save location is the same as the backing dataset. Feel free to keep these settings.
Click the blue Save button.
At the bottom of the Edits block, click the large By actions only button to only allow edits to your object type through the Actions framework.
Save the changes to the Ontology by clicking the green Save button in the top right of the application.
Now, repeat this step for your passenger object type.
📚 Recommended Reading (~1 min read)
Read more about enabling edits through Actions vs other means in this brief article.