FORMS-27300: log unresolved form asset for "Item not available" draft/submission entries - #1980
Open
ashnasingh101 wants to merge 1 commit into
Open
Conversation
…/submission entries
ashnasingh101
force-pushed
the
FORMS-27300-item-not-available-logging
branch
from
September 7, 2026 08:39
954214e to
6287282
Compare
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.
Problem
Forms Portal lists an "Item not available" placeholder in Drafts/Submissions when a
draft/submission record's form cannot be resolved on the current environment (form deleted or
unpublished here, or the record originates from another environment sharing the same store).
When this happens,
DraftsAndSubmissionsImpl.getItem()silently falls back to the placeholderwith no server-side signal, so the entry is impossible to triage from logs.
Root cause
In
getItem(), whenresourceResolver.getResource(formAssetPath)returnsnull, the methodfalls through to the hardcoded "Item not available" placeholder and still adds the item to the
list — with no logging on that branch.
Fix
Add an INFO log on the null-resource branch capturing
type,id,formPathand the resolvedasset path, so the placeholder entry can be traced and its cause (deleted-here vs. cross-environment
record) identified from logs. No behavior change — the item is still listed exactly as before.
Tests
testFormAssetNotResolvablecovering the previously-untested null-resource branch:asserts the placeholder title/description and null form link.
DraftsAndSubmissionsImplTestgreen (7/7); bundle compiles.