Skip to main content

We have several 3rd party relationships where we have key integrations to their applications, but our partner has full responsibility of those applications.  We want visibility to these targets, but prefer to not have them setup like our internal applications within LeanIX.  Their would be minimal data requirements vs the applications we own and manage so it would be less than ideal to have them all stored on the same fact sheet type.  The interface objects seem to only support the application fact sheet for provider and consumer so we are debating the best approach to get visiblity without a lot of overhead.

 

How are others handling this situation? - Thanks

That’s a good question.

Typically when users are modelling third party applications, the only use case would be to model all integrations around those applications without the need to model or manage those applications. For those cases, a good approach would be to add one Application fact sheet called ‘’3rd party Applications’’ and model all relevant interfaces towards this generic Fact Sheet. You can then use the naming convention of those interfaces to capture further details around the applications. I hope that helps!

Reply


Terms & ConditionsCookie settings