Recently active topics

We are seeing a recurring data quality challenge in LeanIX and wanted to learn how other organizations are addressing it.In our setup, application fact sheets are filled by Application Technical Owners and reviewed/approved by Business Owners. While most users complete the fields, many are not familiar with EA terminology and sometimes enter conflicting values in related fields.A common example is: TIME = Eliminate 6R = Retain We’ve identified a few possible approaches and would like to understand what works best in practice: Automation / Rules-based warnings Using LeanIX automations with defined rulesets to warn users (or block approval) when conflicting combinations are selected. User education Creating and circulating cheat sheets, tooltips, or guidance documents explaining how related fields (TIME, 6R, Business Criticality, etc.) should be aligned. Approval-based governance Relying on Business Owner review and quality seal approval to catch and correct inconsistencies. Questi

Hi,I have a question regarding the ServiceNow–LeanIX integration. I’m trying to understand how to synchronize specific fields from ServiceNow into LeanIX.Our current source of truth is LeanIX, and the out-of-the-box integration performs a one-way synchronization from LeanIX to ServiceNow. However, we have a use case where the Accountable Manager is updated in ServiceNow and needs to be reflected back in LeanIX.Do you have any advice or recommendations on how to implement this? Also, do you know whether the out-of-the-box integration supports bi-directional synchronization for the same field?Regards,

Hello everyone, I hope you're all doing well.I'd like to ask for your guidance on two specific use cases in LeanIX:Cost Visualization: Is it possible to generate pie charts or bar graphs that show the Total Cost of Ownership (TCO) of applications? We only find sums of quantity, but not much configuration. And we'd like to group by specific tags for example. Is it possible? We've already have the TCO Extention  Version Management: What's the best practice for seeing evolutionary improvements in an application while maintaining its history? My goal is to track the evolution without having to create multiple new Fact Sheets for each version, thus avoiding unnecessary duplicates in the inventory.Thank you very much in advance for your recommendations!

Hello LeanIX Community, I’m working on a setup where I need to use parent/child relationships inside Application Fact Sheets to run some calculations and to control the visibility of other fields based on whether a parent exists.I think I’ve hit a fundamental limitation in LeanIX and I’m looking for advice or best practices to handle it.Bit of context I have Calculated Fields that depend on whether a Fact Sheet has a parent. I also need to show or hide certain fields based on this logic. So basically the UI depends on the calculated value, and the calculated value depends on the presence of a relation.IssueLeanIX does not evaluate calculated fields:when a Fact Sheet is first created, when the page is opened, or immediately after adding/removing a relation.They only update after a browser refresh. This creates two problems:At creation time, calculated fields are always Blank, even if the logic should return “No parent”. After adding a parent relation, calculated fields do not update rig

Bonjour,Ce message pour vous informer qu’un groupe d’échange entre clients français LeanIX a été créé il y a quelques mois (initiative indépendante des équipes SAP).En termes de format, c’est assez simple : 1 h sur Teams tous les 4 à 6 semaines environ. Nous essayons de définir l’agenda d’une session à l’autre.Si vous souhaitez en faire partie, envoyez-moi un message en privé avec votre adresse e-mail. 

Users who were previously assigned to specific access entities in LeanIX had these entities removed from their accounts. As a result, their access to the corresponding factsheets was revoked.

Hi Community! My name is Andrés. I'm working as a Senior Solution Architect for Movistar ArgentinaWe're taking our first steps toward implementing SAP Leanix. I'm very happy to join the community to share knowledge and experiences.I'm currently taking the Leanix training courses at https://learning.sap.com/ and I'm having a problem: I can't connect to the Demo workspace using the username certification@leanix.net (wrong user/pass). Any help would be greatly appreciated.Best Regards

We have set up the Business Owner subscription to be required when creating a new application fact sheet but I want it to be optional and no longer required. Only the Application Owner should be required. When I go to change this, the "Mandatory" check box is greyed out and it says "This can only be changed in self-configuration". How do I change this so it's no longer required when creating a new fact sheet?  

Los principios de Arquitectura Empresarial suelen ser uno de los pilares de la gobernanza: orientan decisiones, ayudan a alinear iniciativas y sirven como referencia común entre negocio y IT.Sin embargo, en la práctica no siempre es fácil: comunicarlos de forma efectiva mantenerlos actualizados en el tiempo asegurar que se aplican de verdad en proyectos e iniciativas medir su adherencia más allá de documentos estáticos Me gustaría conocer cómo lo estáis abordando en vuestras organizaciones, y en particular si utilizáis LeanIX de alguna forma para apoyar este proceso: ¿Dónde y cómo documentáis los principios? ¿Los relacionáis con aplicaciones, plataformas, iniciativas o decisiones arquitectónicas? ¿Tenéis algún mecanismo para evaluar o evidenciar su cumplimiento? ¿Cómo gestionáis su evolución cuando cambian la estrategia o el contexto tecnológico? Me interesa especialmente saber si alguien ha conseguido pasar de los principios como “declaración teórica” a principios realment

Hello,I’d like to raise an conversation about the topic how to utilize SAP LeanIX for the EU AI Act.We started with applications by enhancing the metamodel following the proposal of SAP LeanIX:The mandatory fields are conditional and except AI Usage they are conditional based on what is selected in the AI Usage single selection.To simplify the factsheets owners data entry I created a survey with all this information inside.We also added the AI Potential to Business Capability Factsheet.Next step is to apply this approach to the component factsheet.We are still discussing how calculate an AI risk score and -level. Did you do already something like this? What’s your approach/formular?Best regards,Carsten

Gartner habla cada vez más de AI Debt: la deuda que se genera cuando priorizamos resultados rápidos en iniciativas de IA frente a la sostenibilidad a largo plazo.Según Gartner, la AI Debt aparece cuando decisiones (intencionadas o no) crean cargas futuras en forma de:retrabajo ineficiencias riesgos de cumplimiento dependencia excesiva de soluciones puntuales dificultad para escalar o pivotarLo interesante es que Gartner no plantea eliminar la AI Debt, sino gestionarla estratégicamente, asumiendo que cierta deuda es inevitable cuando se innova rápido.Desde una perspectiva de Arquitectura Empresarial, esto plantea preguntas muy relevantes:¿Estamos registrando y entendiendo dónde se acumula esta deuda? ¿La vemos solo como un problema técnico o también organizativo, de datos y de gobernanza? ¿Tenemos visibilidad de cómo las decisiones de hoy condicionan nuestra capacidad futura de escalar la IA?👉 Me interesa mucho saber:¿Estáis hablando de AI Debt en vuestras organizaciones? ¿Cómo estáis

En muchos proyectos de Arquitectura Empresarial aparece, antes o después, la necesidad de agrupar aplicaciones y capacidades por dominios (por ejemplo, Customer, Finance, Supply Chain, HR, etc.).Sin embargo, LeanIX no ofrece actualmente una estructura clara out of the box para modelar dominios como tal, y he visto enfoques muy distintos según la organización: uso de tags o convenciones de naming subtypes o campos custom reutilización de otras entidades (con mayor o menor encaje) o directamente decidir no modelarlos  Me gustaría abrir el debate y conocer vuestras experiencias: ¿Usáis dominios en vuestra implementación de LeanIX? ¿Para qué casos de uso concretos os resultan útiles? ¿Cómo los habéis implementado y qué dificultades habéis encontrado? ¿Creéis que es un concepto necesario o prescindible? Creo que compartir experiencias aquí puede ayudarnos a evitar tanto el over-modeling como quedarnos cortos en la estructura.

I hope everyone is starting their PTO or starting it very soon. Before I head out for some time off I wanted to share a recording of the What’s New Webinar for those who did not register and were not sent the recording automatically. Please find that here.We look forward to seeing you in our Q1 session, but in the meantime have a safe and happy holiday season!

Hi everyone, I’m currently working with the MCP Server in SAP LeanIX and need some guidance on best practices for API integration and fact sheet retrieval. Has anyone here worked on similar setups or have recommendations for optimizing the data flow? Would really appreciate your insights!