Managed Fusion Admin APIs
(subject, object, linkType)
. An example would be (foo, bar, dependsOn)
, which would read as “foo dependsOn bar”.
For more information, view the API specification.
linkType
are as follows:
Trigger type | Parameters |
---|---|
inContextOf | The subject exists in the context of the object, which is an app. In this example, the “Movie_Search” app is the context for a parser with the same name: |
hasContext | The subject is an app that contains the object. In this example, an index profile exists in the context of the “Movie_Search” app: |
dependsOn | The subject depends on the object. In this example, a datasource called “web_pokeapi_co-default” depends on a parser by the same name: |
supports | The subject is depended on by the object (the reverse of |
isPartOf | The subject is part of the object, where the object is a group. In this example, an aggregation called “click-signals-default” is part of a group called “signals-object-group-default”: |
hasPart | The subject is a group, of which the object is a member (the reverse of |
relatesTo | The subject relates to the object. This is a uni-directional relationship that associates two objects that have none of the relationships described above. For example, when recommendations are enabled for the default collection, Managed Fusion creates a group of objects which relates to the default collection: |
relatesTo
link type, links are reversible:
inContextOf
is the reverse of hasContext
(and vice versa).dependsOn
is the reverse of supports
(and vice versa).isPartOf
is the reverse of hasPart
(and vice versa).signals-default
collection:
hasPart
objects shown above, we get the reverse representation: