Most self-service options are available to all LeanIX customers, but some are edition-specific. Please reach out in case of doubt.
As a LeanIX administrator, you have the following options to individualize the way your users work with a Fact Sheet:
Encourage the usage of Tags: Tags are a great way to cover your own requirements. Every user can create their own tags, while an Administrator can create tag groups.
Use the following link to learn more about Tagging.
Bring your own Subscription Types: Use role definitions (e.g. Application Owner, Software Architect) that are known by everyone in the company.
Configure the shown sections and attributes: Control what information is shown, and whether it is considered as mandatory. Set the weight of sections to "1" to treat them as mandatory, or to "0" for optional.
Learn more about Fact Sheet Completeness here: Data Quality Management
Especially in onboarding, it is helpful to hide all sections that are not in use. This allows users to focus on the required information. It is safe to hide a section - no data is removed, it is even still accessible via the API.
As an Administrator, you cannot only edit the appearance of a Fact Sheet, but many other settings in self-service:
The Administration area is always accessible via the drop-down at the top right.
Every user - not only administrators - can update their profile, change their password and control their notification settings.
In the Add-Ons area you can access Surveys and Metrics.
At administration, you can manage your users, control settings like Tagging or Subscription mode, and even set your own Logo & Color.
For developers and integrations, you find several tools here as well.
You can find more information at Administration Overview.
In addition to the Self-Service configuration, the Configuration Add-Ons allows you to modify the data model, fact sheet appearance, labels & descriptions, permission model and much more. The configuration is executed by LeanIX Customer Success.
Depending on your edition, different Configuration Add-Ons are available. Please reach out to learn more.
LeanIX comes with a Best practice data model that is well-probed for all typical Enterprise Architecture use cases. The idea of the Add-Ons is not to create a completely new data model, but rather to tweak it such that it fits perfectly with your companies use cases and requirements. The following table show typical goals and how to achieve them.
Reduce the number of tags
Tags are a powerful instrument to bring own information to LeanIX. Usability degrades however when two many tags are used (more than 5-7 for a Fact Sheets). The Configuration Add-Ons allow to turn certain tags into attributes - see https://docs.leanix.net/v4.0/docs/modeling-guidelines#section-tags-vs-attributes
Use explicit relations
Besides the best-practice data model, LeanIX allows you to use requires/required By relations to connect Fact Sheets, e.g. Processes to Interfaces. As this relations are untyped, usability decreases when using them to often. The Configuration Add-Ons allow you to turn them into regular relations.
Fine-tune data completeness
On the best-practice data model, LeanIX allows you to define sections as mandatory or optional for Fact Sheet completeness. With the Configuration Add-Ons , you can fine-tune this to attribute level.
Support new Use Cases
GDPR is a great opportunity for EA, as it requires to maintain a high data quality around the Applications, Data Objects and Interfaces of a company. The Data Protection Officers often have a highly specialized view on their requirements. The Configuration Add-Ons allowf you to support this view without decreasing the general usability.
IT Service Management
In many companies, the concept of a Business Service is established to bridge the gap between Business Capabilities and Applications. LeanIX customers found ways to bridge the gap within the existing data model (e.g. use an Application with a tag "Business Service", use a third-level Business Capability as Business Service), but especially when considering an integration with an ITSM system like ServiceNow, it makes sense to consider a dedicated "Business Service" Fact Sheet.
Advanced IT Architecture Management
Customers use the IT Component Fact Sheet to address use cases like Technology Stack - Reference Models and Cost Management. For this, the standard model of IT Component, Tech. Stacks and Providers works great. More mature customers try to bring more dimensions of their IT Architecture into LeanIX, e.g. instances or platforms, to address use cases like Microservice or Container Management. Here, usability can suffer quickly from an overfrauded IT Component Fact Sheet, and it make sense to consider e.g. a dedicated "Environment Fact Sheet".
Tweak Permission Model
LeanIX helps companies to establish a vivid, open collaboration about their IT landscapes. However, there are cases where company augment this openness by deliberately introducing exceptions, e.g. allowing only some persons to see costs or other explicit content, or allowing a data protection officer to have the sole opportunity to set a certain approval. In this case, the Configuration Add-Ons can help you to bring in new roles or permissions.
Working with sub-organizations
In large companies, it is often desirable to create an open exchange, but the way towards this goal is long. If your company consists of sub-organisations that are not (yet) allowed to share certain content, the Configuration Add-On might help you to bring in this information into a shared workspace while maintaining a clear separation.
The following screenshot shows a simple configuration to address the GDPR use case. Within the Application Fact Sheet, a new Section called GDPR is created. The included attributes are handled as every other attribute in LeanIX.
Behind the scenes, LeanIX Customer Success uses five different models to conduct the configuration:
The Data Model allows adding new Attributes (e.g. Text, Number, Single Select, Multi Select), Relations, Fact Sheets, External IDs and Validators. Standard functionality is available for all new Elements (Filter, Table View, Import / Export, Survey, Dashboard, Accessibility via GraphQL API).
The View Model allows changing the appearance of each single Fact Sheet Type by fine-tuning the look of existing and new elements (e.g. assign symbols and colors to Single-Select Fields, control per attribute whether it is included in completeness calculation).
The Translation Models allow individualizing help texts, label, section names, report names and more. Different languages are supported - currently EN and DE in the standard model.
The Authorization Model allows to fine-tune existing roles (e.g. make a certain attribute only editable by an Admin) or creating an entirely new role with certain privileges.
The Reporting Model allows changing the menu structure for existing and of custom reports, as well as configuring own Matrix, Landscape, World-Map or Roadmap reports.
Q: Why can't I just reuse an existing Fact Sheet Type for another purpose (e.g. use the Provider Fact Sheet which is not in use to model a Business Service)?
A: The existing Fact Sheet Types are highly specialized to serve their role in the Best Practice Data Model and for the supported use cases. Certain reports rely on the out-of-the-box dependencies. Hence, you run the risk to seriously confuse your users when misusing the existing types.
Q: Why is configuration not available in self-service?
A: The adaptions allow powerful modifications on the data model that might cause data loss or legal violations if used in a wrong way. As LeanIX is responsible for the data integrity and quality of service, these modifications can currently not be executed in self-service.
Updated about a month ago