LeanIX
Keeping Track of Fact Sheet Resource Links - The Smart Way
A customer wanted to filter applications by whether they have a documentation resource. Calculated fields can't see documents. The elegant answer? Make LeanIX call itself.
Automation
LeanIX
The Deletion Scope That Doesn't Exist: Clearing Fields with Tags as a Proxy
The problem: syncing away data is harder than syncing it in Most people think about integrations as a one-way street of adding data. A 3rd-party system sends you a payload, you map it onto your LeanIX Fact Sheets, one field gets updated, everyone's happy. But there&
LeanIX
Inheriting Lifecycle Data the Smart Way: From Applications to IT Components
Copying lifecycle dates from Applications to IT Components fails the moment relations go m:n. Here's how to merge them into a correct support envelope — and enable it as a switch.
LeanIX
When 'Just Copy It to IT Components' Turns Into 300 Manual Steps
A customer came to us with what sounded like a simple request: "We want the AI Governance fields on IT Components and Assets too, not just Applications." Fair enough. LeanIX ships AI Governance as a standard feature — but only for Applications. And you cannot just copy field definitions
LeanIX
The 720-Checkbox Problem: Automating LeanIX Permission Transport
The Math That Made Us Automate Let's do some quick napkin math. Picture a typical LeanIX workspace: * 9+ Fact Sheet types (Application, IT Component, Provider, you know the drill) * ~10 information items per type (fields, relations, fields on relations) * 2+ user roles beyond Admin (at minimum VIEWER and
Automation
Copy-Pasting LeanIX Automations Without Losing Your Mind (or Your Logic)
You've built the perfect automation. Twelve steps, three conditions, beautifully orchestrated. Now you need it on a different Fact Sheet type. How hard can it be? (Spoiler: Very.) The Problem: Copy Doesn't Mean Copy LeanIX automations are powerful. They're also surprisingly fragile when you
Webhooks
The Art of Delayed Webhooks: Teaching LeanIX Automations to Wait
"There was a version conflict. Someone else modified this Fact Sheet while you were editing." If your users see this message regularly, your automations might be too eager. Here's how we teach them some patience. The Problem: Automations That Are Too Fast LeanIX webhooks are beautifully
AI
Zero Clicks, Zero Code: How an AI and an MCP Server Configure LeanIX Workspaces
"Create a calculated field that shows how long a Fact Sheet has been in a specific data quality status. Add translations in English and German. Make the field visible in reports." Three sentences. Zero clicks. Fifteen seconds later, it exists in LeanIX. Welcome to the future of EA