昨日、6月25日。 ついに、おじいちゃんになりました。 今日、生まれてまだ24時間も経っていない孫に会ってきました。 本当に小さくて、 本当に可愛い。 命の尊さを改めて感じる、 忘れられない一日になりました。 長女・ミリ、本当にお疲れさま。 よく頑張りました。 そして、元気に生まれてきてくれてありがとう。 これからは、おじいちゃんとして、 たくさんの愛情を注いでいきたいと思います。 いつか、 「BIG BOSS」 そう呼んでもらえる日を楽しみにしています。 MAX ORIDO Yesterday, June 25th, my life changed in a beautiful way. I became a grandfather. Today, I met my grandchild for the very first time—less than 24 hours after being born. So tiny. So precious. So incredibly beautiful. It was a moment I’ll never forget. I’m so proud of my eldest daughter, Miri. She did an amazing job. And to my grandchild, thank you for coming into our lives safely. From now on, I’ll do my best to be a loving grandfather and cherish every moment together. One day, I hope to hear those special words… “BIG BOSS.” 😊 MAX ORIDO @miri559

# 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#