Fetch linked extension object
Resolves a link to an extension object and then loads exactly that object from the selected provider configuration.
Object(s) + key
Fetch linked extension object
Lien custom
Resolved relationship
Vue d’ensemble
Resolves a link to an extension object and then loads exactly that object from the selected provider configuration.
Exemple
From an Ormuz object, retrieve the explicitly linked provider object to read its current state.
Key point A custom link expresses an explicit association but changes neither authority nor lifecycle of linked objects.
Decision routes
foundLink found
A compatible target was resolved.
Recommended actionContinue with the object exposed by the route.
not_foundNo usable link
No compatible target is available for the requested key and type.
Recommended actionHandle absence explicitly or create the expected link before retrying.
Parameters 4
object
Source object from which links must be read or removed.
key
Stable business key naming the custom relationship. It isolates this relationship from other links between the same objects.
target_extension_config
Extension configuration identifying the provider and scope of the external objects concerned.
expected_type
Expected target type. It bounds resolution and determines output type when the node returns a platform object.
Outputs 2
selected_route
Route chosen according to link resolution:
found or not_found.object
Resolved linked object with the type determined by node configuration.
Behavior
The found route exposes the loaded extension object; not_found covers absence of a link or usable target according to the public contract.
Limits and responsibilities
- Custom links do not replace canonical business-model relationships when those exist.
- Creating a link grants no additional right over the target and transfers no business authority between objects.
- External loading requires a compatible configuration and a target that still exists at the provider.