Release 3.9.0: API Impact

Modified on Mon, 11 May at 2:46 PM

Modified Response.java Files
  • AttachmentFileUploadResponse.java- modified
  • InternalControlResponse.java- modified
  • AttachmentResponse.java- modified
  • ContactResponse.java- modified
  • EvidenceResponse.java- modified
  • DocumentRequestResponse.java- modified
  • FindingResponse.java- modified
  • AssetWithAccessResponse.java- added
  • AttachmentPreviewResponse.java- added
  • EvidenceAssetResponse.java- added
  • RcsaResponse.java- added
  • RiskLedgerResponse.java- added
  • AssignedItemResponse.java- deleted
Breaking API Changes
  • AssignedItemResponsewas removed entirely. Any Java/API consumer referencing this DTO or its JSON shape is broken.
    • Removed fields:entityName,items,type,link
    • Removed generated Lombok methods/builders/accessors for that class.
  • EvidenceResponseremoved expanded relation arrays:
    • RemovedrelatedInternalControls: List<InternalControlResponse>
    • RemovedrelatedAssets: List<AssetSelectItem>
    • Counts remain:relatedInternalControlsCount,relatedAssetsCount
    • Breaking for clients expecting those arrays in evidence responses.
Per-File Summary
  • AssetWithAccessResponse.java
    • New DTO with fields:id,internalId,referenceId,name,assetType,primaryContact,status,accessible.
    • Adds Lombok-generated getters/setters/builder methods.
  • AttachmentFileUploadResponse.java
    • Added field:headers: Map<String, String>.
    • Adds generatedgetHeaders,setHeaders, builder setter.
  • AttachmentPreviewResponse.java
    • New DTO for attachment preview metadata.
    • Fields:filename,fileSize,contentType,original,pdf,images.
    • Adds Lombok-generated constructors, accessors, and super-builder methods.
  • AttachmentResponse.java
    • Added field:previewStatus: AttachmentPreviewStatusEnum.
    • Adds generated accessor/setter/builder method.
  • ContactResponse.java
    • Added field:contactSource: ContactSourceEnum, defaulting toDIRECT.
    • Adds generated accessor/setter/builder method.
    • Existing explicit methodnotAvailableContact(...)unchanged.
  • DocumentRequestResponse.java
    • Added field:shared: boolean.
    • Adds generatedisShared,setShared, builder method.
  • EvidenceAssetResponse.java
    • New DTO, same shape asAssetWithAccessResponse.
    • Fields:id,internalId,referenceId,name,assetType,primaryContact,status,accessible.
  • EvidenceResponse.java
    • Removed fields:relatedInternalControls,relatedAssets.
    • Added field:shared: boolean.
    • Removes generated accessors/builders for the removed relation lists.
  • FindingResponse.java
    • Added relation fields:
      • relatedRiskLedgers: List<ReferenceSelectItem>
      • relatedRcsas: List<ReferenceSelectItem>
      • relatedRiskLedgersCount: Long
      • relatedRcsasCount: Long
    • All default to empty list or0L.
    • Adds generated accessors/setters/builder methods.
  • InternalControlResponse.java
    • Added field:shared: boolean.
    • Adds generatedisShared,setShared, builder method.
  • RcsaResponse.java
    • New response DTO for RCSA records, including status, ratings, approval, contacts, tags, timestamps, and related assets.
    • Adds Lombok-generated constructors, accessors, and super-builder methods.
  • RiskLedgerResponse.java
    • New response DTO for risk ledger records, including status, RCSA link, related controls/registers counts, risk scoring fields, contacts, tags, and timestamps.
    • Adds Lombok-generated constructors, accessors, and super-builder methods.


No hand-written methods were added or removed in the surviving modified files; method surface changes come from Lombok-generated accessors/builders tied to added/removed fields.

Guidance for Removed EvidenceResponse Relation Fields
EvidenceResponse no longer includes the expanded relatedAssets or relatedInternalControls arrays. Clients that need those related records should fetch them from the Evidence list endpoints instead.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article