Palantir Ontology Application Workflow

Overview

Use the generated Ontology SDK as the typed contract for a Developer Console application. Keep reads, Functions, and Actions distinct, and validate writeback before execution when the generated SDK and action support it.

Prerequisites

• Identify the Developer Console application, Foundry environment, selected Ontology entities, grant type, application restrictions, and data owner.
• Generate or select the OSDK language and version required by the application; do not guess object, property, link, Action, or Function API names.
• Read references/official-docs.md and the application-specific generated documentation in Developer Console.
• Prepare test objects and a non-production Action path.

Current Contract

• An OSDK is generated for a selected subset of an Ontology and supports TypeScript, Python, Java, and other-language generation paths.
• Application access is the intersection of the acting user or service user, OAuth scopes, and Developer Console restrictions.
• In TypeScript OSDK 2.x, generated definitions are passed to the client for object operations, Actions, and Functions.
• Action validation and returned edits are explicit options; validation-only and returned-edits modes cannot be assumed interchangeable.