​

Hello Everyone! Thank you so much for attending our webinar on Metamodel Configuration. 

We couldn’t be happier to see so many people on the call and engaged with questions! I will try my best to answer questions we couldn’t get to below. Be on the lookout for an email with the meeting recording. I will also post a link to the deck we used to present so you can reference it later!

Q&A During Webinar (in order they were asked)

• Any plans to add other languages from Countries (e.g. Chinese, Japanese, etc)
  • I misspoke originally on the call. I have heard some internal whisperings of this but nothing has officially made it to the roadmap. Please submit a feedback ticket to our product team here. I believe many customers would benefit from these additions. A feed back ticket is the best way to get this on our Product Team’s radar. 
• Is there a way to adjust the order the custom fields are displayed , For example can we keep Description first and then Status the order it displays on screen for that section ?
  • Yes, by clicking on the field you want to adjust, you can click the icon with the two arrows, as seen below, and drag/rearrange the items within that subsection. Special Thanks to Cliff Elgin for helping answer this during the meeting!
• Can the custom fields be reused & be adjusted across various Factsheets?
  • At this time, There is no save Template functionality. You would have to create the Custom Field form scratch. Please consider submitting an idea here.
• Is there a way to add a list as custom attribute on a factsheet type?
  • This needs to be done by Field. 
• Are there any plans to allow a single/multiple select field to read the options from a source other than the hardcoded options in the configuration?
  • Not at this time. Please consider submitting an idea here.
• When I enable the 'draft' status, it looks like it could only be updated to that status online (vs Import process). Is that expected behavior?
  •  Yes, this is currently expected behavior. You cannot change quality seal status via imports currently. However, you can do it much more efficiently by using table view and utilizing the inline editing function which is very similar to Excel’s format dragging option.
• Do we need to create a new role if we wanted to hide specific fields on a fact sheet from others? Same for making a field view only/edit?
  • If you are starting with OOTB roles (i.e. Viewer & Member), then yes it would be recommended to create a new role for the specific team you had in mind when it comes to blocking permissions as someone needs to be able to edit everything within the workspace (your members). For example, if you have a ‘compliance team’ that should only be concerned with the compliance section of a factsheet, then it would make sense to block their ability to edit things not related to compliance. Note: Creation of user roles is only possible if your workspace is managed by an external IDP. More info.
• Can custom fields be shared between Factsheet Types? For example, creating a Business Priority field that is a single select that can be used by Application and IT Component... Do we create one for each Factheet Type? Can we reuse one definition on the other?
  • You would need to add it to both fact sheet types individually. The definition can be mostly the same. You may want to experiment with Tags for this purpose if you’re trying to quickly identify the most important aspects of your business’ IT. More Info
• Is there a way to clone an attribute? Say I want to have 5 single-select attributes with the same options (e.g. approve / deny / uncertain) for 5 different approvers. Right now I have to create these 5 attributes one by one.
  • You would have to create that field and list of choices individually for each factsheet. However, once you send a survey to these approvers, they will all see the same list of options you configured for their corresponding factsheets, and their choices will be listed in the survey results. I hope this answers your question! Please reach out to your CSM if it’s still unclear as to how to proceed.
• Could you please share the links to these videos?
  • Yes! I will share the deck with the videos in this post!
• What is the difference between Application and Application Only in the subtype drop down?
  • This is referring to what fields you will be configuring depending on your selection … ‘application with subtypes’ means you will be configuring the application fact sheet and all of it’s subtypes while ‘application only’ means you will only be configuring the main application fact sheet without any subtype classification. Continuing on, if you only wish to add a specific field to the “microservice” subtype and not have it shown on any of the subtypes/main app fact sheet, you would select ‘microservice’ from the drop down. I hope that answers your question!
• We need a conditional section based on a value different from Yes (we have a list of 10 elements). If it is distinct of Yes then it should show several fields.
  • This is also possible. The rule for conditional fields to work is it has to be either a Single- or Multi-Select field type. You can then determine what fields pop up for each response or combination of responses.
• Will wild search (Not only on filterable fields but also like descriptions, notes etc..) be on the roadmap?
  • At this time, I do not believe it’s on the roadmap. However, with AI features getting stronger and more thought-out every day within LeanIX, I suspect this could be a necessary evolution. However, it doesn’t hurt to submit a product idea! Please consider submitting an idea here.
• How do Factsheet Permissions work with Virtual Workspaces in relation to Roles? Do similar roles must be created for each Virtual Workspace?
  • This question relies heavily on how you manage your roles currently within LeanIX (either external IDP or internally) and the Virtual Workspaces themselves. I recommend connecting with your CSM on this to get a definitive answer.

Q&A Section Questions:

• For MMV4... for App FS, I see Bus App is a sub type, is there a road map to add other types or classification? We are in the process of AppRat project with LeanIX PS team currently, do you suggest to upgrade to V4 from 3 for the TIME and 6R (which is also our current scope of the project).
  • For the first part, currently there is no more plans to add more subtypes for the foreseeable future. The ‘Business Application’ subtype was created to ensure clear distinction if customers were to implement the other subtypes “Deployment” and “Microservice”.
  • For the second answer, MMv4 is still optional for customers to adopt if it aligns with their business goals. You can opt to add the 6R and TIME frameworks yourself to the application factsheet using the same workflows we highlighted during the webinar.
• Reg: configure permissions, to what extent we can go with it? What are the different ways, we can enable and control the permissions - who can and cannot? The permissions needs to update configuration to ensure only responsible people can manage FS details and that only appropriate roles can modify subset of initiative fields.
  • Only Admins will have access to Edit permissions as this is part of the Metamodel configuration only available to the Admin Role. We have CRUD Rights (Create, Read, Update & Delete) and its configurable in general functions of the Factsheet as well as to Fields and relations. So pretty much all Factsheet functionalities. Please visit our documentation here.
  • To your second point you can enable the "Subscription Check" for fields that will achieve what you are looking for meaning only if a person is subscribed responsible to a Factsheet will they have that capacity to edit Factsheet fields.

Here is the link to the webinar deck: https://treibglasnet-my.sharepoint.com/:p:/g/personal/beau_nelson_leanix_net/EfJZ7771nd1Pp6p7ygbeYM8B6G_pdOUVUcdJbf_7k6fj1g