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.
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.
π New Items * Administration: Centralized Audit log experience * Transformations: Initiative Commitment & Time-Aware Landscape * Reports: Custom report agent * EA Assistant: Technology Successor Planning * 2026 - Q4 Roadmap Webinar ποΈ Removed Items * Agent-led toolchain Roadmap on SAP Road Map Explorer: Was in π§ On roadmap / About our roadmap π¦ Moved Items * Architecture decisions: Version
π New Items * Integrations: SAP SuccessFactors Parent Selection * EA Assistant: Toolchain Alignment Agent * Agent-led toolchain Roadmap on SAP Road Map Explorer * Meta model: Extension for agentic skills * Integrations: SAP SuccessFactors Custom Fields Mapping ποΈ Removed Items * Inventory: Configurable fact sheet creation form: Was in π In progress * 2026 - Q2 Roadmap Webinar: Was
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 * Architecture decisions: Version history * Reference Catalog: SAP Solutions Explorer * Discovery: AI agent and AI model discovery from Databricks * Discovery: SAP Integration Suite Integration to discover MCPs * Relation explorer: Advanced explorations * Arch. Guidance: Roles and Permissions * SAP AI Agent Hub as a single source of truth for in-use
π New Items * Dashboards: Create and edit with conversational interface * Integrations: Jira Cloud Enable OAuth-Based Authentication * Discovery: Do you know which local AI agents your employees are building and running today? * 2026 - Q3 Roadmap Webinar * Diagrams: MCP access and AI assistance * EA Assistant: Reports skills * AI agent and SAP discovery
π 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
LeanIX
π 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
Automation
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
"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
"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
Integration
The request sounded fairly typical: "We have a massive Excel file with our applications and interfaces that we use in our ERP project. This file needs to stay in sync with LeanIX because we cannot replace it in the short term β it contains too many columns and information that
News
This is The Fact Sheet Diaries, a brand new collection of our stories and ideas from the exciting world of SAP LeanIX, mostly written by me, Thomas, and sometimes co-authored by Lina, my fellow Aronis partner. You can subscribe if you'd like to stay up to date