Add cmdlet Get-IshPublicationOutputContent to return directly linked content objects of this publication

[ddemeyer]

Quick drop from my personal notes to share an idea on community.sdl.com... Similar to cmdlet Get-IshFolderContent where you want to know which IshObjects (either IshPublicationOutput or IshDocumentObj) are in an IshFolder. People want to know which IshDocumentObj are directly linked to an IshPublicationOutput.

• Note that I state directly, so only using the baseline, not using any complete mode like LatestAvailable or LatestReleased. So imagine that some sub-map doesn't have a version selected in the baseline of the incoming IshPublicationOutput, then any topic used in that sub-map will not be part of the result set of this cmdlet, although the topic might have a version selected in the used baseline. You could say that the topic was unreachable for the given saved baseline.
• Baseline25.ExpandBaseline API function implementation parameters like pasLanguages, pasIllustrationLanguages, pasResourceLanguages and pasResolutions could come from the IshPublicationOutput fields. No cmdlet parameters option to overwrite yet, although this cmdlet would allow future -AutoCompleteMode parameters used by Baseline25 sibling functions.

Actions...
Starting point is cmdlet Get-IshPublicationOutputData which downloads the generated CHM/PDF/ZIP file, but this time we return the used content objects...

• Parameter Set IshObjectsGroup but drop FolderPath
• Output to the pipeline are IshDocumentObj that are directly reachable through baseline selected versions.
  • Root map linked xml content objects in the multiple requested languages
  • Root map linked image content object in the multiple requested languages and resolutions
  • Resource linked xml content objects in the multiple requested languages
  • Resource linked image content object in the multiple requested languages and resolutions
• Multi version test data see AddBackgroundTask.Tests.ps1 and AddIshPublicationOutput.Tests.ps1
• Examples like extract all files to file system over Get-IShDocumentObjData or something over Out-GridView or move status to Released
• (Optional parameter -Language[] taking value/element to overwrite the default incoming IshPublicationOutput metadata field values. Although post filtering on the pipeline through For-Each { ... } is the alternative for now.)
• (Optional parameter -Resolution[] taking value/element to overwrite the default incoming IshPublicationOutput metadata field values. Although post filtering on the pipeline through For-Each { ... } is the alternative for now.)

Ideas...

• Spike optional parameter AutoCompleteMode with the typical LatestAvailable and LatestReleased to go from an ExpandedBaseline into a CompletedBaseline.
• Spike in turn if Expanded-and-Completed IShDocumentObj - read LogicalIds and versions - could serve as pipeline input for Set-IShBaselineItem. The generated AutoComplete report can be used to explicitly set versions in a Baseline. See Extend Set-IshBaselineItem to update a baseline using the incoming IshDocumentObj versions #222
• Spike if this cmdlet plus ObjectType parameter (like Get-IshFolder -FolderTypeFilter) plus New-IshObfuscatedFile can be used to reproduce data structures but with anonymized content.... Perhaps needs the Save-IshDocumentObj and Load-IshDocumentObj

[ddemeyer]

Design notes after deep dive -- pre-implementation (corrected and expanded)

---

Phase 1 -- Get-IshPublicationOutputContent with SOAP

Core call: Baseline25.ExpandBaseline

Why not a separate Expand/Complete cmdlet: The Tridion Docs UI makes autocomplete transparent to users -- reports and publishing use it silently. Get-IshPublicationOutputContent follows the same convention; baseline is an implementation detail, not something surfaced to the user.

Silent metadata fetch: The cmdlet always does its own PublicationOutput25.RetrieveMetadataByIshLngRefs on the incoming IshPublicationOutput objects to guarantee all required fields are present, regardless of what the caller pre-fetched. Users are not required to request any specific fields upfront. IshObject.ObjectRef[ReferenceType.Lng] (the lngref / language card ID) is always structurally present on every IshPublicationOutput and is sufficient to fetch everything else.

Fields fetched internally and how they feed ExpandBaseline:

ExpandBaseline parameter	Field fetched from IshPublicationOutput	Level
baselineId	FISHBASELINE	Version
startLogicalIds[]	FISHMASTERREF (the root map logical ID -- not IshRef, which is the publication's own logical ID)	Version
startResourceLogicalIds[]	FISHRESOURCES (multi-value)	Version
languages[], illustrationLanguages[], resourceLanguages[]	FISHPUBLNGCOMBINATION mapped to all three arrays	Lng
resolutions[]	FISHOUTPUTFORMATREF (Lng) identifies the linked output format card -- secondary fetch of its FISHRESOLUTIONS field via OutputFormat25.GetMetadata	Lng -> OutputFormat card

Output pipeline -- lngref-first approach:

ExpandBaseline returns a Baseline Report XML (https://docs.rws.com/en-US/tridion-docs-main-documentation-1165616/baseline-report-70875). Each reportitem with reportresult="OK" carries a lngref attribute -- the language card ID. These are collected and passed in batches to DocumentObj25.RetrieveMetadataByIshLngRefs(long[] lngRefs, xmlRequestedMetadata) -- the same batched lngref-to-object hydration pattern that Get-IshFolderContent uses. No intermediate logical-id round-trip needed.

Batching respects IshSession.MetadataBatchSize. Output is IshDocumentObj[].

Version guard: API25.Baseline.ExpandBaseline is S on all ISHRemote-supported versions -- no PlatformNotSupportedException needed for the SOAP path.

---

Phase 2 -- AutoComplete mode (SOAP)

Adds optional -AutoCompleteMode parameter (values: ISHFirstVersion, ISHLatestReleased, ISHLatestAvailable). When provided, switches internally from Baseline25.ExpandBaseline to Baseline25.CompleteBaselineByCandidateAndMode. Note: CompleteBaselineByMode is deprecated on all versions; the correct call is CompleteBaselineByCandidateAndMode directly.

Adds optional -Language string[] and -Resolution string[] override parameters. When omitted, FISHPUBLNGCOMBINATION and FISHRESOLUTIONS are used as before (sourced silently). When provided, they override those defaults, mapping to all three of languages/illustrationLanguages/resourceLanguages and resolutions respectively.

The persist flag (REST-only on API30.CompleteBaseline) is deliberately not exposed -- that scenario belongs to issue #222 (Set-IshBaselineItem accepting IshDocumentObj versions).

---

Phase 3 -- Phase 1 rewired to OpenAPI

Core call: API30.ExpandBaseline (POST /v3/Baselines/{Id}/Report/Expand), available from 15.1 onward.

Version guard follows the exact model introduced in GetIshPublicationOutputData.cs (issue #245):

csharp case Enumerations.Protocol.OpenApiWithOpenIdConnect: if (IshSession.ServerIshVersion.MajorVersion > 15 || (IshSession.ServerIshVersion.MajorVersion == 15 && IshSession.ServerIshVersion.MinorVersion >= 1)) { // OpenAPI path -- REST response is BaselineReportEntry[] (typed objects) // BaselineReportItem.languageCardId maps to the lngref from the SOAP XML break; } // Server < 15.1: no REST endpoint, fall back to SOAP goto case Enumerations.Protocol.WcfSoapWithOpenIdConnect; case Enumerations.Protocol.WcfSoapWithWsTrust: case Enumerations.Protocol.WcfSoapWithOpenIdConnect: // SOAP path break;

The BaselineReportItem.languageCardId from the REST response feeds the same RetrieveMetadataByIshLngRefs batch call.

---

Phase 4 -- Phase 2 AutoComplete rewired to OpenAPI

Core call: API30.CompleteBaseline (POST /v3/Baselines/{Id}/Report/Complete), available from 15.1 onward. Same version guard as Phase 3.

-AutoCompleteMode enum value mapping: ISHFirstVersion -> firstVersion, ISHLatestReleased -> latestReleased, ISHLatestAvailable -> latestAvailable (SOAP uses ISH-prefixed names, REST uses lowercase camel -- handled internally).

---

Phasing rationale

Splitting SOAP and OpenAPI into separate phases keeps each commit reviewable and independently testable. Phases 1 and 2 cover all customers on any supported version. Phases 3 and 4 add the preferred protocol path for 15.1+ and 16.x without breaking anything.

[ddemeyer]

Phase 3 and 4 moved to separate issue #269