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&
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.
🆕 New Items * MCP server: Visual apps for fact sheets and relation explorer * Administration: Token Exchange for API authentication * Diagrams: Target architecture diagram improvements * Integrations: Zscaler discovery with the new OneAPI flow * Architecture decisions: MCP server enhancements * Architecture decisions: Decision-to-decision linking * Architecture decisions: Custom statuses 🗑️ Removed Items * Reports: Views
Or: How I learned to stop trusting my eyes and love hex editors I recently discovered an impossible situation in a customer workspace: they had two Applications in their LeanIX workspace with the exact same name. "That can't be right," I thought. LeanIX enforces unique display
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
For a more verbose list of roadmap changes, please get in touch for early access to the weekly / monthly e-mail digest or the RSS roadmap tracker feed. 🆕 New Items * Integrations: Better subscription management for the SAP Signavio integration * AI Agents: Web research agent * Discovery: Build and run custom discovery
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
🎉 Introducing: The LeanIX Roadmap Tracker Or: How we finally solved the "Wait, when did they add that?" problem Let's be honest: keeping up with the LeanIX public roadmap is... a challenge. At the last LeanIX Customer Community Meeting, we had the talk. You know the one.
The unexpected SCIM trick that saved our user lifecycle automation You've probably seen it on the LeanIX roadmap: improved User Lifecycle Management is coming. One of the highlights? Triggering actions when a user's department changes. Updates, subscription management, the works. Sounds great. But it can become
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
"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
"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