docs(api): add use-case examples for cmdb.external identifier endpoints - #1360
Merged
Conversation
Add a Use cases section to the cmdb.external page (EN + DE) with collapsible examples for link.v2 (connect an existing object), push.v2 (add data to a connected object, and create-and-fill in one call) and pull.v2 (look up what is connected), including a parameter table for link.v2. Also on the same page: - translate the English examples' placeholder from 'datenquelle' to 'datasource' - add the required 'data' parameter to the push parameter table - correct the pull parameter table: 'extId' is optional, not required - translate leftover German comments in the English push example - remove the now-unused 'DQ' abbreviation
MichaelOv
force-pushed
the
docs/api-external-use-cases
branch
from
July 31, 2026 07:32
bf28249 to
b0d3f8f
Compare
ljuergenliemke
approved these changes
Jul 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add use-case examples for the cmdb.external identifier endpoints (EN + DE)
The
cmdb.externalpage documented push and pull, but had no example forcmdb.external.link.v2and no use-case-driven walkthrough. This adds a Use cases section that follows one consistent flow: link an existing object, add data to it, create-and-fill in one call, and read it back.Added
cmdb.externalpage (EN + DE) with collapsible examples forcmdb.external.link.v2,cmdb.external.push.v2(add data to a connected object, and create-and-fill), andcmdb.external.pull.v2objectIdis a number without quotes and the JSON-RPCidbelongs at the top level of the requestChanged
object Ebene,Category Ebene,Und ganz wichtig:) in the English push exampleConditions
By sending this pull request I have read and accept the following conditions: