# Learning Palantir Foundry 🚀 Action Types are what decisively separate Foundry from read-only BI. Approvals and assignments become safe, validated, structured writes. 📌 Title and Feature URL Title: アクションタイプ URL: 📝 Overview An Action Type defines a set of changes a user can apply to ontology objects, properties, and links in a single transaction. It encapsulates both the data modifications and any side effects triggered on submission, letting users think in terms of overall goals rather than individual property edits. 🔧 How It Works - Write-back to the ontology: when an action runs, all changes are committed to the ontology and reflected across every app. The latest object data, including user edits, is captured in the object type's write-back dataset. - Parameters and defaults: parameters standardize input, supporting default values, filtered dropdown results, and overrides. - Rules: define when and how an action executes, including object relationships and property constraints. - Submission criteria and validation: validation rules control execution eligibility and error handling before changes persist. - Action logs: a full audit trail of every executed action supports accountability and compliance. 🛠 Practical Usage - Run an "Assign Employee" style action that changes a role property, auto-creates a manager-employee link, and notifies stakeholders in one transaction. - Embed submission criteria like "only a director may submit amounts over 1M yen" as validation, replacing Excel-plus-email approvals with structured operations. - Reuse the same validation logic and workflow consistently across every user-facing app. 🎯 Use Cases - Standardize status changes, approvals, and assignments as permissioned, criteria-bound operations. - Let non-technical users safely execute multi-step changes spanning several objects. - Use the action log of every operation as an audit trail for internal controls. ⚠️ Caveats - Actions execute only after passing their validation rules, so submission-criteria design drives the quality of your controls. - Changes propagate immediately across the ontology and all apps, so do not leave rule and parameter design ambiguous. #PalantirFoundry# #Ontology#

# Learning Palantir Foundry 🚀 The first move that turns a dataset into a business object. How you design Object Types largely decides downstream app performance and UX. 📌 Title and Feature URL Title: オブジェクトタイプ URL: 📝 Overview An Object Type defines the schema for a real-world entity or event. A single occurrence is an object instance (e.g., employee "Melissa Chang"), while a group is an object set (e.g., all tenured employees). This mirrors how datasets handle rows and filtered row collections. 🔧 How It Works - Primary keys and identity: objects need a primary key to uniquely identify instances. Mapping a data source to the object type lets you create and display objects in applications. - Properties: define an object's characteristics, with options such as edit-only properties, required properties, and shared properties reused across multiple object types. - Property types: support time series data, geospatial information, and struct types (nested, complex properties). - Display and search: title/display settings and search indexing improve discoverability inside apps. - Value Types: custom value types with versions, permissions, and constraints standardize representation across the ontology. 🛠 Practical Usage - Connect an employee directory or enterprise data to an Employee object type, converting raw datasets into actionable ontology instances. - Nail down primary key design first and index for search to secure downstream app performance and UX. - Use struct properties to auto-map hierarchical data, combined with shared properties for reuse. 🎯 Use Cases - Turn a customer master into a Customer object so the whole company shares one identity. - Model sensor-equipped assets with time series properties to retain operating history. - Model sites and stores with geospatial properties for map-based search and aggregation. ⚠️ Caveats - Primary key design, property types, and search indexing largely determine later app performance and UX, so treat them as your most important modeling decisions. - You must correctly map a data source to the object type before objects can be created or displayed. #PalantirFoundry# #Ontology#