Hi Melissa,

we do utilize the subtypes in different ways:

We use additional subtypes e.g. to show that some factsheets just for grouping purpose. These ones are approved by a scheduled job and are reduced to very basic information (using conditional attributes.

Some factsheets are enhanced by several subtypes, e.g. the IT component, where we added DBMS, Operating System and others. Based on this subtype we show (and hide) different attributes.

I further extend the use subtypes in combination with conditional fields to enable different mandatory fields for different subtypes, e.g.: For software components we are using the SSO enabled, but that doesn’t make sense for hardware so we mandatory, but not showing it for hardware. So if you want to approve an SW-IT-Component SSO is mandatory, but not for HW, because it is not shown.

From my point of view the enhancement by new subtype is very useful.

Best regards,

 Carsten

Hey Carsten,

Hey, great work on the subtypes in the factsheets! It's really cool to see how you're using conditional attributes and fields to customize the info for each subtype. Treating each subtype as a different component is so important. Thanks a lot for sharing!

@Carsten  Thanks for sharing!  We use subtype on the organization fact sheet but not anywhere else yet.  I understand the use case with the IT Components and field customization.  I’m not understanding the use case of the scheduled job - can you elaborate?

Hello @Kathy Chappel ,

we have a subscription role Factsheet Owner as accountable, who’s responsibility is to take care that the factsheet is (more or less) up to date. For nearly all factsheet types we break the quality seal after 6 month or a year.

We found some cases where we do not want to create additional work to the Factsheet owners to approve certain Factsheets, e.g. for the ones we just use for grouping purpose or the ones which are end of life. So I wrote a python script with a graphql mutation approving these factsheets.

…

graphql_mutation = """

mutation {

  updateFactSheet(id: "%s",patches: c{op:replace,

      path:"/lxState",

      value:"APPROVED"}], validateOnly: false) {

    factSheet {

      rev

      lxState

    }

  }

}    

    """ % (factsheetid)

...

This script runs scheduled, so that these factsheets are automatically approved.

Best regards,

Carsten

Adding to Carter's answer, if we create relations for specific subtypes only, LeanIX is smart enough to filter the selection of the relation in the target fact sheet type to only the appropriate subtypes. Very handy. 

We also use subtypes in quite a few factsheet types, and well as new fact sheets types.

Cheers.