"Any Of" Relation type
Matar Peles
Today a relation can be only for one blueprint, but this FR suggests having a relation that is modeled to be one of multiple blueprints.
For example -
"Resource" blueprint can be connected to one of - service, cloud resource, or on-prem resource, so we create this special relation, and for each entity the relation can be one of the connected blueprints.
For mirror properties, you will be able to mirror only the common properties (meta properties, and intersecting ones)
L
Leonardo Hackin
Hello, this feature is very welcome, due to blueprint dependency relation in some scenarios: this kind of use case can be done on another IDPs solutions at glance. Ex.: I'm trying to create a Blueprint called "Dependency" where I have a Source (a blueprint like Service or Software) and a Target (with the same blueprints).
The current solution that force us to create N relations to Source and the same to Destination is not what we expect on a tool that assumes to be more flexible then their competitors. :)
Please, help us.