title: Implementation Plan — Secondary Collection Service audience: developer keywords: Landsbankinn, Secondary Collection, milliinnheimta, QuerySecondaryCollectionClaims, SecondaryCollectionReturnClaim, IOBS, TS 163, implementation plan

locale: en-us

Implementation Plan — Secondary Collection Service

Add support for the Landsbankinn IcelandicOnlineBankingSecondaryCollectionClaims service (milliinnheimta / secondary collection, handbook TS 163).

Service facts

This service reuses the ClaimTypes schema. The existing Lbi Claims Builder, Lbi Claims Parser, and claim buffer tables apply directly — most work is routing to a second endpoint plus the four secondary-collection-specific operations.

Operations

It exposes the full claim operation set plus four secondary-collection-specific ones. Decision needed (see Open questions): ship only the unique four, or the full set against this endpoint. The four that have no equivalent in the existing Claims integration:

Shared claim operations also exposed on this endpoint (same shapes as the Claims service): QueryClaims, QueryClaim, AlterClaim(s), CancelClaim(s), GetClaimOperationResult, QueryClaimTransactions.

QueryClaimsResult, QueryPaymentsResult, ClaimOperationResult, Claim, and ClaimKey are the same ClaimTypes the current Claims integration already parses — reuse Lbi Claims Parser and the existing claim buffer tables.

Message types to expose (minimum viable)

ReturnClaims is async (returns an operation id), so poll it with Landsbankinn.SecCollection.GetOperationResult — the same pattern as the existing claim batch operations. Identifiers are Locked = true.

Reuse vs. new code

Objects to create

IDs continue at 72363+ (after the Documents plan if both proceed) — see the ID-range prerequisite in API_Gap_Analysis.md.

**Services layer — src/Services/SecondaryCollection/**

Reuse existing claim/payment buffer tables and Lbi Claims Parser for responses.

**Message-type layer — src/MessageTypes/SecondaryCollection/**

Access gate + permissions

Wire through Lbi Access Gate (mirror Lbi Claim Pmt Gate); add to Lbi Banki Full.

Plumbing changes (existing objects)

1. **Lbi Operation enum** — add SecColQueryClaims, SecColQueryPayments,

SecColReturnClaims, SecColGetOperationResult (reuse the existing GetClaimOperationResult only if it routes to the Claims endpoint; secondary collection needs its own endpoint, so add a distinct value).

1. **Lbi Client.SoapActionFor** — reuse ClaimsActionPrefixTok (…/2012/08/01);

add the four suffixes.

1. **Lbi Endpoint** — add `SecCollectionServicePathTok =

'/IcelandicOnlineBankingSecondaryCollectionClaims.svc', an accessor, and the new operations in ServiceUrlFor`.

1. **Lbi Cloud Event Msg Type enum extension** — add the four message-type values.
2. **Help.Landsbankinn.Get** overview — update count and list.

Tests — test/test/LbiSecCollectionTests.Codeunit.al

• Builder: QuerySecondaryCollectionClaims / …Payments bodies carry the correct wrapper

and ClaimTypes-qualified query fields.

• Routing: the new operations resolve to the secondary-collection endpoint URL, not the

Claims endpoint (assert via Lbi Endpoint.ServiceUrlFor).

• Impl: query returns parsed rows; ReturnBatch returns an operation id;

GetOperationResult polls it.

• Access gate blocks SecCollection.ReturnBatch without permission.

Open questions for Landsbankinn / TS 163

• Is the full claim operation set valid on this endpoint, or only the secondary-collection

operations? (Decides whether to ship the minimum-viable four or the full set.)

• SecondaryCollectionClaimsQuery and SecondaryCollectionPaymentsQuery filter fields.
• Whether GetClaimOperationResult on this endpoint shares the same operation-id space as

the primary Claims service.

Sequencing and effort

1. Confirm operation scope + XSD query shapes + TS 163 (0.5 day).
2. Endpoint routing + operation enum + action map (0.5 day).
3. Sec-collection builder + Mgt, reusing claims parser/buffers (1.5 days).
4. Message-type Impl + Help ×4 (1 day).
5. Access gate + permission sets (0.5 day).
6. Tests (1 day).

Rough total: ~5 developer-days (less if scope is the four unique operations only), plus live verification once Landsbankinn confirms entitlement for the secondary-collection service.

© Origo – Cloud Events Base Extension