NOTES AND DOMINO TROUBLESHOOTING RECORD
Prepared October 3, 2026 | Yenra
Guide: https://yenra.com/domino/links/
Purpose: prepare a reproducible report for a maintainer or support engineer.
Use a test environment and disposable data for reproduction. Store this record
privately. Remove credentials, ID files, tokens and unrelated personal content
before sharing a sample. This sheet does not authorize production changes.

1. ENVIRONMENT
Application and responsible owner:
Notes client version / fix pack / OS:
Domino server version / fix pack / OS:
Designer version:
Database path / local or server replica / template or design version:
Execution route (client button, scheduled agent, browser, other):
Test identity and relevant access context (no credentials):
Applicable supported-configuration reference:

2. OBSERVATION
One-sentence intended task:
Expected result:
Actual result and exact error message:
Time with time zone; frequency and number of attempts:
Affected users, documents and environments:
Recent changes, with timestamps:

3. REPRODUCTION
Prerequisites and initial data:
Numbered steps:
Repeat count / failures observed:
Minimal safe sample and approved private location:
Relevant log excerpts and timestamps:

4. DOCUMENTATION AND HYPOTHESIS
Product version / class or feature:
Official reference URL and relevant section:
Observed facts:
Proposed explanation to test:
One controlled test and predicted result:
Actual result:

5. CHANGE AND VERIFICATION
Approved correction and responsible person:
Recovery or reversal steps:
Original workflow retest / identity / result:
Remaining limitations and next action:

Example context: if a form button and server agent save differently, establish
how each obtains the document and which save method it uses. The guide links
HCL's NotesUIDocument/NotesDocument distinction and Save examples. Check the
installed-version reference before changing code. No Domino code was executed
to validate your particular environment in preparing this general worksheet.