Application Rationalization

​@mvanrooijen a couple of approaches may work for you.

1-Add an additional attribute on the application factsheet in a relevant section. I would suggest a “Single-select” type with a specific list of values as set by the code bases you have.

2-Create a relationship to a factsheet type (IT Component or Platform) which have the code bases already defined as individual fact sheets and add the relationship to the relevant applications.

If you want to get fancy these can be conditional and only activated if the required condition is met, see the Conditional Attributes documentation.

Attributes are easier for users to filter in inventory or reports but the relationships can be too with the “advanced filter”.

​@mvanrooijen - Hope you’re doing well! Adding to Justin’s earlier post, depending on the number of Applications that you would like to track custom codes languages on, the tagging functionality can be leveraged. A tag could be attached to the Application for quick insights and reporting in a streamlined way.

To utilize the tagging functionality, please follow the below steps:

1. In the administration area, open the Tagging section.
2. Click New Tag Group.
3. Fill in the needed information, including name, fact sheet type, and mode. Selecting a fact sheet type ensures that the tag group is available only for that type. You can select multiple fact sheet types or even all. The mode of the tag group defines whether it is single-select or multi-select. Providing a description is a good practice as it makes it easier for other users to understand.
4. Click Add.

Documentation of how tagging can be utilized today: Tagging Capabilities.Thank you for leveraging the LeanIX Community platform for your query.

Thank you,

Niral Mehta

Hi All!

Decided to go with ​@Helder.Luz his answer. It seems the best suited to our needs.

Thanks for giving me your insights.

​@mvanrooijen the IT Component relationship is the most robust and full-featured as ​@Helder.Luz explained and if that is best suited to your use cases and needs then that is what counts.

The good thing about LeanIX is it is not a fixed choice and there is the flexibility to change approach over time.